Public report of Kong/insomnia, 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, 16:26 UTC · Survey ID cd_4d5aaf24b93740b7b3cb95a949adc9bc
Kong/insomnia
Measured 26 October 2026, 16:07 UTC, at code version 96edcab
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.
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreAt riskDown 2 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: 172,362 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 1.5 person-years · Weakest lens: Accessibility, 44
Findings by how serious they are
146 critical1446 serious531 minor
11 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, 16:07 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 ▸
84of 84 dimensions measured by tools.
2016of 2123 findings point to an exact file and line, so you can open each one in the code. The other 107 concern the repository as a whole, such as missing documentation.
84dimensions across 7 lenses, read from 172,362 lines of product code in 11 projects.
Kong/insomnia is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because it has controls that only work with a mouse. It scores 49 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 44, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 3 points. Checking whether the largest projects should be split comes next, worth about 1 point. Raising Accessibility to 70 would lift the score to about 53.
Fifty-four known security holes in the packages the code depends on can be used by attackers. Fourteen controls can't be used without a mouse, and thirteen passwords or keys are open to anyone who can read the repository. Making the controls work with a keyboard, updating the vulnerable packages and replacing each exposed password or key would close these risks. Fixing the weaknesses the scanner points to would fix the five security weaknesses in the code, and the three unsafe settings in infrastructure or container files need changing to safe values. The 18 uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 172,362 lines, about €210,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 44 to 70, the lowest score rated Strong, the score would rise from 49 to about 53.
Code composition: what the lines of code are
Product code 75%Tests 25%
New since the last survey: 349 findings
These 349 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.
God Classes · FunctionTooLong: git-change-analysis.GitChangeAnalysis packages/insomnia/src/ui/components/git/git-change-analysis.tsx
God Classes · ClassTooLong: ImportPostman packages/insomnia/src/main/importers/importers/postman.ts
God Classes · FileTooLong: common/render.ts packages/insomnia/src/common/render.ts
God Classes · FunctionTooLong: workspace-delete-modal.WorkspaceDeleteModal packages/insomnia/src/ui/components/modals/workspace-delete-modal.tsx
God Classes · FileTooLong: mcp/mcp-pane.tsx packages/insomnia/src/ui/components/mcp/mcp-pane.tsx
God Classes · FunctionTooLong: mcp-pane.CollectionGridListItem packages/insomnia/src/ui/components/mcp/mcp-pane.tsx
God Classes · FileTooLong: network/websocket.ts packages/insomnia/src/main/network/websocket.ts
Test Quality · Skipped test: can make a mock route: WARNING: THIS TEST DEPENDS ON mock-stage.insomnia.run to be up packages/insomnia-smoke-test/tests/smoke/mock.test.ts
Test Quality · Skipped test: should lint specification with custom ruleset packages/insomnia-inso/src/commands/lint-specification.test.ts
Test Quality · Skipped test: returns decrypted string when toJsonWebKey is false packages/insomnia/src/common/utils/vault.test.ts
Test Quality · Skipped test: returns decrypted object when toJsonWebKey is true packages/insomnia/src/common/utils/vault.test.ts
Boundary Type-Coupling · Cross-context type PersonalPlanType (insomnia-api → insomnia-data) packages/insomnia-data/src/models/organization.ts
Boundary Type-Coupling · Cross-context type InsoEvent (insomnia-analytics → insomnia-inso) packages/insomnia-inso/src/analytics.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia-scripting-environment) packages/insomnia-scripting-environment/src/objects/auth.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia-scripting-environment) packages/insomnia-scripting-environment/src/objects/auth.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/main/importers/entities.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/main/network/o-auth-1/get-token.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/network/authentication.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/network/authentication.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) REDACTED
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) REDACTED
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) REDACTED
Boundary Type-Coupling · Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/common/templating/types.ts
Boundary Type-Coupling · Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/common/project.ts
Boundary Type-Coupling · Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/common/project.ts
Boundary Type-Coupling · Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/common/project.ts
Boundary Type-Coupling · Cross-context type StrictNullSearchParamsValueType (insomnia-data → insomnia) REDACTED
Boundary Type-Coupling · Cross-context type StrictNullSearchParamsValueType (insomnia-data → insomnia) REDACTED
Boundary Type-Coupling · Cross-context type KeyboardShortcut (insomnia-data → insomnia) packages/insomnia/src/ui/components/modals/add-key-combination-modal.tsx
Boundary Type-Coupling · Cross-context type KeyboardShortcut (insomnia-data → insomnia) packages/insomnia/src/ui/components/modals/add-key-combination-modal.tsx
Boundary Type-Coupling · Cross-context type AnalyticsEvent (insomnia-analytics → insomnia) packages/insomnia/src/ui/analytics.ts
Boundary Type-Coupling · Cross-context type AnalyticsEvent (insomnia-analytics → insomnia) packages/insomnia/src/ui/analytics.ts
Boundary Type-Coupling · Cross-context type Compression (insomnia-data → insomnia) packages/insomnia/src/entry.hidden-window-preload.ts
Boundary Type-Coupling · Cross-context type AnalyticsEvent (insomnia-analytics → insomnia) packages/insomnia/src/main/analytics.ts
Boundary Type-Coupling · Cross-context type StageEntry (insomnia-vcs → insomnia) packages/insomnia/src/main/cloud-sync/ipc.ts
Boundary Type-Coupling · Cross-context type StageEntry (insomnia-vcs → insomnia) packages/insomnia/src/main/cloud-sync/ipc.ts
Boundary Type-Coupling · Cross-context type KonnectDeploymentType (insomnia-data → insomnia) packages/insomnia/src/konnect/transform.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/main/mcp/types.ts
Boundary Type-Coupling · Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.connect.tsx
Boundary Type-Coupling · Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.tsx
Boundary Type-Coupling · Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.tsx
Boundary Type-Coupling · Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/routes/untracked-projects.tsx
Boundary Type-Coupling · Cross-context type GitRepoCredentials (insomnia-data → insomnia) packages/insomnia/src/sync/git/get-oauth2-format-name.ts
Boundary Type-Coupling · Cross-context type StageEntry (insomnia-vcs → insomnia) packages/insomnia/src/sync/vcs/initialize-backend-project.ts
Boundary Type-Coupling · Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/sync/vcs/initialize-backend-project.ts
Boundary Type-Coupling · Cross-context type McpServerPrimitiveTypes (insomnia-data → insomnia) packages/insomnia/src/ui/components/mcp/types.ts
Boundary Type-Coupling · Cross-context type KeyboardShortcut (insomnia-data → insomnia) packages/insomnia/src/ui/components/keydown-binder.ts
Boundary Type-Coupling · Cross-context type KeyboardShortcut (insomnia-data → insomnia) packages/insomnia/src/ui/components/keydown-binder.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: 1536 findings
These 1536 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.
Code Duplication · Duplicated block with local edits (29 matched lines × 2 locations) packages/insomnia/src/ui/components/settings/number-setting.tsx
Rebuild cost: about €210,000 · Estimate
Cost to rebuild
€70,000 to €350,000, for 1,170 to 3,713 hours of work, about 1.5 person-years for 1 to 3 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 49. 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: 172,362 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. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.
Raises the score by about 1 point · Low effort · Project Cohesion
3
Fix the listed violations: declare the workspace packages these files import in the importing package's own REDACTED dependencies (470 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (20 rows); move the shared test helper into a source directory production code may depend on (2 rows).
Raises the score by about 2 points · Medium effort · Import Boundaries
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 €210,000 to build again, about 1.5 person-years of work. Its weakest lens is Accessibility, at 44 (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
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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 4.6 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 64,840 lines over the last 90 days, which is about 262,962 lines a year. At that pace, the extra work comes to an estimated 55.7 to 334.1 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 · 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: 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.
717 modules, with 579 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 677 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 insomnia-scripting-environment.src.objects.cookies uses a type in insomnia-scripting-environment.src.objects.properties.
insomnia-scripting-environment.src.objects.cookies uses insomnia-scripting-environment.src.objects.properties, so a change to insomnia-scripting-environment.src.objects.properties can break insomnia-scripting-environment.src.objects.cookies, while a change to insomnia-scripting-environment.src.objects.cookies can't break insomnia-scripting-environment.src.objects.properties.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.cookies uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in insomnia-scripting-environment.src.objects.urls uses a type in insomnia-scripting-environment.src.objects.properties.
insomnia-scripting-environment.src.objects.urls uses insomnia-scripting-environment.src.objects.properties, so a change to insomnia-scripting-environment.src.objects.properties can break insomnia-scripting-environment.src.objects.urls, while a change to insomnia-scripting-environment.src.objects.urls can't break insomnia-scripting-environment.src.objects.properties.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.urls uses a module listed above it, which is the healthy direction.
insomnia-vcs.src.types uses insomnia-inso.src.db.models.types, so a change to insomnia-inso.src.db.models.types can break insomnia-vcs.src.types, while a change to insomnia-vcs.src.types can't break insomnia-inso.src.db.models.types.
Position
Below the diagonal: insomnia-vcs.src.types uses a module listed above it, which is the healthy direction.
insomnia.src.basic-components uses insomnia.src.basic-components.button, so a change to insomnia.src.basic-components.button can break insomnia.src.basic-components, while a change to insomnia.src.basic-components can't break insomnia.src.basic-components.button.
Position
Below the diagonal: insomnia.src.basic-components uses a module listed above it, which is the healthy direction.
insomnia.src.common.templating.types uses insomnia-scripting-environment.src.objects.environments, so a change to insomnia-scripting-environment.src.objects.environments can break insomnia.src.common.templating.types, while a change to insomnia.src.common.templating.types can't break insomnia-scripting-environment.src.objects.environments.
Position
Below the diagonal: insomnia.src.common.templating.types uses a module listed above it, which is the healthy direction.
insomnia.src.main.mcp.types uses insomnia-data.src.models.request, so a change to insomnia-data.src.models.request can break insomnia.src.main.mcp.types, while a change to insomnia.src.main.mcp.types can't break insomnia-data.src.models.request.
Position
Below the diagonal: insomnia.src.main.mcp.types uses a module listed above it, which is the healthy direction.
insomnia.src.ui.components.base uses insomnia.src.basic-components.button, so a change to insomnia.src.basic-components.button can break insomnia.src.ui.components.base, while a change to insomnia.src.ui.components.base can't break insomnia.src.basic-components.button.
Position
Below the diagonal: insomnia.src.ui.components.base uses a module listed above it, which is the healthy direction.
insomnia.src.ui.components.sidebar.project-navigation-sidebar uses insomnia-inso.src.db, so a change to insomnia-inso.src.db can break insomnia.src.ui.components.sidebar.project-navigation-sidebar, while a change to insomnia.src.ui.components.sidebar.project-navigation-sidebar can't break insomnia-inso.src.db.
Position
Below the diagonal: insomnia.src.ui.components.sidebar.project-navigation-sidebar uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects.insomnia uses insomnia-data.common-src.settings, so a change to insomnia-data.common-src.settings can break insomnia-scripting-environment.src.objects.insomnia, while a change to insomnia-scripting-environment.src.objects.insomnia can't break insomnia-data.common-src.settings.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.insomnia uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in insomnia-scripting-environment.src.objects.insomnia uses a type in insomnia-scripting-environment.src.objects.environments.
insomnia-scripting-environment.src.objects.insomnia uses insomnia-scripting-environment.src.objects.environments, so a change to insomnia-scripting-environment.src.objects.environments can break insomnia-scripting-environment.src.objects.insomnia, while a change to insomnia-scripting-environment.src.objects.insomnia can't break insomnia-scripting-environment.src.objects.environments.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.insomnia uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in insomnia-scripting-environment.src.objects.insomnia uses a type in insomnia-scripting-environment.src.objects.cookies.
insomnia-scripting-environment.src.objects.insomnia uses insomnia-scripting-environment.src.objects.cookies, so a change to insomnia-scripting-environment.src.objects.cookies can break insomnia-scripting-environment.src.objects.insomnia, while a change to insomnia-scripting-environment.src.objects.insomnia can't break insomnia-scripting-environment.src.objects.cookies.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.insomnia uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in insomnia-scripting-environment.src.objects.request uses a type in insomnia-scripting-environment.src.objects.properties.
insomnia-scripting-environment.src.objects.request uses insomnia-scripting-environment.src.objects.properties, so a change to insomnia-scripting-environment.src.objects.properties can break insomnia-scripting-environment.src.objects.request, while a change to insomnia-scripting-environment.src.objects.request can't break insomnia-scripting-environment.src.objects.properties.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.request uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects.request uses insomnia-scripting-environment.src.objects.urls, so a change to insomnia-scripting-environment.src.objects.urls can break insomnia-scripting-environment.src.objects.request, while a change to insomnia-scripting-environment.src.objects.request can't break insomnia-scripting-environment.src.objects.urls.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.request uses a module listed above it, which is the healthy direction.
insomnia.src.main.git-service uses insomnia-vcs.src.types, so a change to insomnia-vcs.src.types can break insomnia.src.main.git-service, while a change to insomnia.src.main.git-service can't break insomnia-vcs.src.types.
Position
Below the diagonal: insomnia.src.main.git-service uses a module listed above it, which is the healthy direction.
insomnia.src.ui.components.modals uses insomnia.src.basic-components.button, so a change to insomnia.src.basic-components.button can break insomnia.src.ui.components.modals, while a change to insomnia.src.ui.components.modals can't break insomnia.src.basic-components.button.
Position
Below the diagonal: insomnia.src.ui.components.modals uses a module listed above it, which is the healthy direction.
insomnia.src.ui.components.modals uses insomnia-vcs.src.types, so a change to insomnia-vcs.src.types can break insomnia.src.ui.components.modals, while a change to insomnia.src.ui.components.modals can't break insomnia-vcs.src.types.
Position
Below the diagonal: insomnia.src.ui.components.modals uses a module listed above it, which is the healthy direction.
insomnia.src.ui.hooks uses insomnia-api.src.organizations, so a change to insomnia-api.src.organizations can break insomnia.src.ui.hooks, while a change to insomnia.src.ui.hooks can't break insomnia-api.src.organizations.
Position
Below the diagonal: insomnia.src.ui.hooks uses a module listed above it, which is the healthy direction.
insomnia.src.ui.hooks uses insomnia-inso.src.db, so a change to insomnia-inso.src.db can break insomnia.src.ui.hooks, while a change to insomnia.src.ui.hooks can't break insomnia-inso.src.db.
Position
Below the diagonal: insomnia.src.ui.hooks uses a module listed above it, which is the healthy direction.
insomnia.src.ui.hooks uses insomnia-scripting-environment.src.objects.environments, so a change to insomnia-scripting-environment.src.objects.environments can break insomnia.src.ui.hooks, while a change to insomnia.src.ui.hooks can't break insomnia-scripting-environment.src.objects.environments.
Position
Below the diagonal: insomnia.src.ui.hooks uses a module listed above it, which is the healthy direction.
insomnia.src.ui.hooks uses insomnia.src.common.plugins.types, so a change to insomnia.src.common.plugins.types can break insomnia.src.ui.hooks, while a change to insomnia.src.ui.hooks can't break insomnia.src.common.plugins.types.
Position
Below the diagonal: insomnia.src.ui.hooks uses a module listed above it, which is the healthy direction.
insomnia.src.ui.hooks uses insomnia.src.main.mcp.types, so a change to insomnia.src.main.mcp.types can break insomnia.src.ui.hooks, while a change to insomnia.src.ui.hooks can't break insomnia.src.main.mcp.types.
Position
Below the diagonal: insomnia.src.ui.hooks uses a module listed above it, which is the healthy direction.
insomnia-data.src.models uses insomnia-api.src.organizations, so a change to insomnia-api.src.organizations can break insomnia-data.src.models, while a change to insomnia-data.src.models can't break insomnia-api.src.organizations.
Position
Below the diagonal: insomnia-data.src.models uses a module listed above it, which is the healthy direction.
insomnia-data.src.models uses insomnia-data.src.models.project, so a change to insomnia-data.src.models.project can break insomnia-data.src.models, while a change to insomnia-data.src.models can't break insomnia-data.src.models.project.
Position
Below the diagonal: insomnia-data.src.models uses a module listed above it, which is the healthy direction.
44 pairs of types, where a type in insomnia-data.src.models uses a type in insomnia-inso.src.db.models.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
insomnia-data.src.models uses insomnia-inso.src.db.models.types, so a change to insomnia-inso.src.db.models.types can break insomnia-data.src.models, while a change to insomnia-data.src.models can't break insomnia-inso.src.db.models.types.
Position
Below the diagonal: insomnia-data.src.models uses a module listed above it, which is the healthy direction.
insomnia-data.src.models uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia-data.src.models, while a change to insomnia-data.src.models can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia-data.src.models uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects.interfaces uses insomnia-data.common-src.settings, so a change to insomnia-data.common-src.settings can break insomnia-scripting-environment.src.objects.interfaces, while a change to insomnia-scripting-environment.src.objects.interfaces can't break insomnia-data.common-src.settings.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.interfaces uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in insomnia-scripting-environment.src.objects.interfaces uses a type in insomnia-scripting-environment.src.objects.cookies.
insomnia-scripting-environment.src.objects.interfaces uses insomnia-scripting-environment.src.objects.cookies, so a change to insomnia-scripting-environment.src.objects.cookies can break insomnia-scripting-environment.src.objects.interfaces, while a change to insomnia-scripting-environment.src.objects.interfaces can't break insomnia-scripting-environment.src.objects.cookies.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.interfaces uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in insomnia-scripting-environment.src.objects.interfaces uses a type in insomnia-scripting-environment.src.objects.request.
insomnia-scripting-environment.src.objects.interfaces uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia-scripting-environment.src.objects.interfaces, while a change to insomnia-scripting-environment.src.objects.interfaces can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.interfaces uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in insomnia-scripting-environment.src.objects.response uses a type in insomnia-scripting-environment.src.objects.properties.
insomnia-scripting-environment.src.objects.response uses insomnia-scripting-environment.src.objects.properties, so a change to insomnia-scripting-environment.src.objects.properties can break insomnia-scripting-environment.src.objects.response, while a change to insomnia-scripting-environment.src.objects.response can't break insomnia-scripting-environment.src.objects.properties.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.response uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in insomnia-scripting-environment.src.objects.response uses a type in insomnia-scripting-environment.src.objects.cookies.
insomnia-scripting-environment.src.objects.response uses insomnia-scripting-environment.src.objects.cookies, so a change to insomnia-scripting-environment.src.objects.cookies can break insomnia-scripting-environment.src.objects.response, while a change to insomnia-scripting-environment.src.objects.response can't break insomnia-scripting-environment.src.objects.cookies.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.response uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in insomnia-scripting-environment.src.objects.response uses a type in insomnia-scripting-environment.src.objects.request.
insomnia-scripting-environment.src.objects.response uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia-scripting-environment.src.objects.response, while a change to insomnia-scripting-environment.src.objects.response can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia-scripting-environment.src.objects.response uses a module listed above it, which is the healthy direction.
insomnia.src.common uses insomnia-api.src.organizations, so a change to insomnia-api.src.organizations can break insomnia.src.common, while a change to insomnia.src.common can't break insomnia-api.src.organizations.
Position
Below the diagonal: insomnia.src.common uses a module listed above it, which is the healthy direction.
insomnia.src.common uses insomnia-data.src.models.project, so a change to insomnia-data.src.models.project can break insomnia.src.common, while a change to insomnia.src.common can't break insomnia-data.src.models.project.
Position
Below the diagonal: insomnia.src.common uses a module listed above it, which is the healthy direction.
insomnia.src.common uses insomnia-inso.src.db.models.types, so a change to insomnia-inso.src.db.models.types can break insomnia.src.common, while a change to insomnia.src.common can't break insomnia-inso.src.db.models.types.
Position
Below the diagonal: insomnia.src.common uses a module listed above it, which is the healthy direction.
insomnia.src.common uses insomnia-scripting-environment.src.objects.environments, so a change to insomnia-scripting-environment.src.objects.environments can break insomnia.src.common, while a change to insomnia.src.common can't break insomnia-scripting-environment.src.objects.environments.
Position
Below the diagonal: insomnia.src.common uses a module listed above it, which is the healthy direction.
insomnia.src.common uses insomnia-scripting-environment.src.objects.cookies, so a change to insomnia-scripting-environment.src.objects.cookies can break insomnia.src.common, while a change to insomnia.src.common can't break insomnia-scripting-environment.src.objects.cookies.
Position
Below the diagonal: insomnia.src.common uses a module listed above it, which is the healthy direction.
insomnia.src.common uses insomnia.src.common.templating.types, so a change to insomnia.src.common.templating.types can break insomnia.src.common, while a change to insomnia.src.common can't break insomnia.src.common.templating.types.
Position
Below the diagonal: insomnia.src.common uses a module listed above it, which is the healthy direction.
insomnia.src.common uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia.src.common, while a change to insomnia.src.common can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia.src.common uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in insomnia.src.main.importers.importers.postman-2_0_types uses a type in insomnia-scripting-environment.src.objects.urls.
insomnia.src.main.importers.importers.postman-2_0_types uses insomnia-scripting-environment.src.objects.urls, so a change to insomnia-scripting-environment.src.objects.urls can break insomnia.src.main.importers.importers.postman-2_0_types, while a change to insomnia.src.main.importers.importers.postman-2_0_types can't break insomnia-scripting-environment.src.objects.urls.
Position
Below the diagonal: insomnia.src.main.importers.importers.postman-2_0_types uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in insomnia.src.main.importers.importers.postman-2_0_types uses a type in insomnia-scripting-environment.src.objects.request.
insomnia.src.main.importers.importers.postman-2_0_types uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia.src.main.importers.importers.postman-2_0_types, while a change to insomnia.src.main.importers.importers.postman-2_0_types can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia.src.main.importers.importers.postman-2_0_types uses a module listed above it, which is the healthy direction.
insomnia.src.main.ipc.main uses insomnia.src.main.git-service, so a change to insomnia.src.main.git-service can break insomnia.src.main.ipc.main, while a change to insomnia.src.main.ipc.main can't break insomnia.src.main.git-service.
Position
Below the diagonal: insomnia.src.main.ipc.main uses a module listed above it, which is the healthy direction.
insomnia.src.main.network uses insomnia.src.main.mcp.types, so a change to insomnia.src.main.mcp.types can break insomnia.src.main.network, while a change to insomnia.src.main.network can't break insomnia.src.main.mcp.types.
Position
Below the diagonal: insomnia.src.main.network uses a module listed above it, which is the healthy direction.
insomnia.src.main.network uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia.src.main.network, while a change to insomnia.src.main.network can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia.src.main.network uses a module listed above it, which is the healthy direction.
insomnia.src.ui uses insomnia.src.main.git-service, so a change to insomnia.src.main.git-service can break insomnia.src.ui, while a change to insomnia.src.ui can't break insomnia.src.main.git-service.
Position
Below the diagonal: insomnia.src.ui uses a module listed above it, which is the healthy direction.
insomnia-data.node-src.services uses insomnia-data.common-src.settings, so a change to insomnia-data.common-src.settings can break insomnia-data.node-src.services, while a change to insomnia-data.node-src.services can't break insomnia-data.common-src.settings.
Position
Below the diagonal: insomnia-data.node-src.services uses a module listed above it, which is the healthy direction.
insomnia-data.node-src.services uses insomnia-data.src.models.project, so a change to insomnia-data.src.models.project can break insomnia-data.node-src.services, while a change to insomnia-data.node-src.services can't break insomnia-data.src.models.project.
Position
Below the diagonal: insomnia-data.node-src.services uses a module listed above it, which is the healthy direction.
insomnia-data.node-src.services uses insomnia-scripting-environment.src.objects.environments, so a change to insomnia-scripting-environment.src.objects.environments can break insomnia-data.node-src.services, while a change to insomnia-data.node-src.services can't break insomnia-scripting-environment.src.objects.environments.
Position
Below the diagonal: insomnia-data.node-src.services uses a module listed above it, which is the healthy direction.
insomnia-data.node-src.services uses insomnia-scripting-environment.src.objects.cookies, so a change to insomnia-scripting-environment.src.objects.cookies can break insomnia-data.node-src.services, while a change to insomnia-data.node-src.services can't break insomnia-scripting-environment.src.objects.cookies.
Position
Below the diagonal: insomnia-data.node-src.services uses a module listed above it, which is the healthy direction.
insomnia-data.node-src.services uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia-data.node-src.services, while a change to insomnia-data.node-src.services can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia-data.node-src.services uses a module listed above it, which is the healthy direction.
insomnia-data.node-src.services uses insomnia-scripting-environment.src.objects.response, so a change to insomnia-scripting-environment.src.objects.response can break insomnia-data.node-src.services, while a change to insomnia-data.node-src.services can't break insomnia-scripting-environment.src.objects.response.
Position
Below the diagonal: insomnia-data.node-src.services uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects uses insomnia-data.common-src.settings, so a change to insomnia-data.common-src.settings can break insomnia-scripting-environment.src.objects, while a change to insomnia-scripting-environment.src.objects can't break insomnia-data.common-src.settings.
Position
Below the diagonal: insomnia-scripting-environment.src.objects uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects uses insomnia-data.src.models.request, so a change to insomnia-data.src.models.request can break insomnia-scripting-environment.src.objects, while a change to insomnia-scripting-environment.src.objects can't break insomnia-data.src.models.request.
Position
Below the diagonal: insomnia-scripting-environment.src.objects uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects uses insomnia-scripting-environment.src.objects.urls, so a change to insomnia-scripting-environment.src.objects.urls can break insomnia-scripting-environment.src.objects, while a change to insomnia-scripting-environment.src.objects can't break insomnia-scripting-environment.src.objects.urls.
Position
Below the diagonal: insomnia-scripting-environment.src.objects uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia-scripting-environment.src.objects, while a change to insomnia-scripting-environment.src.objects can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia-scripting-environment.src.objects uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects uses insomnia-scripting-environment.src.objects.interfaces, so a change to insomnia-scripting-environment.src.objects.interfaces can break insomnia-scripting-environment.src.objects, while a change to insomnia-scripting-environment.src.objects can't break insomnia-scripting-environment.src.objects.interfaces.
Position
Below the diagonal: insomnia-scripting-environment.src.objects uses a module listed above it, which is the healthy direction.
insomnia-scripting-environment.src.objects uses insomnia-scripting-environment.src.objects.response, so a change to insomnia-scripting-environment.src.objects.response can break insomnia-scripting-environment.src.objects, while a change to insomnia-scripting-environment.src.objects can't break insomnia-scripting-environment.src.objects.response.
Position
Below the diagonal: insomnia-scripting-environment.src.objects uses a module listed above it, which is the healthy direction.
insomnia.src.konnect uses insomnia-data.src.models.project, so a change to insomnia-data.src.models.project can break insomnia.src.konnect, while a change to insomnia.src.konnect can't break insomnia-data.src.models.project.
Position
Below the diagonal: insomnia.src.konnect uses a module listed above it, which is the healthy direction.
insomnia.src.konnect uses insomnia.src.konnect.transform, so a change to insomnia.src.konnect.transform can break insomnia.src.konnect, while a change to insomnia.src.konnect can't break insomnia.src.konnect.transform.
Position
Below the diagonal: insomnia.src.konnect uses a module listed above it, which is the healthy direction.
insomnia.src.konnect uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia.src.konnect, while a change to insomnia.src.konnect can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia.src.konnect uses a module listed above it, which is the healthy direction.
insomnia.src.konnect uses insomnia-scripting-environment.src.objects.response, so a change to insomnia-scripting-environment.src.objects.response can break insomnia.src.konnect, while a change to insomnia.src.konnect can't break insomnia-scripting-environment.src.objects.response.
Position
Below the diagonal: insomnia.src.konnect uses a module listed above it, which is the healthy direction.
insomnia.src.main uses insomnia-scripting-environment.src.objects.cookies, so a change to insomnia-scripting-environment.src.objects.cookies can break insomnia.src.main, while a change to insomnia.src.main can't break insomnia-scripting-environment.src.objects.cookies.
Position
Below the diagonal: insomnia.src.main uses a module listed above it, which is the healthy direction.
insomnia.src.main uses insomnia.src.common.templating.types, so a change to insomnia.src.common.templating.types can break insomnia.src.main, while a change to insomnia.src.main can't break insomnia.src.common.templating.types.
Position
Below the diagonal: insomnia.src.main uses a module listed above it, which is the healthy direction.
insomnia.src.main uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia.src.main, while a change to insomnia.src.main can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia.src.main uses a module listed above it, which is the healthy direction.
insomnia.src.main uses insomnia.src.main.git-service, so a change to insomnia.src.main.git-service can break insomnia.src.main, while a change to insomnia.src.main can't break insomnia.src.main.git-service.
Position
Below the diagonal: insomnia.src.main uses a module listed above it, which is the healthy direction.
insomnia.src.main uses insomnia-scripting-environment.src.objects.response, so a change to insomnia-scripting-environment.src.objects.response can break insomnia.src.main, while a change to insomnia.src.main can't break insomnia-scripting-environment.src.objects.response.
Position
Below the diagonal: insomnia.src.main uses a module listed above it, which is the healthy direction.
insomnia.src.network.concurrency_renderer uses insomnia-data.common-src.settings, so a change to insomnia-data.common-src.settings can break insomnia.src.network.concurrency_renderer, while a change to insomnia.src.network.concurrency_renderer can't break insomnia-data.common-src.settings.
Position
Below the diagonal: insomnia.src.network.concurrency_renderer uses a module listed above it, which is the healthy direction.
insomnia.src.network.concurrency_renderer uses insomnia-scripting-environment.src.objects.environments, so a change to insomnia-scripting-environment.src.objects.environments can break insomnia.src.network.concurrency_renderer, while a change to insomnia.src.network.concurrency_renderer can't break insomnia-scripting-environment.src.objects.environments.
Position
Below the diagonal: insomnia.src.network.concurrency_renderer uses a module listed above it, which is the healthy direction.
insomnia.src.network.concurrency_renderer uses insomnia-scripting-environment.src.objects.cookies, so a change to insomnia-scripting-environment.src.objects.cookies can break insomnia.src.network.concurrency_renderer, while a change to insomnia.src.network.concurrency_renderer can't break insomnia-scripting-environment.src.objects.cookies.
Position
Below the diagonal: insomnia.src.network.concurrency_renderer uses a module listed above it, which is the healthy direction.
insomnia.src.network.concurrency_renderer uses insomnia-scripting-environment.src.objects.request, so a change to insomnia-scripting-environment.src.objects.request can break insomnia.src.network.concurrency_renderer, while a change to insomnia.src.network.concurrency_renderer can't break insomnia-scripting-environment.src.objects.request.
Position
Below the diagonal: insomnia.src.network.concurrency_renderer uses a module listed above it, which is the healthy direction.
insomnia.src.network.concurrency_renderer uses insomnia-scripting-environment.src.objects.interfaces, so a change to insomnia-scripting-environment.src.objects.interfaces can break insomnia.src.network.concurrency_renderer, while a change to insomnia.src.network.concurrency_renderer can't break insomnia-scripting-environment.src.objects.interfaces.
Position
Below the diagonal: insomnia.src.network.concurrency_renderer uses a module listed above it, which is the healthy direction.
insomnia.src.routes uses insomnia-data.src.models.project, so a change to insomnia-data.src.models.project can break insomnia.src.routes, while a change to insomnia.src.routes can't break insomnia-data.src.models.project.
Position
Below the diagonal: insomnia.src.routes uses a module listed above it, which is the healthy direction.
insomnia.src.routes uses insomnia-inso.src.db.models.types, so a change to insomnia-inso.src.db.models.types can break insomnia.src.routes, while a change to insomnia.src.routes can't break insomnia-inso.src.db.models.types.
Position
Below the diagonal: insomnia.src.routes uses a module listed above it, which is the healthy direction.
insomnia.src.routes uses insomnia-scripting-environment.src.objects.response, so a change to insomnia-scripting-environment.src.objects.response can break insomnia.src.routes, while a change to insomnia.src.routes can't break insomnia-scripting-environment.src.objects.response.
Position
Below the diagonal: insomnia.src.routes uses a module listed above it, which is the healthy direction.
insomnia.src.ui.components uses insomnia-data.common-src.settings, so a change to insomnia-data.common-src.settings can break insomnia.src.ui.components, while a change to insomnia.src.ui.components can't break insomnia-data.common-src.settings.
Position
Below the diagonal: insomnia.src.ui.components uses a module listed above it, which is the healthy direction.
insomnia.src.ui.components uses insomnia-data.src.models.request, so a change to insomnia-data.src.models.request can break insomnia.src.ui.components, while a change to insomnia.src.ui.components can't break insomnia-data.src.models.request.
Position
Below the diagonal: insomnia.src.ui.components uses a module listed above it, which is the healthy direction.
insomnia.src.ui.components uses insomnia.src.basic-components.button, so a change to insomnia.src.basic-components.button can break insomnia.src.ui.components, while a change to insomnia.src.ui.components can't break insomnia.src.basic-components.button.
Position
Below the diagonal: insomnia.src.ui.components uses a module listed above it, which is the healthy direction.
insomnia.src.ui.components uses insomnia.src.main.importers.importers.postman-2_0_types, so a change to insomnia.src.main.importers.importers.postman-2_0_types can break insomnia.src.ui.components, while a change to insomnia.src.ui.components can't break insomnia.src.main.importers.importers.postman-2_0_types.
Position
Below the diagonal: insomnia.src.ui.components uses a module listed above it, which is the healthy direction.
insomnia.src.network uses insomnia-data.common-src.settings, so a change to insomnia-data.common-src.settings can break insomnia.src.network, while a change to insomnia.src.network can't break insomnia-data.common-src.settings.
Position
Below the diagonal: insomnia.src.network uses a module listed above it, which is the healthy direction.
insomnia.src.network uses insomnia-data.src.models.request, so a change to insomnia-data.src.models.request can break insomnia.src.network, while a change to insomnia.src.network can't break insomnia-data.src.models.request.
Position
Below the diagonal: insomnia.src.network uses a module listed above it, which is the healthy direction.
insomnia.src.network uses insomnia-scripting-environment.src.objects.environments, so a change to insomnia-scripting-environment.src.objects.environments can break insomnia.src.network, while a change to insomnia.src.network can't break insomnia-scripting-environment.src.objects.environments.
Position
Below the diagonal: insomnia.src.network uses a module listed above it, which is the healthy direction.
insomnia.src.network uses insomnia.src.konnect.transform, so a change to insomnia.src.konnect.transform can break insomnia.src.network, while a change to insomnia.src.network can't break insomnia.src.konnect.transform.
Position
Below the diagonal: insomnia.src.network uses a module listed above it, which is the healthy direction.
insomnia.src.network uses insomnia-scripting-environment.src.objects.cookies, so a change to insomnia-scripting-environment.src.objects.cookies can break insomnia.src.network, while a change to insomnia.src.network can't break insomnia-scripting-environment.src.objects.cookies.
Position
Below the diagonal: insomnia.src.network uses a module listed above it, which is the healthy direction.
insomnia.src.network uses insomnia.src.network.concurrency_renderer, so a change to insomnia.src.network.concurrency_renderer can break insomnia.src.network, while a change to insomnia.src.network can't break insomnia.src.network.concurrency_renderer.
Position
Below the diagonal: insomnia.src.network uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 58% · Adequate · gated by D1, D2 ·
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
A03:2025 — Software Supply Chain Failures
85
High / Critical
A05:2025 — Injection
54
High / Critical
A07:2025 — Authentication Failures
14
High / Critical
A02:2025 — Security Misconfiguration
5
High / Critical
Roadmap
First, ensure all custom controls are fully keyboard-operable and every form element has a proper programmatic label to meet accessibility standards. Next, resolve the 470 cross-package import violations by updating package manifests and using public entry points, while breaking circular dependencies by extracting shared logic into independent modules. Finally, enforce these quality gates by integrating accessibility linting into the toolchain and requiring automated axe checks in CI to prevent future regressions.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Fix the listed violations: declare the workspace packages these files import in the importing package's own REDACTED dependencies (470 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (20 rows); move the shared test helper into a source directory production code may depend on (2 rows).
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.
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 — 146
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 — 1446
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 — 531
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
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. 84 of 84 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 — 84 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, 2016 of 2123 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.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/insomnia/ was NOT MEASURED: the dependency install for packages/insomnia/ could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/insomnia-analytics/ was NOT MEASURED: the dependency install for packages/insomnia-analytics/ could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/insomnia-api/ was NOT MEASURED: the dependency install for packages/insomnia-api/ could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/insomnia-data/ was NOT MEASURED: the dependency install for packages/insomnia-data/ could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/insomnia-scripting-environment/ was NOT MEASURED: the dependency install for packages/insomnia-scripting-environment/ could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/insomnia-testing/ was NOT MEASURED: the dependency install for packages/insomnia-testing/ could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/insomnia-vcs/ was NOT MEASURED: the dependency install for packages/insomnia-vcs/ could not reach registry.npmmirror.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://registry.npmmirror.com/git-side-band-message/-/git-side-band-message-0.0.3.tgz), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (packages/insomnia/send-request/electron/package.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
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.
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. `packages/insomnia-component-docs/docusaurus.config.ts`, `packages/insomnia-data/node-src/services/index.ts`, `packages/insomnia-data/src/models/index.ts`, `packages/insomnia/react-router.config.ts`, `packages/insomnia/src/common/import-deep-link.ts`, … (+12 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.
AC2 Forms & labels — 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. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/insomnia/src/sync/git/providers/registry.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
IC1 Incompleteness & stubs — 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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
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. 485 further occurrence(s) are not listed individually; the score already reflects all 525.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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. 556 further occurrence(s) are not listed individually; the score already reflects all 596.
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. 452 further occurrence(s) are not listed individually; the score already reflects all 492.
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. 69 further occurrence(s) are not listed individually; the score already reflects all 109.
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. 405 further occurrence(s) are not listed individually; the score already reflects all 445.
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. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's C, C++ is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's C++ is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — 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. 52 further occurrence(s) are not listed individually; the score already reflects all 92.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 19 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.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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.
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.
225 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was project-navigation-sidebar.ProjectNavigationSidebarInner at 203. A further 3 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 automock.mockScalar at 17 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/insomnia/src/main/ipc/automock.ts (automock.mockScalar at 17), packages/insomnia/src/main/llm-config-service.ts (llm-config-service.getBackendConfig at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 219 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with project-navigation-sidebar.ProjectNavigationSidebarInner (cyclomatic 203), project-settings-form.ProjectSettingsForm (cyclomatic 136), tag-editor.TagEditor (cyclomatic 131). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 2.1 to about 3.3/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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.
+ 264 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with project-navigation-sidebar.ProjectNavigationSidebarInner (cognitive 271), tag-editor.TagEditor (cognitive 148), organization.$organizationId.project.$projectId.update.clientAction (cognitive 125). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 2.0 to about 2.3/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes5.7 / 10Adequate✓ 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 144 FunctionTooLong finding(s) in God Classes — start with import-modal.tsx (3), organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx (2), insomnia-v5.ts (2). — One of this dimension's main actionable groups (144 warning-level).
Resolve the 41 FileTooLong finding(s) in God Classes — start with git-service.ts, git-project-staging-modal.tsx, git-vcs.ts. — One of this dimension's main actionable groups (41 warning-level).
Resolve the 4 ClassTooLong finding(s) in God Classes — start with git-vcs.ts, vcs.ts, repo-file-watcher.ts. — One of this dimension's main actionable groups (4 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.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
9 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 8 of the 9 (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).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with github.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
3292 test methods: 3289 unit, 3 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 3292 `it`/`test` case(s) across 352 test file(s) declaring at least one; its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Adequategated by 2 critical 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.
9 skipped (5 with a documented reason), 249 zero-assertion, 1 racing the wall clock, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3292 tests (1 harness-style project(s) excluded from the assertion penalty).
No assertions (empty test): t1 · ×2packages/insomnia-scripting-environment/src/objects/__tests__/test.test.ts:14
Skipped test: can make a mock route: WARNING: THIS TEST DEPENDS ON mock-stage.insomnia.run to be up · ×4packages/insomnia-smoke-test/tests/smoke/mock.test.ts:5
No assertions: merges even if no common root · ×4packages/insomnia-vcs/src/__tests__/vcs.test.ts:717
Races the wall clock: custom with format "yyyy" returns the current 4-digit yearpackages/insomnia/src/common/templating/__tests__/local-template-tags.test.ts:395
No direct assertions: after-response scripts: transient vars, assertions, and environment/global persistence · ×243packages/insomnia-smoke-test/tests/smoke/after-response-script-features.test.ts:9
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with test.test.ts (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 4 Skipped test finding(s) in Test Quality — start with vault.test.ts (2), mock.test.ts, lint-specification.test.ts. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 No assertions finding(s) in Test Quality — start with test.test.ts (2), vcs.test.ts, sync-queue.test.ts. — One of this dimension's main actionable groups (4 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.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
87 outdated direct production npm dependency(ies) of 145 graded, 0 pinning defect(s), across 12 REDACTED (11 of them the product) and 3 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 4 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Resolve the 16 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (16). — One of this dimension's main actionable groups (16 recommendation-level).
Resolve the 6 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 recommendation-level).
Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 145 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 145 production dependency(ies) this repository's committed lockfile resolves, across 11 product REDACTED manifest(s). Its 117 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 4 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx (16×203=3248); packages/insomnia/src/ui/components/templating/tag-editor.tsx (7×131=917); packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx (10×76=760) Repeated repair below the complexity floor: packages/insomnia/src/ui/components/templating/variable-editor.tsx (3 of 5 changes were fixes); packages/insomnia/src/ui/utils/render-realtime-connect.ts (3 of 4 changes were fixes); packages/insomnia/src/ui/context/app/insomnia-app-data-context.tsx (3 of 4 changes were fixes)
Resolve the 63 Hotspot finding(s) in Churn × Complexity Hotspots — start with project-navigation-sidebar.tsx, tag-editor.tsx, git-project-staging-modal.tsx. — One of this dimension's main actionable groups (63 warning-level).
Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with variable-editor.tsx, render-realtime-connect.ts, insomnia-app-data-context.tsx. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
32 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/insomnia/src/scripting/quickjs-script-engine.ts. Counted over 603 of the 1310 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×6
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.
142 deducted task-comment markers across 171643 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 135 TodoComment finding(s) in Explicit Debt — start with properties.ts (6), urls.ts (6), auth.ts (5). — One of this dimension's main actionable groups (135 warning-level).
Resolve the 6 HackComment finding(s) in Explicit Debt — start with misc.ts, organization.$organizationId.project.$projectId._index.tsx, organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.connect.tsx. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with progress.tsx. — 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. 22 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 domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
48 domain type(s) cross context boundaries across 9 contexts.
Cross-context type Project (insomnia-data → insomnia) · ×15packages/insomnia/src/common/templating/types.ts:157
Cross-context type RequestAuthentication (insomnia-data → insomnia) · ×10packages/insomnia/src/main/importers/entities.ts:53
Cross-context type KeyboardShortcut (insomnia-data → insomnia) · ×4packages/insomnia/src/ui/components/modals/add-key-combination-modal.tsx:11
Cross-context type AnalyticsEvent (insomnia-analytics → insomnia) · ×3packages/insomnia/src/ui/analytics.ts:18
Cross-context type StageEntry (insomnia-vcs → insomnia) · ×3packages/insomnia/src/main/cloud-sync/ipc.ts:57
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Cross-context type Project (insomnia-data → insomnia) finding(s) in Boundary Type-Coupling — start with project.ts (3), organization.$organizationId.project.$projectId.workspace.$workspaceId.tsx (2), use-insomnia-navigation.ts (2). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 10 Cross-context type RequestAuthentication (insomnia-data → insomnia) finding(s) in Boundary Type-Coupling — start with REDACTED (3), authentication.ts (2), entities.ts. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 4 Cross-context type KeyboardShortcut (insomnia-data → insomnia) finding(s) in Boundary Type-Coupling — start with add-key-combination-modal.tsx (2), keydown-binder.ts (2). — One of this dimension's main actionable groups (4 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
2 of 11 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: 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.
13 finding(s): 0 critical, 13 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 9 High secret finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (4). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
54 finding(s): 0 critical, 10 high, 44 medium, 0 low. 2 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 30 file(s) — `packages/insomnia-component-docs/docusaurus.config.ts` (line 32, line 75), `packages/insomnia-data/node-src/services/index.ts` (line 100), `packages/insomnia-data/src/models/client-certificate.test.ts` (line 3), `packages/insomnia-data/src/models/index.ts` (lines 12–24), `packages/insomnia/react-router.config.ts` (line 10), … (+25 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 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 44 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (43), REDACTED. — One of this dimension's main actionable groups (44 issue-level).
Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-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.
16 of 603 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/insomnia/src/sync/git/mem-client.ts. Counted over 603 of the 1310 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with interfaces.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 18 Change coupling finding(s) in Change Coupling — start with git-service.ts (2), project-create-form.tsx, organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with organization.$organizationId.project.$projectId._index.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether 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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 2 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives7.0 / 10Strong✓ 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. (×2) — packages/insomnia/src/routes/git-migration.$.tsx:210, packages/insomnia/src/ui/components/viewers/response-viewer.tsx:284
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.1 / 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 control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×6) — packages/insomnia/src/routes/auth.authorize.tsx:108, packages/insomnia/src/routes/auth.authorize.tsx:141, packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:544, …
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — packages/insomnia/src/ui/components/dropdowns/workspace-card-dropdown.tsx:316, packages/insomnia/src/ui/components/header-invite-button.tsx:131
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). (×6) — packages/insomnia/src/ui/components/editors/auth/components/auth-input-row.tsx:135, packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:182, packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:252, …
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. (×4) — packages/insomnia/src/ui/components/editors/body/file-editor.tsx:30, packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:132, packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:126, …
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×20) — packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx:393, packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx:447, packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:121, …
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. (×2) — packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:175, packages/insomnia/src/ui/components/modals/cloud-credential-modal/cloud-credential-modal.tsx:192
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>. — packages/insomnia/src/root.tsx:206
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). (×5) — REDACTED:14, packages/insomnia/src/ui/components/panes/placeholder-request-pane.tsx:39, packages/insomnia/src/ui/components/settings/shortcuts.tsx:47, …
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. (×9) — packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:675, packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:680, packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:684, …
This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. (×3) — packages/insomnia/src/ui/components/editable-input.tsx:79, packages/insomnia/src/ui/components/settings/vault-key-panel.tsx:45, packages/insomnia/src/ui/components/tabs/tab.tsx:179
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. (×6) — packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-field-link.tsx:23, packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-search-results.tsx:110, packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-search-results.tsx:143, …
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×3) — packages/insomnia/src/ui/components/project/konnect-moved-onboarding.tsx:33, packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/konnect-env-onboarding.tsx:33, packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/sidebar-focus-onboarding.tsx:33
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×2) — packages/insomnia/src/ui/components/settings/plugins.tsx:577, packages/insomnia/src/ui/components/settings/plugins.tsx:626
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.
A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded. — packages/insomnia/src/ui/components/spec-view.tsx:914
What to do
Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
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.
<i> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — packages/insomnia/src/ui/components/base/prompt-button.tsx:148
<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). — packages/insomnia/src/ui/components/first-request-creation.tsx:557
<div> moves — its `animate-[sidebar-focus-in_200ms_ease-out]` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×2) — packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:875, packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:1025
`summary` 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. — packages/insomnia/src/ui/css/main.css:166
`.form-control` 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. — packages/insomnia/src/ui/css/main.css:776
`textarea` 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. — packages/insomnia/src/ui/css/main.css:1059
`.modal: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. — packages/insomnia/src/ui/css/main.css:2430
`.sidebar: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. — packages/insomnia/src/ui/css/main.css:2951
`.CodeMirror-scroll` 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. — packages/insomnia/src/ui/css/lib/codemirror/codemirror.css:248
`.CodeMirror-code` 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. — packages/insomnia/src/ui/css/lib/codemirror/codemirror.css:375
`.ai-block` moves (`animation: AIBlockLoading 1s ease-in-out`) 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. — packages/insomnia/src/ui/css/main.css:767
`.toast` moves (`transition: opacity 200ms,
right 300ms,
bottom 300ms,
transform 200ms ease-out`) 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. — packages/insomnia/src/ui/css/main.css:3361
`.bounce-in` moves (`animation: bounceIn 350ms ease-in`) 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. — packages/insomnia/src/ui/css/styles.css:251
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 462 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 @axe-core/playwright 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.
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.
`IDatabase` declares 19 required operations: `batchModifyDocs`, `bufferChanges`, `bufferChangesIndefinitely`, `count`, `docCreate`, `docUpdate`, `duplicate`, `find`, `findOne`, `flushChanges`, `init`, `insert`, `onChange`, `remove`, `removeWhere`, `unsafeRemove`, `update`, `withAncestors`, `getWithDescendants`. 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/insomnia-data/src/database/types.ts:48
`PluginsBridgeAPI` declares 18 required operations: `getThemes`, `getPlugins`, `getActivePlugins`, `reloadPlugins`, `getRequestActions`, `getRequestGroupActions`, `getWorkspaceActions`, `getDocumentActions`, `executeAction`, `getTemplateTags`, `runTemplateTagAction`, `getBundlePlugins`, `executePluginMainAction`, `hasRequestHooks`, `hasResponseHooks`, `applyRequestHooks`, `applyResponseHooks`, `getBridgeMetrics`. 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/insomnia/src/common/plugins/bridge-types.ts:150
`SyncBridgeMethods` declares 24 required operations: `archiveProject`, `checkout`, `compareRemoteBranch`, `fork`, `getBranchNames`, `getCurrentBranchName`, `getHistory`, `getHistoryCount`, `getRemoteBranchNames`, `getVersion`, `merge`, `pull`, `push`, `removeBranch`, `removeRemoteBranch`, `rollback`, `rollbackToLatest`, `stage`, `status`, `switchAndCreateBackendProjectIfNotExist`, `takeSnapshot`, `unstage`, `getActiveBackendProject`, `hasBackendProject`. 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/insomnia/src/main/cloud-sync/ipc.ts:26
`RendererToMainBridgeAPI` declares 51 required operations: `runTests`, `loginStateChange`, `openInBrowser`, `restart`, `halfSecondAfterAppStart`, `openDeepLink`, `manualUpdateCheck`, `applyUpdateAndRestart`, `getUpdateStatus`, `backup`, `restoreBackup`, `setMenuBarVisibility`, `multipartBufferToArray`, `writeFile`, `deleteCompiledRuleset`, `refreshCompiledRuleset`, `writeResponseBodyToFile`, `getAuthHeader`, `getOAuth2Token`, `secureReadFile`, `insecureReadFile`, `insecureReadFileWithEncoding`, `readDir`, `readOrCreateDataDir`, `on`, `trackAnalyticsEvent`, `trackPageView`, `setCurrentOrganizationId`, `showNunjucksContextMenu`, `showContextMenu`, `lintSpec`, `bundleSpectralRuleset`, `createPlugin`, `getExecution`, `addExecutionStep`, `startExecution`, `completeExecutionStep`, `updateLatestStepName`, `extractJsonFileFromPostmanDataDumpArchive`, `getLocalStorageDataFromFileOrigin`, and 11 more. 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/insomnia/src/main/ipc/main.ts:218
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of 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, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
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.
`abortCommandSearch` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia-data/node-src/services/helpers/command-search.ts:321
`resetAsyncTasks` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia-scripting-environment/src/objects/async-objects.ts:81
`openDeepLinkUrl` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/entry.main.ts:66
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×2) — packages/insomnia/src/main/ipc/cookies.ts:23, packages/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:267
`setSecret` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/main/ipc/secret-storage.ts:22
`deleteSecret` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/main/ipc/secret-storage.ts:44
`clearConnectionContext` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/main/mcp/common.ts:171
`cancelRequest` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/main/mcp/common.ts:450
`deleteRequestMaps` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×3) — packages/insomnia/src/main/network/curl.ts:401, packages/insomnia/src/main/network/socket-io.ts:458, packages/insomnia/src/main/network/websocket.ts:563
`sendPayload` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/main/network/socket-io.ts:479
`sendWebSocketEvent` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — packages/insomnia/src/main/network/socket-io.ts:514, packages/insomnia/src/main/network/websocket.ts:618
`getWebSocketReadyState` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/main/network/websocket.ts:580
`onAction` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:591
`onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×9) — packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:764, packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:188, packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:201, …
`unlink` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/sync/git/mem-client.ts:173
`mkdir` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/sync/git/mem-client.ts:189
`rmdir` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — packages/insomnia/src/sync/git/mem-client.ts:224, packages/insomnia/src/sync/git/ne-db-client.ts:285
`symlink` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/sync/git/mem-client.ts:263
`onPress` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:1059
`onSelectionChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — packages/insomnia/src/ui/components/socket-io/event-tab-pane.tsx:161
`getNavigationTabId` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/insomnia/src/ui/hooks/use-insomnia-tab.ts:240
`certificates` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/insomnia-data/__schemas__/model-schemas.ts:35, packages/insomnia-vcs/src/__schemas__/model-schemas.ts:35
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×4) — packages/insomnia-inso/src/commands/lint-specification.test.ts:45, packages/insomnia-smoke-test/tests/smoke/mock.test.ts:5, packages/insomnia/src/common/utils/vault.test.ts:73, …
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
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.
1007 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 6 of 12 project(s) that lack one — worth up to 1 pts.
Review the README against recent changes; refresh the parts that drifted.
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.
packages/insomnia-smoke-test/README.md links to `CLI.md`, but `packages/insomnia-smoke-test/CLI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — packages/insomnia-smoke-test/README.md:5
What to do
Reconcile the README with reality: packages/insomnia-smoke-test/README.md links to `CLI.md`, but `packages/insomnia-smoke-test/CLI.md` 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 & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/insomnia-smoke-test`.
`packages/insomnia/customSign.js` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/customSign.js:12
`packages/insomnia/customSign.js` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/customSign.js:18
`packages/insomnia/customSign.js` reports through `console.*` at line 25 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/customSign.js:25
`packages/insomnia/customSign.js` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/customSign.js:31
`packages/insomnia/customSign.js` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/customSign.js:34
`packages/insomnia/customSign.js` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/customSign.js:36
`packages/insomnia/customSign.js` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/customSign.js:39
`packages/insomnia/customSign.js` reports through `console.*` at line 41 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/customSign.js:41
`packages/insomnia/src/entry.hidden-window-preload.ts` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.hidden-window-preload.ts:39
`packages/insomnia/src/entry.hidden-window.ts` reports through `console.*` at line 50 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.hidden-window.ts:50
`packages/insomnia/src/entry.hidden-window.ts` reports through `console.*` at line 58 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.hidden-window.ts:58
`packages/insomnia/src/entry.plugin-window.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.plugin-window.ts:23
`packages/insomnia/src/entry.plugin-window.ts` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.plugin-window.ts:39
`packages/insomnia/src/entry.preload.ts` reports through `console.*` at line 371 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.preload.ts:371
`packages/insomnia/src/script-executor.ts` reports through `console.*` at line 25 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/script-executor.ts:25
`packages/insomnia/src/script-executor.ts` reports through `console.*` at line 73 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/script-executor.ts:73
`packages/insomnia/src/script-executor.ts` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/script-executor.ts:74
`packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 87 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.client.tsx:87
`packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 144 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.client.tsx:144
`packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 164 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.client.tsx:164
`packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 170 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.client.tsx:170
`packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 185 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.client.tsx:185
`packages/insomnia/src/entry.server.tsx` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/entry.server.tsx:56
`packages/insomnia/src/root.tsx` 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. — packages/insomnia/src/root.tsx:89
`packages/insomnia/src/root.tsx` reports through `console.*` at line 744 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/root.tsx:744
`packages/insomnia/src/ui/auth-session-provider.client.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/auth-session-provider.client.ts:17
`packages/insomnia/src/ui/auth-session-provider.client.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/auth-session-provider.client.ts:23
`packages/insomnia/src/ui/auth-session-provider.client.ts` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/auth-session-provider.client.ts:39
`packages/insomnia/src/ui/auth-session-provider.client.ts` reports through `console.*` at line 78 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/auth-session-provider.client.ts:78
`packages/insomnia/src/ui/auth-session-provider.client.ts` reports through `console.*` at line 86 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/auth-session-provider.client.ts:86
`packages/insomnia/src/ui/organization-utils.ts` reports through `console.*` at line 208 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/organization-utils.ts:208
`packages/insomnia/src/ui/renderer-listeners.ts` reports through `console.*` at line 26 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/renderer-listeners.ts:26
`packages/insomnia/src/ui/vault-key.client.ts` reports through `console.*` at line 82 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/vault-key.client.ts:82
`packages/insomnia/src/ui/worker/templating-handler.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/worker/templating-handler.ts:11
`packages/insomnia/src/ui/utils/dedupe-collection-items.ts` reports through `console.*` at line 6 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/utils/dedupe-collection-items.ts:6
`packages/insomnia/src/ui/utils/first-request-latch.ts` reports through `console.*` at line 85 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/utils/first-request-latch.ts:85
`packages/insomnia/src/ui/utils/first-request-latch.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. — packages/insomnia/src/ui/utils/first-request-latch.ts:89
`packages/insomnia/src/ui/utils/record-action.ts` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/insomnia/src/ui/utils/record-action.ts:34
`packages/insomnia/src/ui/utils/router.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. — packages/insomnia/src/ui/utils/router.ts:53
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.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether 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.existsSync` in `callback to action` 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:563
`fs.statSync` in `callback to action` 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:564
`fs.accessSync` in `callback to action` 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:570
`fs.existsSync` in `DbAdapter` 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. — packages/insomnia-inso/src/db/adapters/insomnia-adapter.ts:69
`fs.lstatSync` in `DbAdapter` 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. — packages/insomnia-inso/src/db/adapters/insomnia-adapter.ts:69
`fs.existsSync` in `copyFixtureDatabase` 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. — packages/insomnia-smoke-test/playwright/paths.ts:21
`fs.statSync` in `callback to files.map` 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. — packages/insomnia-smoke-test/playwright/utils/file-operations.ts:37
`zlib.gzipSync` in `callback to blobIds.forEach` 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:515
`zlib.gunzipSync` in `callback to blobs.forEach` 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:669
`existsSync` in `app.post("/v1/test-utils/git/setup")` 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:198
`rmSync` in `app.post("/v1/test-utils/git/setup")` 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:199
`mkdtempSync` in `app.post("/v1/test-utils/git/setup")` 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:201
`cpSync` in `app.post("/v1/test-utils/git/setup")` 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:202
`existsSync` in `app.delete("/v1/test-utils/git/setup")` 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:208
`rmSync` in `app.delete("/v1/test-utils/git/setup")` 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:209
`fs.mkdirSync` in `generateVendoredFile` 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. — packages/insomnia/scripts/sandbox-vendored-lib.ts:78
`fs.writeFileSync` in `generateVendoredFile` 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. — packages/insomnia/scripts/sandbox-vendored-lib.ts:80
`mkdirSync` in `ipcMainHandle("openPath")` 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. — packages/insomnia/src/main/ipc/electron.ts:477
`fs.statSync` 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) — packages/insomnia/src/main/network/libcurl-promise.ts:162, packages/insomnia/src/main/network/multipart.ts:28
`fs.openSync` 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. — packages/insomnia/src/main/network/libcurl-promise.ts:168
`fs.readFileSync` in `callback to filteredClientCertificates.forEach` 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. (×6) — packages/insomnia/src/main/network/socket-io.ts:208, packages/insomnia/src/main/network/socket-io.ts:213, packages/insomnia/src/main/network/socket-io.ts:218, …
`fs.readFileSync` in `findHandlersThatBypassBodyPathOwnership` 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) — packages/insomnia/src/main/templating-worker-database-surface.ts:118, packages/insomnia/src/main/templating-worker-database-surface.ts:124
`fs.writeFileSync` in `findHandlersThatBypassBodyPathOwnership` 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. — packages/insomnia/src/main/templating-worker-database-surface.ts:127
`fs.mkdirSync` in `recursiveWriteProtoDirectory` 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. — packages/insomnia/src/network/grpc/write-proto-file.node.ts:38
`fs.existsSync` in `callback to files.map` 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. — packages/insomnia/src/network/grpc/write-proto-file.node.ts:45
`fs.mkdirSync` in `writeProtoFile` 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. — packages/insomnia/src/network/grpc/write-proto-file.node.ts:116
`fs.existsSync` in `writeProtoFile` 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. — packages/insomnia/src/network/grpc/write-proto-file.node.ts:125
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.9 / 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.
71 duplicated blocks under packages/insomnia/src/ui/components/ have copies in at least two of the sibling directories dropdowns, editors, git, git-credentials, graph-ql-explorer, key-value-editor (+10 more sibling(s) not listed) — 55 of them are reported below, and 16 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 71 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 71 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 71 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/insomnia/src/ui/components/socket-io/request-pane.tsx:196
45 duplicated blocks under packages/insomnia/src/ have copies in at least two of the sibling directories common, main, network, plugins, routes, runtimes (+3 more sibling(s) not listed) — 36 of them are reported below, and 9 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 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:64
11 duplicated blocks under packages/ have copies in at least two of the sibling directories insomnia, insomnia-data, insomnia-inso, insomnia-scripting-environment, insomnia-testing, insomnia-vcs — 7 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 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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/insomnia-inso/src/commands/lint-specification.ts:23
packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:64 · packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx:68 — the two spans are one implementation copied and then locally edited — 1828 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/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:64
packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:1 · packages/insomnia/src/ui/components/modals/git-project-branches-modal.tsx:1 — these 2 files are line-for-line copies of one another — 277 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. — packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:1
packages/insomnia/src/sync/git/providers/github.ts:92 · packages/insomnia/src/sync/git/providers/gitlab.ts:156 — the two spans are one implementation copied and then locally edited — 1124 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/insomnia/src/sync/git/providers/github.ts:92
packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:532 · packages/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:255 — the two spans are one implementation copied and then locally edited — 622 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/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:532
packages/insomnia/src/ui/components/settings/llms/gemini.tsx:38 · packages/insomnia/src/ui/components/settings/llms/openai.tsx:42 — 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. — packages/insomnia/src/ui/components/settings/llms/gemini.tsx:38
packages/insomnia/src/ui/components/settings/llms/gguf.tsx:24 · packages/insomnia/src/ui/components/settings/llms/url.tsx:38 — the two spans are one implementation copied and then locally edited — 840 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/insomnia/src/ui/components/settings/llms/gguf.tsx:24
packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:57 · packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:64 — the two spans are one implementation copied and then locally edited — 644 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/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:57
packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.tsx:114 · packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.test.tsx:123 — the two spans are one implementation copied and then locally edited — 635 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/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.tsx:114
packages/insomnia/src/ui/components/settings/llms/claude.tsx:1 · packages/insomnia/src/ui/components/settings/llms/openai.tsx:1 — these 2 files are line-for-line copies of one another — 114 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. — packages/insomnia/src/ui/components/settings/llms/claude.tsx:1
packages/insomnia/src/ui/components/settings/llms/claude.tsx:58 · packages/insomnia/src/ui/components/settings/llms/gemini.tsx:62 · packages/insomnia/src/ui/components/settings/llms/openai.tsx:66 — the 3 copies are spread across 3 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. — packages/insomnia/src/ui/components/settings/llms/claude.tsx:58
packages/insomnia/src/ui/components/socket-io/request-pane.tsx:196 · packages/insomnia/src/ui/components/websockets/websocket-request-pane.tsx:348 — 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. — packages/insomnia/src/ui/components/socket-io/request-pane.tsx:196
packages/insomnia/src/common/project.ts:156 · packages/insomnia/src/routes/organization.$organizationId.project.$projectId.list-workspaces.tsx:16 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/insomnia/src/common/project.ts:156
packages/insomnia/src/ui/components/modals/request-settings-modal.tsx:137 · packages/insomnia/src/ui/components/modals/request-settings-modal.tsx:327 — the two spans are one implementation copied and then locally edited — 429 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. — packages/insomnia/src/ui/components/modals/request-settings-modal.tsx:137
packages/insomnia/src/ui/components/settings/credentials.tsx:69 · packages/insomnia/src/ui/components/settings/credentials.tsx:297 — the two spans are one implementation copied and then locally edited — 515 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. — packages/insomnia/src/ui/components/settings/credentials.tsx:69
packages/insomnia/src/templating/index.ts:29 · packages/insomnia/src/ui/templating/worker.ts:26 — the two spans are one implementation copied and then locally edited — 630 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/insomnia/src/templating/index.ts:29
packages/insomnia/src/ui/components/modals/git-log-modal.tsx:1 · packages/insomnia/src/ui/components/modals/git-project-log-modal.tsx:1 — these 2 files are line-for-line copies of one another — 78 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. — packages/insomnia/src/ui/components/modals/git-log-modal.tsx:1
packages/insomnia/src/ui/components/dropdowns/request-actions-dropdown.tsx:293 · packages/insomnia/src/ui/components/dropdowns/request-group-actions-dropdown.tsx:332 — 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. — packages/insomnia/src/ui/components/dropdowns/request-actions-dropdown.tsx:293
packages/insomnia/src/script-executor.ts:60 · packages/insomnia/src/scripting/run-script.ts:80 — the two spans are one implementation copied and then locally edited — 323 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/insomnia/src/script-executor.ts:60
packages/insomnia/src/ui/components/panes/request-pane.tsx:244 · packages/insomnia/src/ui/components/socket-io/request-pane.tsx:240 · packages/insomnia/src/ui/components/websockets/websocket-request-pane.tsx:392 — the 3 copies are spread across 3 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. — packages/insomnia/src/ui/components/panes/request-pane.tsx:244
packages/insomnia/src/common/templating/liquid-extension-worker.ts:65 · packages/insomnia/src/templating/liquid-extension.ts:23 — the two spans are one implementation copied and then locally edited — 462 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/insomnia/src/common/templating/liquid-extension-worker.ts:65
packages/insomnia/src/plugins/themes/default.ts:1 · packages/insomnia/src/plugins/themes/legacy.ts:1 — these 2 files are line-for-line copies of one another — 53 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. — packages/insomnia/src/plugins/themes/default.ts:1
packages/insomnia/src/ui/components/environment-picker.tsx:165 · packages/insomnia/src/ui/components/environment-picker.tsx:264 — the two spans are one implementation copied and then locally edited — 235 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. — packages/insomnia/src/ui/components/environment-picker.tsx:165
packages/insomnia/src/ui/components/project/project-create-form.tsx:431 · packages/insomnia/src/ui/components/project/project-settings-form.tsx:745 — 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. — packages/insomnia/src/ui/components/project/project-create-form.tsx:431
packages/insomnia/src/main/templating-worker-database.ts:821 · packages/insomnia/src/plugins/context/network.ts:67 — 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. — packages/insomnia/src/main/templating-worker-database.ts:821
packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.generate-request-collection.tsx:14 · packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.spec.generate-request-collection.tsx:19 — the two spans are one implementation copied and then locally edited — 211 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/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.generate-request-collection.tsx:14
packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx:122 · packages/insomnia/src/ui/components/settings/credentials.tsx:229 · packages/insomnia/src/ui/components/settings/credentials.tsx:341 — the 3 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. — packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx:122
packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:680 · packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:998 — 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. — packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:680
packages/insomnia/src/sync/git/git-vcs.ts:1463 · packages/insomnia/src/sync/git/git-vcs.ts:1687 — 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. — packages/insomnia/src/sync/git/git-vcs.ts:1463
packages/insomnia/src/ui/components/panes/request-test-result-pane.tsx:169 · packages/insomnia/src/ui/components/panes/runner-test-result-pane.tsx:94 — the two spans are one implementation copied and then locally edited — 191 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/insomnia/src/ui/components/panes/request-test-result-pane.tsx:169
packages/insomnia-data/node-src/services/socket-io-request-meta.ts:4 · packages/insomnia-data/node-src/services/websocket-request-meta.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. — packages/insomnia-data/node-src/services/socket-io-request-meta.ts:4
packages/insomnia/src/ui/components/editors/mock-response-headers-editor.tsx:24 · packages/insomnia/src/ui/components/editors/request-parameters-editor.tsx: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. — packages/insomnia/src/ui/components/editors/mock-response-headers-editor.tsx:24
packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx:327 · packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx:399 — 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/insomnia/src/ui/components/modals/sync-staging-modal.tsx:327
packages/insomnia/src/routes/ai.generate-commit-messages.tsx:10 · packages/insomnia/src/routes/ai.mcp-generate-sampling-response.tsx:20 — the two spans are one implementation copied and then locally edited — 201 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/insomnia/src/routes/ai.generate-commit-messages.tsx:10
packages/insomnia/src/main/templating-worker-database.ts:483 · packages/insomnia/src/main/templating-worker-database.ts:554 — 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/insomnia/src/main/templating-worker-database.ts:483
packages/insomnia/src/ui/components/.client/codemirror/code-editor.tsx:753 · packages/insomnia/src/ui/components/.client/codemirror/one-line-editor.tsx:526 — 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. — packages/insomnia/src/ui/components/.client/codemirror/code-editor.tsx:753
packages/insomnia/src/ui/components/command-palette.tsx:323 · packages/insomnia/src/ui/components/command-palette.tsx:422 — 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/insomnia/src/ui/components/command-palette.tsx:323
packages/insomnia/src/sync/git/git-vcs.ts:490 · packages/insomnia/src/sync/git/git-vcs.ts:654 — 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/insomnia/src/sync/git/git-vcs.ts:490
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.
packages/insomnia-data/node-src/services/organization.ts:1 imports insomnia-api, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-data/node-src/services/organization.ts:1
packages/insomnia-data/node-src/services/project.ts:1 imports insomnia-api, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-data/node-src/services/project.ts:1
packages/insomnia-inso/src/analytics.ts:3 imports insomnia/src/common/constants, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-inso/src/analytics.ts:3
packages/insomnia-inso/src/analytics.ts:4 imports insomnia-analytics, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-inso/src/analytics.ts:4
REDACTED:11 imports insomnia/src/common/configure-v3-client, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:11
REDACTED:12 imports insomnia/src/common/constants, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:12
REDACTED:13 imports insomnia/src/common/insomnia-fetch, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:13
REDACTED:14 imports insomnia/src/network/send-request.node, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:14
REDACTED:15 imports insomnia/src/runtimes, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:15
REDACTED:16 imports insomnia/src/runtimes/runtime.node, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:16
REDACTED:17 imports insomnia-api, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:17
REDACTED:26 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:26
REDACTED:27 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:27
REDACTED:28 imports insomnia-data/node, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:28
REDACTED:29 imports insomnia-testing/src/generate/generate, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:29
REDACTED:30 imports insomnia-testing/src/run/run, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:30
packages/insomnia-inso/src/commands/lint-specification.ts:14 imports insomnia/src/main/bundle-spectral-ruleset, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-inso/src/commands/lint-specification.ts:14
packages/insomnia-inso/src/commands/lint-specification.ts:15 imports insomnia/src/main/private-host, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-inso/src/commands/lint-specification.ts:15
packages/insomnia-inso/src/commands/run-collection/result-report.ts:15 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-inso/src/commands/run-collection/result-report.ts:15
packages/insomnia-inso/src/db/adapters/git-adapter.ts:4 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-inso/src/db/adapters/git-adapter.ts:4
packages/insomnia-inso/src/db/adapters/insomnia-adapter.ts:4 imports insomnia/src/common/insomnia-v5, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-inso/src/db/adapters/insomnia-adapter.ts:4
packages/insomnia-scripting-environment/src/objects/insomnia.ts:3 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-scripting-environment/src/objects/insomnia.ts:3
packages/insomnia-scripting-environment/src/objects/interpolator.ts:1 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-scripting-environment/src/objects/interpolator.ts:1
packages/insomnia-scripting-environment/src/objects/request.ts:9 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-scripting-environment/src/objects/request.ts:9
packages/insomnia-scripting-environment/src/objects/response.ts:3 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-scripting-environment/src/objects/response.ts:3
packages/insomnia-scripting-environment/src/objects/response.ts:4 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-scripting-environment/src/objects/response.ts:4
packages/insomnia-scripting-environment/src/objects/send-request.ts:3 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-scripting-environment/src/objects/send-request.ts:3
packages/insomnia-scripting-environment/src/objects/send-request.ts:23 imports insomnia/src/main/network/libcurl-promise, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-scripting-environment/src/objects/send-request.ts:23
packages/insomnia-vcs/setup-vitest.ts:1 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/setup-vitest.ts:1
packages/insomnia-vcs/setup-vitest.ts:2 imports insomnia-data/node, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/setup-vitest.ts:2
packages/insomnia-vcs/setup-vitest.ts:10 reaches into another package with a relative path (../insomnia-data/__mocks__/uuid) — import the package by name instead. — packages/insomnia-vcs/setup-vitest.ts:10
packages/insomnia-vcs/setup-vitest.ts:10 imports packages/insomnia-data/__mocks__/uuid.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/insomnia-vcs/setup-vitest.ts:10
packages/insomnia-vcs/src/__schemas__/model-schemas.ts:4 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/src/__schemas__/model-schemas.ts:4
packages/insomnia-vcs/src/backend-projects.ts:3 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/src/backend-projects.ts:3
packages/insomnia-vcs/src/session.ts:1 imports insomnia-api, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/src/session.ts:1
packages/insomnia-vcs/src/session.ts:3 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/src/session.ts:3
packages/insomnia-vcs/src/store/drivers/graceful-rename.ts:3 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/src/store/drivers/graceful-rename.ts:3
packages/insomnia-vcs/src/util.ts:5 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/src/util.ts:5
packages/insomnia-vcs/src/util.ts:6 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia-vcs/src/util.ts:6
packages/insomnia/setup-vitest.ts:1 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/insomnia/setup-vitest.ts:1
What to do
Fix the listed violations: declare the workspace packages these files import in the importing package's own REDACTED dependencies (470 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (20 rows); move the shared test helper into a source directory production code may depend on (2 rows).
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.
toPreRequestAuth has cyclomatic complexity 87 and cognitive complexity 88; 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/insomnia-scripting-environment/src/objects/auth.ts:597
ProjectSettingsForm has cyclomatic complexity 86 and cognitive complexity 71; 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/insomnia/src/ui/components/project/project-settings-form.tsx:78
SpecView has cyclomatic complexity 77 and cognitive complexity 70; 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/insomnia/src/ui/components/spec-view.tsx:136
clientAction has cyclomatic complexity 62 and cognitive complexity 128; 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/insomnia/src/routes/organization.$organizationId.project.$projectId.update.tsx:48
run has cyclomatic complexity 57 and cognitive complexity 81; 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/insomnia/src/common/templating/local-template-tags.ts:570
map has cyclomatic complexity 57 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. — packages/insomnia/src/sync/git/git-vcs.ts:665
threeWayMerge has cyclomatic complexity 56 and cognitive complexity 53; 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/insomnia-vcs/src/util.ts:67
canDrop has cyclomatic complexity 53 and cognitive complexity 75; 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/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:252
traversePluginPath has cyclomatic complexity 52 and cognitive complexity 84; 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/insomnia/src/plugins/index.ts:189
SyncDropdown has cyclomatic complexity 50 and cognitive complexity 45; 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/insomnia/src/ui/components/dropdowns/sync-dropdown.tsx:42
(anonymous) has cyclomatic complexity 49 and cognitive complexity 73; 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/insomnia/src/root.tsx:458
(anonymous) has cyclomatic complexity 48 and cognitive complexity 58; 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/insomnia/src/common/insomnia-v5.ts:675
GitProjectSyncDropdown has cyclomatic complexity 48 and cognitive complexity 35; 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/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:52
(anonymous) has cyclomatic complexity 44 and cognitive complexity 61; 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/insomnia/src/ui/components/templating/tag-editor.tsx:371
createConfiguredCurlInstance has cyclomatic complexity 43 and cognitive complexity 70; 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/insomnia/src/main/network/libcurl-promise.ts:344
clientAction has cyclomatic complexity 42 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/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.new.tsx:41
onMove has cyclomatic complexity 41 and cognitive complexity 64; 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/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:693
HeaderPlanIndicator has cyclomatic complexity 41 and cognitive complexity 38; 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/insomnia/src/ui/components/header-plan-indicator.tsx:23
GitSyncDropdown has cyclomatic complexity 41 and cognitive complexity 30; 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/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:43
(anonymous) has cyclomatic complexity 40 and cognitive complexity 76; 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/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:183
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files6.6 / 10Adequate✓ 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.
packages/insomnia/src/main/git-service.ts has 3782 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/insomnia/src/main/git-service.ts:1
packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx has 2146 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/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:1
packages/insomnia/src/sync/git/git-vcs.ts has 1977 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/insomnia/src/sync/git/git-vcs.ts:1
packages/insomnia/src/common/insomnia-v5.ts has 1437 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/insomnia/src/common/insomnia-v5.ts:1
packages/insomnia/src/ui/components/spec-view.tsx has 1367 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/insomnia/src/ui/components/spec-view.tsx:1
packages/insomnia-vcs/src/vcs.ts has 1272 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/insomnia-vcs/src/vcs.ts:1
packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx has 1199 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/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:1
packages/insomnia/src/sync/git/repo-file-watcher.ts has 1194 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/insomnia/src/sync/git/repo-file-watcher.ts:1
packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx has 1151 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/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:1
packages/insomnia/src/main/templating-worker-database.ts has 1090 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/insomnia/src/main/templating-worker-database.ts:1
REDACTED has 1006 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
packages/insomnia/src/ui/components/settings/import-export.tsx has 972 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/insomnia/src/ui/components/settings/import-export.tsx:1
packages/insomnia/src/common/templating/local-template-tags.ts has 960 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/insomnia/src/common/templating/local-template-tags.ts:1
REDACTED has 944 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
packages/insomnia/src/common/render.ts has 931 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/insomnia/src/common/render.ts:1
packages/insomnia/src/ui/components/example-openapi-specs.ts has 920 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/insomnia/src/ui/components/example-openapi-specs.ts:1
packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx has 888 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/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:1
packages/insomnia/src/main/ipc/main.ts has 879 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/insomnia/src/main/ipc/main.ts:1
packages/insomnia/src/main/importers/importers/postman.ts has 854 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/insomnia/src/main/importers/importers/postman.ts:1
REDACTED has 838 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
packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx has 827 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/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:1
packages/insomnia/src/root.tsx 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. — packages/insomnia/src/root.tsx:1
packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx has 799 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/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:1
packages/insomnia/src/common/import.ts has 797 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/insomnia/src/common/import.ts:1
packages/insomnia-scripting-environment/src/objects/auth.ts has 761 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/insomnia-scripting-environment/src/objects/auth.ts:1
packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx has 744 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/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx:1
packages/insomnia/src/ui/components/project/project-settings-form.tsx has 741 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/insomnia/src/ui/components/project/project-settings-form.tsx:1
packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx has 738 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/insomnia/src/ui/components/modals/new-workspace-modal.tsx:1
packages/insomnia/src/ui/components/templating/tag-editor.tsx has 734 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/insomnia/src/ui/components/templating/tag-editor.tsx:1
packages/insomnia/src/main/importers/importers/openapi-3.ts has 731 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/insomnia/src/main/importers/importers/openapi-3.ts:1
packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx has 727 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/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:1
packages/insomnia/src/ui/components/settings/plugins.tsx has 720 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/insomnia/src/ui/components/settings/plugins.tsx:1
packages/insomnia/src/konnect/sync.ts has 697 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/insomnia/src/konnect/sync.ts:1
packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx has 681 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/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx:1
REDACTED has 679 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
packages/insomnia-scripting-environment/src/objects/request.ts has 677 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/insomnia-scripting-environment/src/objects/request.ts:1
packages/insomnia/src/ui/components/settings/credentials.tsx has 672 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/insomnia/src/ui/components/settings/credentials.tsx:1
packages/insomnia/src/plugins/index.ts has 666 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/insomnia/src/plugins/index.ts:1
REDACTED has 650 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
packages/insomnia/src/ui/components/mcp/mcp-pane.tsx has 648 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/insomnia/src/ui/components/mcp/mcp-pane.tsx: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 Coverage6.3 / 10Adequate✓ 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) — packages/insomnia/src/ui/components/spec-view.tsx:1, packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:1, packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx: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 REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code8.0 / 10Strong✓ 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.
1281 file(s) (~207972 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/insomnia/src/routes/git.log.tsx imports './+types/git.log', 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. — packages/insomnia
14 file(s) (~785 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/insomnia-testing
Nothing imports this binding — it is safe to review for removal. (×38) — packages/insomnia-scripting-environment/src/objects/auth.ts:190, packages/insomnia-vcs/src/__schemas__/type-schemas.ts:25, packages/insomnia-vcs/src/__schemas__/type-schemas.ts:57, …
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 only as a TYPE and declared in no reachable REDACTED. 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 REDACTED. (×7) — packages/insomnia/src/ui/components/icon.tsx:1, packages/insomnia/src/ui/components/base/dropdown/dropdown.tsx:2, packages/insomnia/src/ui/components/base/dropdown/dropdown.tsx:3, …
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×18) — packages/insomnia/src/ui/components/rjsf/theme.tsx:1, packages/insomnia/src/ui/components/base/dropdown/dropdown.tsx:1, packages/insomnia/src/ui/components/base/dropdown/index.ts:1, …
Declared in the root REDACTED 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.
Declared in packages/insomnia-component-docs/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. (×2)
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.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×12) — packages/insomnia-data/node-src/services/cookie-jar.ts:24, packages/insomnia-data/node-src/services/environment.ts:82, packages/insomnia-vcs/src/util.ts:476, …
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 12 sites, not one: `packages/insomnia-data/node-src/services/cookie-jar.ts:24` (createHash("sha1")), `packages/insomnia-data/node-src/services/environment.ts:82` (createHash("sha1")), `packages/insomnia-vcs/src/util.ts:476` (createHash("sha1")), `packages/insomnia-vcs/src/vcs.ts:45` (createHash("sha1")), `packages/insomnia-vcs/src/vcs.ts:1472` (createHash("sha1")), `packages/insomnia/src/main/importers/importers/openapi-3.ts:149` (createHash("sha1")), `packages/insomnia/src/main/importers/importers/openapi-3.ts:237` (createHash("sha1")), `packages/insomnia/src/main/importers/importers/openapi-3.ts:665` (createHash("sha1")), and 4 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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.
The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. (×11) — packages/insomnia-vcs/src/store/drivers/file-system-driver.ts:81, packages/insomnia-scripting-environment/src/objects/send-request.ts:18, packages/insomnia/src/entry.preload.ts:363, …
`forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. (×5) — packages/insomnia-data/node-src/services/environment.ts:55, packages/insomnia/src/ui/hooks/use-close-connection.ts:40, packages/insomnia/src/ui/hooks/use-close-connection.ts:51, …
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 stream5.3 / 10Adequate✓ Tool-verified
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.
`spawn` pipes `stderr` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `proc.stderr`, while `proc.stdout` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stderr (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`proc.stderr.on('data', …)`, or `proc.stderr.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot. — packages/insomnia/src/sync/git/utils.ts:100
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
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 document1.6 / 10Critical✓ Tool-verified
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.
`deterministicStringify` is exported and takes `value: any` from its caller, and it calls itself at line 8 (`deterministicStringify`) with a piece of `value` (and at line 9, line 21) — and nowhere in `deterministicStringify` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deterministicStringify` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/insomnia-data/common-src/deterministic-stringify.ts:8
`valuesEqual` is exported, takes a document from its caller (line 119) and hands it to `sortDeep`, which calls itself at line 96 (`sortDeep`) with a piece of `value` (and at line 102) — and nowhere in `sortDeep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sortDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/insomnia/src/ui/components/modals/visual-diff/diff-engine.ts:96
`checkNestedKeys` is exported and takes `obj: Record<string, any>` from its caller, and it calls itself at line 50 (`checkNestedKeys`) with a piece of `obj` — and nowhere in `checkNestedKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `checkNestedKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/insomnia/src/common/utils/environment-utils.ts:50
`getKeys` is exported and takes `obj: any` from its caller, and it calls itself at line 24 (`getKeys`) with a piece of `obj` (and at line 30) — and nowhere in `getKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:24
`collectLeafValues` is exported and takes `value: any` from its caller, and it calls itself at line 136 (`collectLeafValues`) with a piece of `value` (and at line 140) — and nowhere in `collectLeafValues` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collectLeafValues` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/insomnia/src/common/network/sensitive-value-collector.ts:136
`normalizePropertyOrder` is exported and takes `obj: any` from its caller, and it calls itself at line 152 (`normalizePropertyOrder`) with a piece of `obj` (and at line 172) — and nowhere in `normalizePropertyOrder` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `normalizePropertyOrder` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/insomnia/src/common/insomnia-schema-migrations/index.ts:152
`cleanHeadersAndParameters` is exported and takes `obj: any` from its caller, and it calls itself at line 69 (`cleanHeadersAndParameters`) with a piece of `obj` (and at line 127, line 140, line 158) — and nowhere in `cleanHeadersAndParameters` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `cleanHeadersAndParameters` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/insomnia/src/common/insomnia-schema-migrations/v5.1.ts:69
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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 async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 7/15 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`readFileFromPathOrUrl` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:197
`updateGitProjectCount` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/insomnia-api/src/project.ts:74
`decodeBase64` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/insomnia/src/ui/auth-session-provider.client.ts:31
`onComplete` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/insomnia/src/ui/components/design-empty-state.tsx:80
`sendRequestViaFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/insomnia/src/scripting/quickjs-script-engine.ts:279
`validatePat` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/insomnia/src/konnect/api.ts:125
`fetchImportContentFromURI` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/insomnia/src/common/import.ts:82
`fetchFromTemplateWorkerDatabase` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/insomnia/src/common/templating/liquid-extension-worker.ts:49
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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.
`debug` at line 1033 is called with an argument built by `join(' ')` (line 1033), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — REDACTED:1033
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped4.3 / 10Weak✓ 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.
`compiled` 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. — packages/insomnia/src/ui/components/markdown-preview.tsx:62
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.
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 element3.5 / 10Weak✓ Tool-verified
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.
This loop runs once per element of `moves`, and the statement it guards acts on the element it is on — `moves[j]`. The test deciding whether that statement runs does not: `b > a` reads `moves[i]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 29, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — packages/insomnia/src/ui/utils.ts:33
What to do
Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×31) — packages/insomnia-vcs/src/vcs.ts:187, packages/insomnia-vcs/src/vcs.ts:201, packages/insomnia-vcs/src/vcs.ts:229, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — packages/insomnia-data/common-src/ndjson.ts:22, packages/insomnia/src/ui/plugins/misc.ts:32, packages/insomnia/src/ui/components/editors/auth/o-auth-2-auth.tsx:474, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×5) — packages/insomnia/src/ui/hooks/use-command-search.ts:44, packages/insomnia/src/ui/hooks/use-command-search.ts:117, packages/insomnia/src/ui/hooks/use-command-search.ts:131, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~1.2 `!` null assertions per 1k TypeScript source lines — 211 assertion(s) across the 176805 source line(s) of the 1217 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/insomnia/src/ui/components/project/project-settings-form.tsx (17), packages/insomnia/src/ui/components/workspace/use-workspace-breadcrumb.tsx (10), packages/insomnia/src/konnect/sync.ts (9). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
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 — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 15 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 — 44 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence 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 a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .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
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.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) — 17 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.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication. The rest — .cpp (254 lines, 0.2% of production source) — is compared by neither card, so duplication there is unmeasured; it is a corner of this repository, not its product.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (5 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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.
AC2 · Forms & labels· <input> without a programmatic label · ×8
<input> without a programmatic label packages/insomnia/src/routes/auth.authorize.tsx:108— 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 packages/insomnia/src/routes/auth.authorize.tsx:141— 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 packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:544— 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 packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:576— 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 packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:175— 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 packages/insomnia/src/ui/components/mcp/mcp-roots-panel.tsx:95— 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 packages/insomnia/src/ui/components/modals/cloud-credential-modal/cloud-credential-modal.tsx:170— 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 packages/insomnia/src/ui/components/modals/cloud-credential-modal/cloud-credential-modal.tsx:192— 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.
AC2 · Forms & labels· <button> with no accessible text · ×6
<button> with no accessible text packages/insomnia/src/ui/components/editors/auth/components/auth-input-row.tsx:135— 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).
<button> with no accessible text packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:182— 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).
<button> with no accessible text packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:252— 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).
<button> with no accessible text packages/insomnia/src/ui/components/key-value-editor/row.tsx:75— 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).
<button> with no accessible text packages/insomnia/src/ui/components/key-value-editor/row.tsx:200— 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).
<button> with no accessible text packages/insomnia/src/ui/components/key-value-editor/row.tsx:210— 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 <span> · ×6
Click handler on a non-interactive <span> packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:675— 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> packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:680— 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> packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:684— 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> packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:744— 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> packages/insomnia/src/ui/components/settings/llms/gguf.tsx:142— 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> packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:904— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels· <label> that labels no control · ×4
<label> that labels no control packages/insomnia/src/ui/components/editors/body/file-editor.tsx:30— 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 packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:132— 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 packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:126— 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 packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:172— 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.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×4
Click handler on a non-interactive <div> packages/insomnia/src/ui/components/modals/import-modal/import-projects-modal.tsx:339— 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> packages/insomnia/src/ui/components/panes/runner-result-history-pane.tsx:61— 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> packages/insomnia/src/ui/components/settings/plugins.tsx:577— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> packages/insomnia/src/ui/components/settings/plugins.tsx:626— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Import cycle (3 files) packages/insomnia/src/sync/git/providers/github.ts:9— packages/insomnia/src/sync/git/providers/github.ts → packages/insomnia/src/sync/git/utils.ts → packages/insomnia/src/sync/git/providers/index.ts → packages/insomnia/src/sync/git/providers/github.ts (one verified cycle inside a mutually-dependent group of 4 files)
AC4 · Keyboard semantics· Double-click handler on a non-interactive <div> · ×3
Double-click handler on a non-interactive <div> packages/insomnia/src/ui/components/editable-input.tsx:79— This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Double-click handler on a non-interactive <div> packages/insomnia/src/ui/components/settings/vault-key-panel.tsx:45— This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Double-click handler on a non-interactive <div> packages/insomnia/src/ui/components/tabs/tab.tsx:179— This <div> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
AC1 · Text alternatives· <img> without a text alternative · ×2
<img> without a text alternative packages/insomnia/src/routes/git-migration.$.tsx:210— 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 packages/insomnia/src/ui/components/viewers/response-viewer.tsx:284— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D10 · Test Quality· No assertions (empty test) · ×2
No assertions (empty test): t1 packages/insomnia-scripting-environment/src/objects/__tests__/test.test.ts:14— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): fast packages/insomnia-scripting-environment/src/objects/__tests__/test.test.ts:60— Test method has an empty body — it asserts nothing and exercises no code.
Unlisted import '@stoplight/spectral-runtime' packages/insomnia/src/main/lint-process.mjs:11— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@stoplight/spectral-runtime' packages/insomnia-inso/src/commands/lint-specification.ts:12— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'es-toolkit' packages/insomnia/src/common/templating/render-error.ts:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'es-toolkit' REDACTED:10— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
AC4 · Keyboard semantics· Click handler on a non-interactive <i> · ×1
Click handler on a non-interactive <i> packages/insomnia/src/ui/components/viewers/password-viewer.tsx:40— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC5 · ARIA correctness· aria-expanded on a <div> with no role to carry it · ×1
aria-expanded on a <div> with no role to carry it packages/insomnia/src/ui/components/spec-view.tsx:914— A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded.
Boundary-crossing change coupling: interfaces.ts ↔ request-script-editor.tsx packages/insomnia-scripting-environment/src/objects/interfaces.ts:1— `packages/insomnia-scripting-environment/src/objects/interfaces.ts` (context insomnia-scripting-environment) and `packages/insomnia/src/ui/components/editors/request-script-editor.tsx` (context insomnia) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `3a49afbe` Add global base environment support in script[INS-5544] (#8734); `3e9ead3b` feat(sdk): enable folder env interfaces for manipulation in script (#… (at that commit the file was still `packages/insomnia-sdk/src/objects/interfaces.ts`); `8fad1200` fix(runner): extend insomnia.variables.set lifetime to whole executio… (at that commit the file was still `packages/insomnia-sdk/src/objects/interfaces.ts`) — run `git show` on any of them.
Unlisted import '@internationalized/date' packages/insomnia/src/ui/components/rjsf/theme.tsx:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@react-aria/interactions' packages/insomnia/src/ui/components/base/dropdown/dropdown.tsx:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@react-stately/collections' packages/insomnia/src/ui/components/base/dropdown/index.ts:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'cheerio' packages/insomnia/src/scripting/require-interceptor.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'crypto-js' packages/insomnia/src/scripting/require-interceptor.ts:4— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'csv-parse' packages/insomnia/src/scripting/require-interceptor.ts:5— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'diff' packages/insomnia/src/sync/git/git-vcs.ts:4— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'moment' packages/insomnia/src/scripting/require-interceptor.ts:7— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'protobufjs' packages/insomnia/src/main/ipc/__tests__/automock.test.ts:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'tv4' packages/insomnia/src/scripting/require-interceptor.ts:8— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'xml2js' packages/insomnia/src/scripting/require-interceptor.ts:10— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@stoplight/spectral-ref-resolver' packages/insomnia-inso/src/commands/lint-specification.ts:10— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'uuid' packages/insomnia-inso/src/analytics.ts:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
FunctionTooLong: new-workspace-modal.NewWorkspaceModal packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx:52— FunctionTooLong — NewWorkspaceModal runs 623 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 523 over it, 6.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.Runner packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:155— FunctionTooLong — Runner runs 613 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 513 over it, 6.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: git-project-sync-dropdown.GitProjectSyncDropdown packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:52— FunctionTooLong — GitProjectSyncDropdown runs 609 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 509 over it, 6.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: organization.$organizationId.project.$projectId._index.Component packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:79— FunctionTooLong — Component runs 553 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 453 over it, 5.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.
FunctionTooLong: cli.go REDACTED:265— FunctionTooLong — go runs 550 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 450 over it, 5.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: command-palette.CommandPaletteCombobox packages/insomnia/src/ui/components/command-palette.tsx:102— FunctionTooLong — CommandPaletteCombobox runs 455 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 355 over it, 4.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.
FunctionTooLong: graph-ql-editor.GraphQLEditor packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx:232— FunctionTooLong — GraphQLEditor runs 441 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 341 over it, 4.41× 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: workspace-environments-edit-modal.WorkspaceEnvironmentsEditModal packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx:44— FunctionTooLong — WorkspaceEnvironmentsEditModal runs 426 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 326 over it, 4.26× 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: grpc-request-pane.GrpcRequestPane packages/insomnia/src/ui/components/panes/grpc-request-pane.tsx:62— FunctionTooLong — GrpcRequestPane runs 395 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 295 over it, 3.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: request-settings-modal.RequestSettingsModal packages/insomnia/src/ui/components/modals/request-settings-modal.tsx:49— FunctionTooLong — RequestSettingsModal runs 386 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 286 over it, 3.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: git-staging-modal.GitStagingModal packages/insomnia/src/ui/components/modals/git-staging-modal.tsx:30— FunctionTooLong — GitStagingModal runs 384 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 284 over it, 3.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: main.registerMainHandlers packages/insomnia/src/main/ipc/main.ts:384— FunctionTooLong — registerMainHandlers runs 377 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 277 over it, 3.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: insomnia-v5.getInsomniaV5DataExport packages/insomnia/src/common/insomnia-v5.ts:1043— FunctionTooLong — getInsomniaV5DataExport runs 373 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 273 over it, 3.73× 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: git-sync-dropdown.GitSyncDropdown packages/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:43— FunctionTooLong — GitSyncDropdown runs 367 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 267 over it, 3.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: mcp-pane.McpPane packages/insomnia/src/ui/components/mcp/mcp-pane.tsx:89— FunctionTooLong — McpPane runs 367 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 267 over it, 3.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: insomnia-tab-context.InsomniaTabProvider packages/insomnia/src/ui/context/app/insomnia-tab-context.tsx:60— FunctionTooLong — InsomniaTabProvider runs 367 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 267 over it, 3.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sync-dropdown.SyncDropdown packages/insomnia/src/ui/components/dropdowns/sync-dropdown.tsx:42— FunctionTooLong — SyncDropdown runs 355 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 255 over it, 3.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.
FunctionTooLong: database-nedb.createNedbDatabase packages/insomnia-data/node-src/database/database-nedb.ts:47— FunctionTooLong — createNedbDatabase runs 350 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 250 over it, 3.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: window-utils.createWindow REDACTED:204— FunctionTooLong — createWindow runs 343 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 243 over it, 3.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: root.Root packages/insomnia/src/root.tsx:345— FunctionTooLong — Root runs 341 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 241 over it, 3.41× 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: project-create-form.ProjectCreateForm packages/insomnia/src/ui/components/project/project-create-form.tsx:40— FunctionTooLong — ProjectCreateForm runs 338 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 238 over it, 3.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: url.Url packages/insomnia/src/ui/components/settings/llms/url.tsx:40— FunctionTooLong — Url runs 336 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 236 over it, 3.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sync-staging-modal.SyncStagingModal packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx:113— FunctionTooLong — SyncStagingModal 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: request-pane.RequestPane packages/insomnia/src/ui/components/panes/request-pane.tsx:44— FunctionTooLong — RequestPane runs 324 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 224 over it, 3.24× 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: sidebar-workspace-dropdown.SidebarWorkspaceDropdown packages/insomnia/src/ui/components/dropdowns/sidebar-workspace-dropdown.tsx:77— FunctionTooLong — SidebarWorkspaceDropdown runs 319 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 219 over it, 3.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.
TodoComment packages/insomnia-vcs/src/crypt.ts:79— // TODO: Add assertion checks for JWK — 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/insomnia-vcs/src/crypt.ts:110— // TODO: Add assertion checks for JWK — 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/insomnia-vcs/src/crypt.ts:142— // TODO: Add assertion checks for JWK — 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/insomnia-vcs/src/crypt.ts:171— // TODO: Add assertion checks for JWK — 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/insomnia-vcs/src/session.ts:7— // TODO: This is a temporary solution to get the private key from the session. — 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/insomnia-vcs/src/vcs.ts:536— // TODO: Fix server returning null instead of empty list — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/insomnia-vcs/src/vcs.ts:641— // TODO: may be we can create another push function for initial push, so that we can reduce some api 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/insomnia-vcs/src/store/drivers/memory-driver.ts:3— // TODO: unsound definite property assignment assertion — 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/insomnia-smoke-test/tests/smoke/design-interactions.test.ts:47— // TODO(filipe) - add this in another PR — 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/insomnia-smoke-test/tests/smoke/pre-request-script-features.test.ts:315— // TODO: try to understand why this breaks the test — 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/insomnia-smoke-test/tests/smoke/quickjs-script-sandbox.test.ts:22— // TODO(INS-3890): re-enable once the QuickJS sandbox setting is un-hidden in scripting-settings.tsx.
TodoComment packages/insomnia-smoke-test/tests/smoke/quickjs-sendrequest-bridge.test.ts:15— // TODO(INS-3890): re-enable once the QuickJS sandbox setting is un-hidden in scripting-settings.tsx.
TodoComment packages/insomnia-smoke-test/tests/migration/local-to-cloud-projects.test.ts:42— // // Open migrated local migrated collection that should have Git Sync - TODO - Fix this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/insomnia-scripting-environment/src/objects/async-objects.ts:32— // TODO: super.any seems not supported for the compile target (es2021) — 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/insomnia-scripting-environment/src/objects/async-objects.ts:62— // TODO: Promise.any seems not supported for the compile target (es2021) — 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/insomnia-scripting-environment/src/objects/auth.ts:567— // TODO(george): some keys are lost here, see if we can support them in Insomnia — 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/insomnia-scripting-environment/src/objects/auth.ts:588— // TODO(george): support this in the script side — 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/insomnia-scripting-environment/src/objects/auth.ts:780— // TODO(george): these fields are not supported in Insomnia side — 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/insomnia-scripting-environment/src/objects/auth.ts:805— // 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/insomnia-scripting-environment/src/objects/auth.ts:809— // 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/insomnia-scripting-environment/src/objects/console.ts:38— // TODO: support replacing substitution — 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/insomnia-scripting-environment/src/objects/cookies.ts:232— // TODO: its format from Insomnia is unknown — 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/insomnia-scripting-environment/src/objects/cookies.ts:294— // TODO: create a better method for setting cookie, or overload the above method — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/insomnia-scripting-environment/src/objects/environments.ts:196— // TODO: support vars for all levels — 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/insomnia-scripting-environment/src/objects/headers.ts:248— // TODO: handle special characters — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Hotspot: packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:82— packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 203 in project-navigation-sidebar.ProjectNavigationSidebarInner at line 82. 7 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/templating/tag-editor.tsx packages/insomnia/src/ui/components/templating/tag-editor.tsx:78— packages/insomnia/src/ui/components/templating/tag-editor.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 131 in tag-editor.TagEditor at line 78. 3 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/templating/tag-editor.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:430— packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in git-project-staging-modal.GeneratedCommitsForm at line 430. 4 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:79— packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 81 in organization.$organizationId.project.$projectId._index.Component at line 79. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:52— packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 103 in git-project-sync-dropdown.GitProjectSyncDropdown at line 52. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/main/git-service.ts packages/insomnia/src/main/git-service.ts:1417— packages/insomnia/src/main/git-service.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in git-service.cloneGitRepoAction at line 1417. 7 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/main/git-service.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/root.tsx packages/insomnia/src/root.tsx:345— packages/insomnia/src/root.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in root.Root at line 345. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/root.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/project/project-settings-form.tsx packages/insomnia/src/ui/components/project/project-settings-form.tsx:78— packages/insomnia/src/ui/components/project/project-settings-form.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 136 in project-settings-form.ProjectSettingsForm at line 78. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/project/project-settings-form.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/common/insomnia-v5.ts packages/insomnia/src/common/insomnia-v5.ts:665— packages/insomnia/src/common/insomnia-v5.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in insomnia-v5.getCollection at line 665. 4 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/common/insomnia-v5.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/common/render.ts packages/insomnia/src/common/render.ts:600— packages/insomnia/src/common/render.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in render.render at line 600. 5 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/common/render.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:155— packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 82 in organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.Runner at line 155. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:205— packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 63 in import-modal.ImportModal at line 205. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx:66— packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in key-value-editor.EnvironmentKVEditor at line 66. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/spec-view.tsx packages/insomnia/src/ui/components/spec-view.tsx:136— packages/insomnia/src/ui/components/spec-view.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 139 in spec-view.SpecView at line 136. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/spec-view.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:489— REDACTED changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in network.tryToExecuteScript at line 489. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx:164— packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.Debug at line 164. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:595— packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in use-sidebar-drag-and-drop.useSidebarDragAndDrop at line 595. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/modals/visual-diff/entity-diff-list.tsx packages/insomnia/src/ui/components/modals/visual-diff/entity-diff-list.tsx:64— packages/insomnia/src/ui/components/modals/visual-diff/entity-diff-list.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in entity-diff-list.EntityDiffList at line 64. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/modals/visual-diff/entity-diff-list.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/sync/git/git-vcs.ts packages/insomnia/src/sync/git/git-vcs.ts:346— packages/insomnia/src/sync/git/git-vcs.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in GitVCS.fileStatus at line 346. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/sync/git/git-vcs.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:62— packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.Component at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx:44— packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in workspace-environments-edit-modal.WorkspaceEnvironmentsEditModal at line 44. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/dropdowns/sidebar-workspace-dropdown.tsx packages/insomnia/src/ui/components/dropdowns/sidebar-workspace-dropdown.tsx:77— packages/insomnia/src/ui/components/dropdowns/sidebar-workspace-dropdown.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in sidebar-workspace-dropdown.SidebarWorkspaceDropdown at line 77. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/dropdowns/sidebar-workspace-dropdown.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/ui/components/project/project-create-form.tsx packages/insomnia/src/ui/components/project/project-create-form.tsx:40— packages/insomnia/src/ui/components/project/project-create-form.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in project-create-form.ProjectCreateForm at line 40. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/project/project-create-form.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/main/network/curl.ts packages/insomnia/src/main/network/curl.ts:137— packages/insomnia/src/main/network/curl.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in curl.openCurlConnection at line 137. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/main/network/curl.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/insomnia/src/plugins/index.ts packages/insomnia/src/plugins/index.ts:189— packages/insomnia/src/plugins/index.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in index.traversePluginPath at line 189. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/plugins/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: main/git-service.ts packages/insomnia/src/main/git-service.ts— FileTooLong — 2660 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2160 over it, 5.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: modals/git-project-staging-modal.tsx packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx— FileTooLong — 1826 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1326 over it, 3.65× 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: git/git-vcs.ts packages/insomnia/src/sync/git/git-vcs.ts— FileTooLong — 1392 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: GitVCS (150-2195). The bar is 500 significant lines; this is 892 over it, 2.78× 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: common/insomnia-v5.ts packages/insomnia/src/common/insomnia-v5.ts— FileTooLong — 985 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 485 over it, 1.97× 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: routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx— FileTooLong — 954 significant lines (blank, comment-only and punctuation-only lines excluded), about 64% of them inside a single declaration: Runner (155-933). The bar is 500 significant lines; this is 454 over it, 1.91× 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/vcs.ts packages/insomnia-vcs/src/vcs.ts— FileTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: VCS (96-1468). The bar is 500 significant lines; this is 416 over it, 1.83× 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: project-navigation-sidebar/project-navigation-sidebar.tsx packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx— FileTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: ProjectNavigationSidebarInner (82-1274). The bar is 500 significant lines; this is 416 over it, 1.83× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 814 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 314 over it, 1.63× 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: settings/import-export.tsx packages/insomnia/src/ui/components/settings/import-export.tsx— FileTooLong — 797 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 297 over it, 1.59× 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: main/templating-worker-database.ts packages/insomnia/src/main/templating-worker-database.ts— FileTooLong — 775 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 275 over it, 1.55× 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 — 748 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: go (265-1047). The bar is 500 significant lines; this is 248 over it, 1.50× 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: import-modal/import-modal.tsx packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx— FileTooLong — 711 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 211 over it, 1.42× 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: ipc/main.ts packages/insomnia/src/main/ipc/main.ts— FileTooLong — 704 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 204 over it, 1.41× 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: modals/new-workspace-modal.tsx packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx— FileTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: NewWorkspaceModal (52-779). The bar is 500 significant lines; this is 167 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: git/repo-file-watcher.ts packages/insomnia/src/sync/git/repo-file-watcher.ts— FileTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: RepoFileWatcher (103-1258). The bar is 500 significant lines; this is 164 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: dropdowns/git-project-sync-dropdown.tsx packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: GitProjectSyncDropdown (52-859). The bar is 500 significant lines; this is 156 over it, 1.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: importers/postman.ts packages/insomnia/src/main/importers/importers/postman.ts— FileTooLong — 646 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: ImportPostman (141-962). The bar is 500 significant lines; this is 146 over it, 1.29× 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: templating/local-template-tags.ts packages/insomnia/src/common/templating/local-template-tags.ts— FileTooLong — 641 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 141 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: project/project-settings-form.tsx packages/insomnia/src/ui/components/project/project-settings-form.tsx— FileTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 138 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: settings/plugins.tsx packages/insomnia/src/ui/components/settings/plugins.tsx— FileTooLong — 634 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 134 over it, 1.27× 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: common/render.ts packages/insomnia/src/common/render.ts— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 124 over it, 1.25× 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: routes/organization.$organizationId.project.$projectId._index.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: Component (79-758). The bar is 500 significant lines; this is 124 over it, 1.25× 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/root.tsx packages/insomnia/src/root.tsx— FileTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 123 over it, 1.25× 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: project-navigation-sidebar/use-sidebar-drag-and-drop.tsx packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx— FileTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 119 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: common/import.ts packages/insomnia/src/common/import.ts— FileTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 116 over it, 1.23× 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.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-data/node-src/services/organization.ts:1— packages/insomnia-data/node-src/services/organization.ts:1 imports insomnia-api, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-data/node-src/services/project.ts:1— packages/insomnia-data/node-src/services/project.ts:1 imports insomnia-api, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-inso/src/analytics.ts:3— packages/insomnia-inso/src/analytics.ts:3 imports insomnia/src/common/constants, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-inso/src/analytics.ts:4— packages/insomnia-inso/src/analytics.ts:4 imports insomnia-analytics, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:11— REDACTED:11 imports insomnia/src/common/configure-v3-client, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:12— REDACTED:12 imports insomnia/src/common/constants, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:13— REDACTED:13 imports insomnia/src/common/insomnia-fetch, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:14— REDACTED:14 imports insomnia/src/network/send-request.node, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:15— REDACTED:15 imports insomnia/src/runtimes, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:16— REDACTED:16 imports insomnia/src/runtimes/runtime.node, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:17— REDACTED:17 imports insomnia-api, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:26— REDACTED:26 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:27— REDACTED:27 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:28— REDACTED:28 imports insomnia-data/node, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:29— REDACTED:29 imports insomnia-testing/src/generate/generate, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] REDACTED:30— REDACTED:30 imports insomnia-testing/src/run/run, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-inso/src/commands/lint-specification.ts:14— packages/insomnia-inso/src/commands/lint-specification.ts:14 imports insomnia/src/main/bundle-spectral-ruleset, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-inso/src/commands/lint-specification.ts:15— packages/insomnia-inso/src/commands/lint-specification.ts:15 imports insomnia/src/main/private-host, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-inso/src/commands/run-collection/result-report.ts:15— packages/insomnia-inso/src/commands/run-collection/result-report.ts:15 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-inso/src/db/adapters/git-adapter.ts:4— packages/insomnia-inso/src/db/adapters/git-adapter.ts:4 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-inso/src/db/adapters/insomnia-adapter.ts:4— packages/insomnia-inso/src/db/adapters/insomnia-adapter.ts:4 imports insomnia/src/common/insomnia-v5, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-scripting-environment/src/objects/insomnia.ts:3— packages/insomnia-scripting-environment/src/objects/insomnia.ts:3 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-scripting-environment/src/objects/interpolator.ts:1— packages/insomnia-scripting-environment/src/objects/interpolator.ts:1 imports insomnia-data/common, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-scripting-environment/src/objects/request.ts:9— packages/insomnia-scripting-environment/src/objects/request.ts:9 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] packages/insomnia-scripting-environment/src/objects/response.ts:3— packages/insomnia-scripting-environment/src/objects/response.ts:3 imports insomnia-data, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file packages/insomnia/src/ui/components/spec-view.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 packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.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 packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.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 packages/insomnia/src/main/ipc/main.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 packages/insomnia/src/ui/components/example-openapi-specs.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 packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.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 packages/insomnia/src/ui/components/editors/body/graph-ql-editor.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 packages/insomnia/src/ui/components/project/project-settings-form.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 packages/insomnia/src/ui/components/modals/new-workspace-modal.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 packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.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 packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.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 packages/insomnia/src/main/network/websocket.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 packages/insomnia/src/ui/components/command-palette.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 packages/insomnia/src/ui/components/mcp/mcp-pane.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 packages/insomnia/src/ui/components/editors/auth/o-auth-2-auth.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 packages/insomnia/src/main/network/socket-io.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 packages/insomnia/src/ui/components/first-request-creation.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 packages/insomnia/src/ui/components/modals/cookies-modal.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 packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.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 packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.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 packages/insomnia/src/entry.preload.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 packages/insomnia/src/ui/components/websockets/realtime-response-pane.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 packages/insomnia/src/ui/components/request-url-bar.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 packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.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 packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.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.
Swallowed exception (empty catch) packages/insomnia-vcs/src/vcs.ts:187— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia-vcs/src/vcs.ts:201— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia-vcs/src/vcs.ts:229— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia-vcs/src/vcs.ts:780— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia-vcs/src/store/drivers/graceful-rename.ts:44— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia-inso/src/analytics.ts:53— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia-inso/src/analytics.ts:77— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:911— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/esbuild.entrypoints.ts:30— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/organization-utils.ts:115— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/utils/first-request-treatment.ts:66— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/utils/first-request-treatment.ts:97— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/utils/first-request-treatment.ts:121— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/utils/router.ts:143— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/utils/prettify/json.ts:38— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/hooks/use-command-search.ts:44— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/hooks/use-command-search.ts:117— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/hooks/use-command-search.ts:131— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/components/error-boundary.tsx:40— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/components/error-boundary.tsx:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/components/websockets/event-view.tsx:59— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/components/viewers/response-viewer.tsx:147— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/components/viewers/response-viewer.tsx:159— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/components/viewers/response-viewer.tsx:245— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/insomnia/src/ui/components/project/utils.tsx:45— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Sync-over-async blocking REDACTED:563— `fs.existsSync` in `callback to action` 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:564— `fs.statSync` in `callback to action` 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:570— `fs.accessSync` in `callback to action` 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 packages/insomnia-inso/src/db/adapters/insomnia-adapter.ts:69— `fs.existsSync` in `DbAdapter` 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 packages/insomnia-inso/src/db/adapters/insomnia-adapter.ts:69— `fs.lstatSync` in `DbAdapter` 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 packages/insomnia-smoke-test/playwright/paths.ts:21— `fs.existsSync` in `copyFixtureDatabase` 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 packages/insomnia-smoke-test/playwright/utils/file-operations.ts:37— `fs.statSync` in `callback to files.map` 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:515— `zlib.gzipSync` in `callback to blobIds.forEach` 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:669— `zlib.gunzipSync` in `callback to blobs.forEach` 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:198— `existsSync` in `app.post("/v1/test-utils/git/setup")` 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:199— `rmSync` in `app.post("/v1/test-utils/git/setup")` 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:201— `mkdtempSync` in `app.post("/v1/test-utils/git/setup")` 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:202— `cpSync` in `app.post("/v1/test-utils/git/setup")` 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:208— `existsSync` in `app.delete("/v1/test-utils/git/setup")` 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:209— `rmSync` in `app.delete("/v1/test-utils/git/setup")` 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 packages/insomnia/scripts/sandbox-vendored-lib.ts:78— `fs.mkdirSync` in `generateVendoredFile` 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 packages/insomnia/scripts/sandbox-vendored-lib.ts:80— `fs.writeFileSync` in `generateVendoredFile` 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 packages/insomnia/src/main/ipc/electron.ts:477— `mkdirSync` in `ipcMainHandle("openPath")` 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 packages/insomnia/src/main/network/libcurl-promise.ts:162— `fs.statSync` 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 packages/insomnia/src/main/network/libcurl-promise.ts:168— `fs.openSync` 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 packages/insomnia/src/main/network/multipart.ts:28— `fs.statSync` 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 packages/insomnia/src/main/network/socket-io.ts:208— `fs.readFileSync` in `callback to filteredClientCertificates.forEach` 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 packages/insomnia/src/main/network/socket-io.ts:213— `fs.readFileSync` in `callback to filteredClientCertificates.forEach` 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 packages/insomnia/src/main/network/socket-io.ts:218— `fs.readFileSync` in `callback to filteredClientCertificates.forEach` 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 packages/insomnia/src/main/network/websocket.ts:292— `fs.readFileSync` in `callback to filteredClientCertificates.forEach` 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.
Fake-async — async method never awaits packages/insomnia-data/node-src/services/helpers/command-search.ts:321— `abortCommandSearch` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia-scripting-environment/src/objects/async-objects.ts:81— `resetAsyncTasks` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/entry.main.ts:66— `openDeepLinkUrl` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/ipc/secret-storage.ts:22— `setSecret` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/ipc/secret-storage.ts:44— `deleteSecret` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/mcp/common.ts:171— `clearConnectionContext` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/mcp/common.ts:450— `cancelRequest` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/network/curl.ts:401— `deleteRequestMaps` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/network/socket-io.ts:458— `deleteRequestMaps` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/network/socket-io.ts:479— `sendPayload` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/network/socket-io.ts:514— `sendWebSocketEvent` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/network/websocket.ts:563— `deleteRequestMaps` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/network/websocket.ts:580— `getWebSocketReadyState` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/main/network/websocket.ts:618— `sendWebSocketEvent` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/sync/git/mem-client.ts:173— `unlink` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/sync/git/mem-client.ts:189— `mkdir` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/sync/git/mem-client.ts:224— `rmdir` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/sync/git/mem-client.ts:263— `symlink` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/sync/git/ne-db-client.ts:285— `rmdir` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/insomnia/src/ui/hooks/use-insomnia-tab.ts:240— `getNavigationTabId` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
D30 · Dependency Vulnerabilities· Medium CVE · ×19
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
AC2 · Forms & labels· <TextField> field component without a label · ×18
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:121— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:173— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:198— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:223— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:300— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:332— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/gcp-credential-form.tsx:62— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:115— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:201— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:226— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:254— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:264— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:292— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:317— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:327— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:394— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/git-project-branches-modal.tsx:351— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:634— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
Change coupling: project-create-form.tsx ↔ project-settings-form.tsx packages/insomnia/src/ui/components/project/project-create-form.tsx:1— `packages/insomnia/src/ui/components/project/project-create-form.tsx` and `packages/insomnia/src/ui/components/project/project-settings-form.tsx` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `d693ea90` fix(git): fix folder naming, relocation, and resurrection bugs for gi…; `5acb5221` fix: pressing Enter within a modal triggers primary CTA properly (#10…; `7863ad71` feat: Adds dialog to confirm closing a modal with unsaved changes (p2… — run `git show` on any of them.
Change coupling: organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx ↔ workspace-environments-edit-modal.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:1— `packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx` and `packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx` change together 78% of the time (21 of the 27 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 21 shared commits counted here, the most recent 3 are `9a468f99` fix: keep variable source tooltip interactive in the environments mod…; `eca11ccb` feat: Implement UX for marking environments as confidential (#10480); `5cfe018d` feat: show variable source in live preview and hover tooltip (#10583) — run `git show` on any of them.
Change coupling: request-group-settings-modal.tsx ↔ request-settings-modal.tsx packages/insomnia/src/ui/components/modals/request-group-settings-modal.tsx:1— `packages/insomnia/src/ui/components/modals/request-group-settings-modal.tsx` and `packages/insomnia/src/ui/components/modals/request-settings-modal.tsx` 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 — 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 `99d9a3d7` feat: focus & keyboard navigation improvements [INS-2552] (#10049); `3082b102` fix: exclude environment workspaces from Move/Copy to Workspace dropd…; `3fec8698` Markdown-inlined (#7554) — run `git show` on any of them.
Change coupling: sync-history-modal.tsx ↔ sync-staging-modal.tsx packages/insomnia/src/ui/components/modals/sync-history-modal.tsx:1— `packages/insomnia/src/ui/components/modals/sync-history-modal.tsx` and `packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `64dab5af` upgrade react-aria-components to rc (#6906); `e1fa0cb4` handle overflows on sync modals (#6796); `a6dabb2e` Insomnia Sync improvements (#6738) — run `git show` on any of them.
Change coupling: entry.preload.ts ↔ main.ts packages/insomnia/src/entry.preload.ts:1— `packages/insomnia/src/entry.preload.ts` and `packages/insomnia/src/main/ipc/main.ts` change together 66% of the time (43 of the 65 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 43 shared commits counted here, the most recent 3 are `e1922712` feat: confidential value policy and render engine (#10509); `5a0b951f` feat: surface OAuth2 request logs in Console timeline (INS-1284) (#10…; `b4c36a39` feat(templating): (H1) route user-plugin request hooks through the sa… — run `git show` on any of them.
Change coupling: sync-branches-modal.tsx ↔ sync-history-modal.tsx packages/insomnia/src/ui/components/modals/sync-branches-modal.tsx:1— `packages/insomnia/src/ui/components/modals/sync-branches-modal.tsx` and `packages/insomnia/src/ui/components/modals/sync-history-modal.tsx` 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 — 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 6 shared commits counted here, the most recent 3 are `64dab5af` upgrade react-aria-components to rc (#6906); `e1fa0cb4` handle overflows on sync modals (#6796); `a6dabb2e` Insomnia Sync improvements (#6738) — run `git show` on any of them.
Change coupling: tag-editor.tsx ↔ variable-editor.tsx packages/insomnia/src/ui/components/templating/tag-editor.tsx:1— `packages/insomnia/src/ui/components/templating/tag-editor.tsx` and `packages/insomnia/src/ui/components/templating/variable-editor.tsx` change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `c9b20dd8` fix/confidential variable (#10629); `03076765` feat: apply confidential policy to preview surfaces (#10510); `4bd9b166` Change nunjucks preview box to <textarea> (Closes #904) (at that commit the files were still `packages/insomnia-app/app/ui/components/templating/tag-editor.js` and `packages/insomnia-app/app/ui/components/templating/variable-editor.js`) — run `git show` on any of them.
Change coupling: request-pane.tsx ↔ websocket-request-pane.tsx packages/insomnia/src/ui/components/panes/request-pane.tsx:1— `packages/insomnia/src/ui/components/panes/request-pane.tsx` and `packages/insomnia/src/ui/components/websockets/websocket-request-pane.tsx` change together 56% of the time (19 of the 34 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `791b9ac8` fix(ui): prevent button text truncation (#10100); `14a8797d` fix: wrong tailwind usage (#9336); `3324a7f9` chore: remove fromSync hack (#9016) — run `git show` on any of them.
Change coupling: organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx ↔ organization.$organizationId.project.$projectId.workspace.$workspaceId.test.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx:1— `packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx` and `packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.test.tsx` change together 55% of the time (34 of the 62 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 34 shared commits counted here, the most recent 3 are `095585f5` change show test behavior (#10504); `f0bf6c8b` fix: New Collection API issues and UI adjustment (#10503); `b29fef97` Fix tab width for document. (#10094) — run `git show` on any of them.
Change coupling: git-service.ts ↔ git-project-sync-dropdown.tsx packages/insomnia/src/main/git-service.ts:1— `packages/insomnia/src/main/git-service.ts` and `packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx` change together 55% of the time (12 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `e446fef6` fix(git): enable bidirectional sync for local projects without a remo…; `d693ea90` fix(git): fix folder naming, relocation, and resurrection bugs for gi…; `71dc5c93` feat(Git Sync): improve git migration onboarding UX and local file sy… — run `git show` on any of them.
Change coupling: raw-editor.tsx ↔ response-pane.tsx packages/insomnia/src/ui/components/editors/body/raw-editor.tsx:1— `packages/insomnia/src/ui/components/editors/body/raw-editor.tsx` and `packages/insomnia/src/ui/components/panes/response-pane.tsx` 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 — 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 `9122ca93` feat: common actions analytics [INS-2120] (#9664); `dce5f320` Refactor settings and store timeline separately (at that commit the files were still `packages/insomnia-app/app/ui/components/editors/body/raw-editor.js` and `packages/insomnia-app/app/ui/components/response-pane.js`); `c647c1e1` Persist editor scroll positions (#746) (at that commit the files were still `packages/insomnia-app/app/ui/components/editors/body/raw-editor.js` and `packages/insomnia-app/app/ui/components/response-pane.js`) — run `git show` on any of them.
Change coupling: git-branches-modal.tsx ↔ git-staging-modal.tsx packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:1— `packages/insomnia/src/ui/components/modals/git-branches-modal.tsx` and `packages/insomnia/src/ui/components/modals/git-staging-modal.tsx` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `bc8aa388` Support for resolving conflicts when using git-merge [INS-4638] (#8185); `c3859718` Support for resolving conflicts when pulling from remote git branch. …; `6463d709` Feat/git improvements (#5779) — run `git show` on any of them.
Change coupling: response-pane.tsx ↔ response-multipart-viewer.tsx packages/insomnia/src/ui/components/panes/response-pane.tsx:1— `packages/insomnia/src/ui/components/panes/response-pane.tsx` and `packages/insomnia/src/ui/components/viewers/response-multipart-viewer.tsx` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — 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 9 shared commits counted here, the most recent 3 are `d0116ebe` fix: large responses now download correctly [INS-2365] (#9807); `4bc34bba` fix: remove Buffer class usage in renderer code (#10031); `ae9bbbff` async getBodyBuffer (#8469) — run `git show` on any of them.
Change coupling: code-editor.tsx ↔ one-line-editor.tsx packages/insomnia/src/ui/components/.client/codemirror/code-editor.tsx:1— `packages/insomnia/src/ui/components/.client/codemirror/code-editor.tsx` and `packages/insomnia/src/ui/components/.client/codemirror/one-line-editor.tsx` change together 50% of the time (33 of the 66 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 33 shared commits counted here, the most recent 3 are `03076765` feat: apply confidential policy to preview surfaces (#10510); `5cfe018d` feat: show variable source in live preview and hover tooltip (#10583); `200fc47e` fix: Update the vault tag id when paste the vault tag (#10402) — run `git show` on any of them.
Change coupling: git-service.ts ↔ git-project-staging-modal.tsx packages/insomnia/src/main/git-service.ts:1— `packages/insomnia/src/main/git-service.ts` and `packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx` change together 50% of the time (15 of the 30 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `95fcf1b4` feat(Git Diff): Warn when a file isn't in the format Insomnia writes …; `db419cdb` feat: Debug Mode setting that enables the Git commit diagnostic panel…; `0b2b7f82` feat: Add incompatible fields check for git sync document (#10591) — run `git show` on any of them.
Change coupling: request-url-bar.tsx ↔ action-bar.tsx packages/insomnia/src/ui/components/request-url-bar.tsx:1— `packages/insomnia/src/ui/components/request-url-bar.tsx` and `packages/insomnia/src/ui/components/websockets/action-bar.tsx` change together 50% of the time (10 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `feb24e86` fix: support variables in websocket requests (#10067); `8dfadecd` Feat: Make people's first request easy (#9950); `3fe4e54c` fix: update action bar value after users click import from url (#8643) — run `git show` on any of them.
Change coupling: organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.tsx ↔ organization.$organizationId.project.$projectId.workspace.$workspaceId.test.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.tsx:1— `packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.tsx` and `packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.test.tsx` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `8ab1b383` feat: support for middle mouse button click to open new tab (#9696); `abe57bc9` Revert "feat: support for middle mouse button click to open new tab"; `9b1b2598` feat: support for middle mouse button click to open new tab — run `git show` on any of them.
Change coupling: mock-response-extractor.tsx ↔ mock-url-bar.tsx packages/insomnia/src/ui/components/editors/mock-response-extractor.tsx:1— `packages/insomnia/src/ui/components/editors/mock-response-extractor.tsx` and `packages/insomnia/src/ui/components/mocks/mock-url-bar.tsx` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `d99c753c` Reapply "feat: create collection from mock server routes (#9156)"; `a9d1a4b4` Revert "feat: create collection from mock server routes (#9156)"; `0b14918b` feat: create collection from mock server routes (#9156) — run `git show` on any of them.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/common/templating/types.ts:157— Project (context insomnia-data) is exposed in insomnia's public surface via RenderContextAncestor.RenderContextAncestor — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/common/project.ts:102— Project (context insomnia-data) is exposed in insomnia's public surface via project.regenerateProjectDocIds — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/common/project.ts:144— Project (context insomnia-data) is exposed in insomnia's public surface via project.checkAllProjectSyncStatus — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/common/project.ts:272— Project (context insomnia-data) is exposed in insomnia's public surface via project.getProjectsWithGitRepositories — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.tsx:48— Project (context insomnia-data) is exposed in insomnia's public surface via WorkspaceLoaderData.activeProject — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.tsx:60— Project (context insomnia-data) is exposed in insomnia's public surface via WorkspaceLoaderData.projects — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/routes/untracked-projects.tsx:10— Project (context insomnia-data) is exposed in insomnia's public surface via UntrackedProjectsLoaderData.untrackedProjects — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/sync/vcs/initialize-backend-project.ts:55— Project (context insomnia-data) is exposed in insomnia's public surface via initialize-backend-project.pushSnapshotOnInitialize — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/ui/components/modals/project-modal.tsx:15— Project (context insomnia-data) is exposed in insomnia's public surface via project-modal.ProjectModal — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx:52— Project (context insomnia-data) is exposed in insomnia's public surface via new-workspace-modal.NewWorkspaceModal — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/ui/hooks/use-insomnia-navigation.ts:19— Project (context insomnia-data) is exposed in insomnia's public surface via NavigationResource.NavigationResource — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/ui/hooks/use-insomnia-navigation.ts:136— Project (context insomnia-data) is exposed in insomnia's public surface via NavigationResources.project — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/ui/hooks/use-remote-files.ts:66— Project (context insomnia-data) is exposed in insomnia's public surface via use-remote-files.useRemoteFilesByProjectId — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/ui/organization-utils.ts:170— Project (context insomnia-data) is exposed in insomnia's public surface via organization-utils.updateLocalProjectToRemote — couples the contexts.
Cross-context type Project (insomnia-data → insomnia) packages/insomnia/src/ui/utils/remote-projects.ts:18— Project (context insomnia-data) is exposed in insomnia's public surface via remote-projects.groupRemoteFilesByProjectId — couples the contexts.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×12
Markup wires an event to an empty handler packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:591— `onAction` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:764— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:188— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:201— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:238— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:250— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:334— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:346— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:382— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:394— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:1059— `onPress` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler packages/insomnia/src/ui/components/socket-io/event-tab-pane.tsx:161— `onSelectionChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Weak hash algorithm packages/insomnia-data/node-src/services/cookie-jar.ts:24— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia-data/node-src/services/environment.ts:82— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia-vcs/src/util.ts:476— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia-vcs/src/vcs.ts:45— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia-vcs/src/vcs.ts:1472— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia/src/main/importers/importers/openapi-3.ts:149— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia/src/main/importers/importers/openapi-3.ts:237— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia/src/main/importers/importers/openapi-3.ts:665— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia/src/main/importers/importers/swagger-2.ts:27— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia/src/main/templating-worker-database.ts:673— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia/src/sync/delta/diff.ts:99— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/insomnia/src/templating/liquid-extension.ts:65— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
`async` Promise executor packages/insomnia-vcs/src/store/drivers/file-system-driver.ts:81— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia-scripting-environment/src/objects/send-request.ts:18— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/entry.preload.ts:363— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/ui/templating/worker.ts:44— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/templating/index.ts:47— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/main/api.protocol.ts:68— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/main/authorize-user-in-window.ts:30— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/main/network/libcurl-promise.ts:105— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/main/network/multipart.ts:17— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/main/ipc/main.ts:804— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/insomnia/src/main/ipc/main.ts:853— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/main/importers/entities.ts:53— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via ImportRequest.authentication — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/main/network/o-auth-1/get-token.ts:43— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via get-token.getToken — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/network/authentication.ts:17— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via authentication.isAuthEnabled — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/network/authentication.ts:19— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via authentication.getAuthObjectOrNull — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) REDACTED:52— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via network.getOrInheritAuthentication — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) REDACTED:1016— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via network.getAuthQueryParams — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) REDACTED:1031— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via network.transformUrl — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/main/mcp/types.ts:91— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via OpenMcpHTTPClientConnectionOptions.authentication — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.connect.tsx:26— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via ConnectActionParams.authentication — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia) packages/insomnia/src/ui/utils/render-realtime-connect.ts:15— RequestAuthentication (context insomnia-data) is exposed in insomnia's public surface via RenderedRealtimeConnectPayload.authentication — couples the contexts.
X2 · Cancellation propagation· Async function without AbortSignal · ×8
Async function without AbortSignal: readFileFromPathOrUrl REDACTED:197— `readFileFromPathOrUrl` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: updateGitProjectCount packages/insomnia-api/src/project.ts:74— `updateGitProjectCount` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: decodeBase64 packages/insomnia/src/ui/auth-session-provider.client.ts:31— `decodeBase64` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: onComplete packages/insomnia/src/ui/components/design-empty-state.tsx:80— `onComplete` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: sendRequestViaFetch packages/insomnia/src/scripting/quickjs-script-engine.ts:279— `sendRequestViaFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: validatePat packages/insomnia/src/konnect/api.ts:125— `validatePat` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchImportContentFromURI packages/insomnia/src/common/import.ts:82— `fetchImportContentFromURI` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchFromTemplateWorkerDatabase packages/insomnia/src/common/templating/liquid-extension-worker.ts:49— `fetchFromTemplateWorkerDatabase` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×7
Focus outline removed in CSS without a :focus replacement packages/insomnia/src/ui/css/main.css:166— `summary` 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 packages/insomnia/src/ui/css/main.css:776— `.form-control` 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 packages/insomnia/src/ui/css/main.css:1059— `textarea` 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 packages/insomnia/src/ui/css/main.css:2430— `.modal: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 packages/insomnia/src/ui/css/main.css:2951— `.sidebar: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 packages/insomnia/src/ui/css/lib/codemirror/codemirror.css:248— `.CodeMirror-scroll` 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 packages/insomnia/src/ui/css/lib/codemirror/codemirror.css:375— `.CodeMirror-code` 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.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×7
Recursive walk over a caller-supplied document has no depth cap packages/insomnia-data/common-src/deterministic-stringify.ts:8— `deterministicStringify` is exported and takes `value: any` from its caller, and it calls itself at line 8 (`deterministicStringify`) with a piece of `value` (and at line 9, line 21) — and nowhere in `deterministicStringify` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deterministicStringify` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/insomnia/src/ui/components/modals/visual-diff/diff-engine.ts:96— `valuesEqual` is exported, takes a document from its caller (line 119) and hands it to `sortDeep`, which calls itself at line 96 (`sortDeep`) with a piece of `value` (and at line 102) — and nowhere in `sortDeep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sortDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/insomnia/src/common/utils/environment-utils.ts:50— `checkNestedKeys` is exported and takes `obj: Record<string, any>` from its caller, and it calls itself at line 50 (`checkNestedKeys`) with a piece of `obj` — and nowhere in `checkNestedKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `checkNestedKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap REDACTED:24— `getKeys` is exported and takes `obj: any` from its caller, and it calls itself at line 24 (`getKeys`) with a piece of `obj` (and at line 30) — and nowhere in `getKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/insomnia/src/common/network/sensitive-value-collector.ts:136— `collectLeafValues` is exported and takes `value: any` from its caller, and it calls itself at line 136 (`collectLeafValues`) with a piece of `value` (and at line 140) — and nowhere in `collectLeafValues` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collectLeafValues` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/insomnia/src/common/insomnia-schema-migrations/index.ts:152— `normalizePropertyOrder` is exported and takes `obj: any` from its caller, and it calls itself at line 152 (`normalizePropertyOrder`) with a piece of `obj` (and at line 172) — and nowhere in `normalizePropertyOrder` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `normalizePropertyOrder` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/insomnia/src/common/insomnia-schema-migrations/v5.1.ts:69— `cleanHeadersAndParameters` is exported and takes `obj: any` from its caller, and it calls itself at line 69 (`cleanHeadersAndParameters`) with a piece of `obj` (and at line 127, line 140, line 158) — and nowhere in `cleanHeadersAndParameters` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `cleanHeadersAndParameters` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC4 · Keyboard semantics· Link used as a button (placeholder href) · ×6
Link used as a button (placeholder href) packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-field-link.tsx:23— 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.
Link used as a button (placeholder href) packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-search-results.tsx:110— 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.
Link used as a button (placeholder href) packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-search-results.tsx:143— 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.
Link used as a button (placeholder href) packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-type-link.tsx:35— 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.
Link used as a button (placeholder href) packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:229— 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.
Link used as a button (placeholder href) packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:240— 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×6
Animation without a prefers-reduced-motion guard packages/insomnia/src/ui/components/base/prompt-button.tsx:148— <i> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:875— <div> moves — its `animate-[sidebar-focus-in_200ms_ease-out]` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:1025— <div> moves — its `animate-[sidebar-focus-in_200ms_ease-out]` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard packages/insomnia/src/ui/css/main.css:767— `.ai-block` moves (`animation: AIBlockLoading 1s ease-in-out`) 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 packages/insomnia/src/ui/css/main.css:3361— `.toast` moves (`transition: opacity 200ms,
right 300ms,
bottom 300ms,
transform 200ms ease-out`) 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 packages/insomnia/src/ui/css/styles.css:251— `.bounce-in` moves (`animation: bounceIn 350ms ease-in`) 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.
HackComment packages/insomnia/src/ui/plugins/misc.ts:115— // HACK: Dialog styles for CodeMirror dialogs too — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:198— // hack to workaround gridlist not have access to workspace scope — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.connect.tsx:133— // HACK: even more elaborate hack to get the request to update — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/insomnia/src/main/network/get-auth-header.ts:79— // HACK: GraphQL requests use a child request to fetch the schema with an — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/insomnia/src/main/ipc/grpc.ts:513— // HACK BUT DO NOT REMOVE — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/insomnia/src/common/render.ts:870— // HACK: Switch '#}' to '# }' to prevent Nunjucks from barfing — 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.
AC3 · Page structure· Data table has no header cells · ×5
Data table has no header cells REDACTED:14— 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).
Data table has no header cells packages/insomnia/src/ui/components/panes/placeholder-request-pane.tsx:39— 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).
Data table has no header cells packages/insomnia/src/ui/components/settings/shortcuts.tsx:47— 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).
Data table has no header cells packages/insomnia/src/ui/components/tags/size-tag.tsx:20— 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).
Data table has no header cells packages/insomnia/src/ui/components/viewers/response-csv-viewer.tsx:49— 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).
`async` callback passed to `forEach` packages/insomnia-data/node-src/services/environment.ts:55— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` packages/insomnia/src/ui/hooks/use-close-connection.ts:40— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` packages/insomnia/src/ui/hooks/use-close-connection.ts:51— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` packages/insomnia/src/ui/components/modals/proto-files-modal.tsx:296— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` packages/insomnia/src/main/backup.ts:71— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
Skipped test: can make a mock route: WARNING: THIS TEST DEPENDS ON mock-stage.insomnia.run to be up packages/insomnia-smoke-test/tests/smoke/mock.test.ts:5— Skipped — switched off by test.skip
Skipped test: should lint specification with custom ruleset packages/insomnia-inso/src/commands/lint-specification.test.ts:45— Skipped — switched off by it.skip
Skipped test: returns decrypted string when toJsonWebKey is false packages/insomnia/src/common/utils/vault.test.ts:73— Skipped — switched off by it.skip
Skipped test: returns decrypted object when toJsonWebKey is true packages/insomnia/src/common/utils/vault.test.ts:83— Skipped — switched off by it.skip
No assertions: merges even if no common root packages/insomnia-vcs/src/__tests__/vcs.test.ts:717— 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: t2 packages/insomnia-scripting-environment/src/objects/__tests__/test.test.ts:27— 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: slow packages/insomnia-scripting-environment/src/objects/__tests__/test.test.ts: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: waitUntilDone() resolves immediately when queue is empty packages/insomnia/src/sync/git/sync-queue.test.ts:63— 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.
Deprecated: eslint REDACTED:63— eslint 9.39.4, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: crypto-js packages/insomnia-scripting-environment/package.json:33— crypto-js 4.2.0, declared in packages/insomnia-scripting-environment/package.json, is marked deprecated by its publisher: "Active development of CryptoJS has been discontinued. This library is no longer maintained.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: apiconnect-wsdl REDACTED:86— apiconnect-wsdl 2.0.36, declared in REDACTED, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: httplease-asap REDACTED:120— httplease-asap 0.6.0, declared in REDACTED, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Repeated repair: packages/insomnia/src/ui/components/templating/variable-editor.tsx packages/insomnia/src/ui/components/templating/variable-editor.tsx:32— packages/insomnia/src/ui/components/templating/variable-editor.tsx changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is variable-editor.VariableEditor at line 32), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix/confidential variable (#10629)”; “fix: ignore inherited keys when resolving variable source (#10640)”; “fix: sync variable source with live preview edits (#10639)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/components/templating/variable-editor.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/insomnia/src/ui/utils/render-realtime-connect.ts packages/insomnia/src/ui/utils/render-realtime-connect.ts:24— packages/insomnia/src/ui/utils/render-realtime-connect.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is render-realtime-connect.renderRealtimeConnectPayload at line 24), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(INS-3620): tag cookie assignment origin (#10475)”; “fix(network): send fully rendered request for SSE connections (#10445)”; “fix: consolidate user-agent disable logic (#10310)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/utils/render-realtime-connect.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/insomnia/src/ui/context/app/insomnia-app-data-context.tsx packages/insomnia/src/ui/context/app/insomnia-app-data-context.tsx:40— packages/insomnia/src/ui/context/app/insomnia-app-data-context.tsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is insomnia-app-data-context.useDBQueryClient at line 40), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: change tanstack query option (#10426)”; “fix: Create workspace below the focus item when created in sidebar (#10370)”; “fix sidebar data not updated when offline (#10369)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/ui/context/app/insomnia-app-data-context.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/insomnia/src/main/secure-read-file.ts packages/insomnia/src/main/secure-read-file.ts:61— packages/insomnia/src/main/secure-read-file.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is secure-read-file.isDatabaseFileAlias at line 61), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(scripting): allow form-data body updates via script (#10576)”; “fix: constrain file template tag (#10528)”; “fix(INS-3620): tag cookie assignment origin (#10475)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 10:42:49 +00:00' --until='2026-10-26 10:42:49 +00:00' --full-history --no-merges -- packages/insomnia/src/main/secure-read-file.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Cross-context type KeyboardShortcut (insomnia-data → insomnia) packages/insomnia/src/ui/components/modals/add-key-combination-modal.tsx:11— KeyboardShortcut (context insomnia-data) is exposed in insomnia's public surface via AddKeyCombinationModalOptions.keyboardShortcut — couples the contexts.
Cross-context type KeyboardShortcut (insomnia-data → insomnia) packages/insomnia/src/ui/components/modals/add-key-combination-modal.tsx:13— KeyboardShortcut (context insomnia-data) is exposed in insomnia's public surface via AddKeyCombinationModalOptions.addKeyCombination — couples the contexts.
Cross-context type KeyboardShortcut (insomnia-data → insomnia) packages/insomnia/src/ui/components/keydown-binder.ts:17— KeyboardShortcut (context insomnia-data) is exposed in insomnia's public surface via keydown-binder.useKeyboardShortcuts — couples the contexts.
Cross-context type KeyboardShortcut (insomnia-data → insomnia) packages/insomnia/src/ui/components/keydown-binder.ts:54— KeyboardShortcut (context insomnia-data) is exposed in insomnia's public surface via keydown-binder.useDocBodyKeyboardShortcuts — couples the contexts.
ClassTooLong: GitVCS packages/insomnia/src/sync/git/git-vcs.ts:150— ClassTooLong — 1244 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 844 over it, 3.11× 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: VCS packages/insomnia-vcs/src/vcs.ts:96— ClassTooLong — 840 significant lines (blank, comment-only and punctuation-only lines excluded), 71 methods. The bar is 400 significant lines; this is 440 over it, 2.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: RepoFileWatcher packages/insomnia/src/sync/git/repo-file-watcher.ts:103— ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 186 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ImportPostman packages/insomnia/src/main/importers/importers/postman.ts:141— ClassTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 138 over it, 1.35× 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.
Swallowed exception (caught, then discarded) packages/insomnia-data/common-src/ndjson.ts:22— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/insomnia/src/ui/plugins/misc.ts:32— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/insomnia/src/ui/components/editors/auth/o-auth-2-auth.tsx:474— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) packages/insomnia/src/sync/git/git-repo-migration.ts:86— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×3
Modal dialog does not manage focus packages/insomnia/src/ui/components/project/konnect-moved-onboarding.tsx:33— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/konnect-env-onboarding.tsx:33— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/sidebar-focus-onboarding.tsx:33— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Cross-context type AnalyticsEvent (insomnia-analytics → insomnia) packages/insomnia/src/ui/analytics.ts:18— AnalyticsEvent (context insomnia-analytics) is exposed in insomnia's public surface via analytics.trackOnceDaily — couples the contexts.
Cross-context type AnalyticsEvent (insomnia-analytics → insomnia) packages/insomnia/src/ui/analytics.ts:44— AnalyticsEvent (context insomnia-analytics) is exposed in insomnia's public surface via analytics.trackImportEvent — couples the contexts.
Cross-context type AnalyticsEvent (insomnia-analytics → insomnia) packages/insomnia/src/main/analytics.ts:60— AnalyticsEvent (context insomnia-analytics) is exposed in insomnia's public surface via analytics.trackAnalyticsEvent — couples the contexts.
Cross-context type StageEntry (insomnia-vcs → insomnia) packages/insomnia/src/main/cloud-sync/ipc.ts:57— StageEntry (context insomnia-vcs) is exposed in insomnia's public surface via SyncBridgeMethods.stage — couples the contexts.
Cross-context type StageEntry (insomnia-vcs → insomnia) packages/insomnia/src/main/cloud-sync/ipc.ts:61— StageEntry (context insomnia-vcs) is exposed in insomnia's public surface via SyncBridgeMethods.unstage — couples the contexts.
Cross-context type StageEntry (insomnia-vcs → insomnia) packages/insomnia/src/sync/vcs/initialize-backend-project.ts:10— StageEntry (context insomnia-vcs) is exposed in insomnia's public surface via SyncVCSLike.stage — couples the contexts.
TooManyMethods: VCS packages/insomnia-vcs/src/vcs.ts:96— TooManyMethods — 71 methods. The bar is 30 methods; this is 41 over it, 2.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: GitVCS packages/insomnia/src/sync/git/git-vcs.ts:150— 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: RepoFileWatcher packages/insomnia/src/sync/git/repo-file-watcher.ts:103— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
AC2 · Forms & labels· <RadioGroup> field component without a label · ×2
<RadioGroup> field component without a label packages/insomnia/src/ui/components/dropdowns/workspace-card-dropdown.tsx:316— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<RadioGroup> field component without a label packages/insomnia/src/ui/components/header-invite-button.tsx:131— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <PasswordInput> field component without a label · ×2
<PasswordInput> field component without a label packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx:393— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<PasswordInput> field component without a label packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx:447— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
key-value-editor.EnvironmentKVEditor::renderPairItem (cognitive 21) packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx:329— key-value-editor.EnvironmentKVEditor::renderPairItem has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 17, ternaries 4. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (key-value-editor.EnvironmentKVEditor::handleItemChange) 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.
key-value-editor.EnvironmentKVEditor::handleItemChange (cognitive 16) packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx:213— key-value-editor.EnvironmentKVEditor::handleItemChange has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6 (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: one other method here (key-value-editor.EnvironmentKVEditor::renderPairItem) 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.
Cross-context type RequestAuthentication (insomnia-data → insomnia-scripting-environment) packages/insomnia-scripting-environment/src/objects/auth.ts:353— RequestAuthentication (context insomnia-data) is exposed in insomnia-scripting-environment's public surface via auth.fromPreRequestAuth — couples the contexts.
Cross-context type RequestAuthentication (insomnia-data → insomnia-scripting-environment) packages/insomnia-scripting-environment/src/objects/auth.ts:597— RequestAuthentication (context insomnia-data) is exposed in insomnia-scripting-environment's public surface via auth.toPreRequestAuth — couples the contexts.
Cross-context type StrictNullSearchParamsValueType (insomnia-data → insomnia) REDACTED:57— StrictNullSearchParamsValueType (context insomnia-data) is exposed in insomnia's public surface via querystring.buildQueryParameter — couples the contexts.
Cross-context type StrictNullSearchParamsValueType (insomnia-data → insomnia) REDACTED:95— StrictNullSearchParamsValueType (context insomnia-data) is exposed in insomnia's public surface via querystring.buildQueryStringFromParams — couples the contexts.
Cross-context type KonnectDeploymentType (insomnia-data → insomnia) packages/insomnia/src/konnect/transform.ts:305— KonnectDeploymentType (context insomnia-data) is exposed in insomnia's public surface via transform.getKonnectDeploymentType — couples the contexts.
Cross-context type KonnectDeploymentType (insomnia-data → insomnia) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/konnect-project-icon/konnect-project-icon.tsx:18— KonnectDeploymentType (context insomnia-data) is exposed in insomnia's public surface via konnect-project-icon.KonnectProjectIcon — couples the contexts.
MethodTooLong: GitVCS.diff packages/insomnia/src/sync/git/git-vcs.ts:642— MethodTooLong — diff runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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: GitVCS.collectMergeConflicts packages/insomnia/src/sync/git/git-vcs.ts:1672— MethodTooLong — collectMergeConflicts runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
IC1 · Incompleteness & stubs· Both branches are identical · ×2
Both branches are identical — the condition decides nothing packages/insomnia/src/main/ipc/cookies.ts:23— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Both branches are identical — the condition decides nothing packages/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:267— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×2
Duplicated block with local edits (53 matched lines × 2 locations) packages/insomnia/src/common/templating/liquid-extension-worker.ts:65— packages/insomnia/src/common/templating/liquid-extension-worker.ts:65 · packages/insomnia/src/templating/liquid-extension.ts:23 — the two spans are one implementation copied and then locally edited — 462 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 (53 matched lines × 2 locations) packages/insomnia/src/ui/components/environment-picker.tsx:165— packages/insomnia/src/ui/components/environment-picker.tsx:165 · packages/insomnia/src/ui/components/environment-picker.tsx:264 — the two spans are one implementation copied and then locally edited — 235 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 (51 matched lines × 2 locations) · ×2
Duplicated block with local edits (51 matched lines × 2 locations) packages/insomnia/src/main/templating-worker-database.ts:821— packages/insomnia/src/main/templating-worker-database.ts:821 · packages/insomnia/src/plugins/context/network.ts:67 — 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 with local edits (51 matched lines × 2 locations) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.generate-request-collection.tsx:14— packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.generate-request-collection.tsx:14 · packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.spec.generate-request-collection.tsx:19 — the two spans are one implementation copied and then locally edited — 211 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/insomnia/src/ui/components/editors/mock-response-headers-editor.tsx:24— packages/insomnia/src/ui/components/editors/mock-response-headers-editor.tsx:24 · packages/insomnia/src/ui/components/editors/request-parameters-editor.tsx: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.
Duplicated block (43 lines × 2 locations) packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx:327— packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx:327 · packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx:399 — 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 (41 lines × 2 locations) packages/insomnia/src/main/templating-worker-database.ts:483— packages/insomnia/src/main/templating-worker-database.ts:483 · packages/insomnia/src/main/templating-worker-database.ts:554 — 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 (41 lines × 2 locations) packages/insomnia/src/ui/components/.client/codemirror/code-editor.tsx:753— packages/insomnia/src/ui/components/.client/codemirror/code-editor.tsx:753 · packages/insomnia/src/ui/components/.client/codemirror/one-line-editor.tsx:526 — 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.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark packages/insomnia/src/root.tsx:206— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Focus outline removed inline packages/insomnia/src/ui/components/first-request-creation.tsx:557— <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).
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 462 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.
project-navigation-sidebar.ProjectNavigationSidebarInner (cyclomatic 203) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:82— project-navigation-sidebar.ProjectNavigationSidebarInner has cyclomatic complexity 203 (threshold 15). Of this number, 26 points are the body's own statements and 177 belong to 41 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.
project-settings-form.ProjectSettingsForm (cyclomatic 136) packages/insomnia/src/ui/components/project/project-settings-form.tsx:78— project-settings-form.ProjectSettingsForm has cyclomatic complexity 136 (threshold 15). Of this number, 86 points are the body's own statements and 50 belong to 16 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.
tag-editor.TagEditor (cyclomatic 131) packages/insomnia/src/ui/components/templating/tag-editor.tsx:78— tag-editor.TagEditor has cyclomatic complexity 131 (threshold 15). Of this number, 17 points are the body's own statements and 114 belong to 18 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.
git-project-sync-dropdown.GitProjectSyncDropdown (cyclomatic 103) packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:52— git-project-sync-dropdown.GitProjectSyncDropdown has cyclomatic complexity 103 (threshold 15). Of this number, 49 points are the body's own statements and 54 belong to 16 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.
cli.go (cyclomatic 95) REDACTED:265— cli.go has cyclomatic complexity 95 (threshold 15). Most of this is not in the body itself: 13 of the 95 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 533, a function literal at line 902, a function literal at line 376, …). 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.
key-value-editor.KeyValueEditor (cyclomatic 95) packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:81— key-value-editor.KeyValueEditor has cyclomatic complexity 95 (threshold 15). Of this number, 31 points are the body's own statements and 64 belong to 18 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.
auth.toPreRequestAuth (cyclomatic 93) packages/insomnia-scripting-environment/src/objects/auth.ts:597— auth.toPreRequestAuth has cyclomatic complexity 93 (threshold 15). Of this number, 87 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.
insomnia-tab-context.InsomniaTabProvider (cyclomatic 85) packages/insomnia/src/ui/context/app/insomnia-tab-context.tsx:60— insomnia-tab-context.InsomniaTabProvider has cyclomatic complexity 85 (threshold 15). Most of this is not in the body itself: 2 of the 85 points are its own statements and the rest belongs to 27 function literals inside it that branch (lines 190, 258, 568, …). 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.
new-workspace-modal.NewWorkspaceModal (cyclomatic 83) packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx:52— new-workspace-modal.NewWorkspaceModal has cyclomatic complexity 83 (threshold 15). Most of this is not in the body itself: 11 of the 83 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 211, a function literal at line 132, a function literal at line 154, …). 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.Runner (cyclomatic 82) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:155— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.Runner has cyclomatic complexity 82 (threshold 15). Of this number, 26 points are the body's own statements and 56 belong to 27 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.
organization.$organizationId.project.$projectId._index.Component (cyclomatic 81) packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:79— organization.$organizationId.project.$projectId._index.Component has cyclomatic complexity 81 (threshold 15). Of this number, 34 points are the body's own statements and 47 belong to 16 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.
graph-ql-editor.GraphQLEditor (cyclomatic 81) packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx:232— graph-ql-editor.GraphQLEditor has cyclomatic complexity 81 (threshold 15). Of this number, 27 points are the body's own statements and 54 belong to 15 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.
sync-dropdown.SyncDropdown (cyclomatic 79) packages/insomnia/src/ui/components/dropdowns/sync-dropdown.tsx:42— sync-dropdown.SyncDropdown has cyclomatic complexity 79 (threshold 15). Of this number, 50 points are the body's own statements and 29 belong to 7 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.
git-project-staging-modal.GeneratedCommitsForm (cyclomatic 76) packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:430— git-project-staging-modal.GeneratedCommitsForm has cyclomatic complexity 76 (threshold 15). Of this number, 28 points are the body's own statements and 48 belong to 12 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.
git-project-staging-modal.ManualCommitForm (cyclomatic 72) packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:819— git-project-staging-modal.ManualCommitForm has cyclomatic complexity 72 (threshold 15). Of this number, 34 points are the body's own statements and 38 belong to 11 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.
GitVCS.diff (cyclomatic 71) packages/insomnia/src/sync/git/git-vcs.ts:642— GitVCS.diff has cyclomatic complexity 71 (threshold 15). Most of this is not in the body itself: 1 of the 71 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 665, a function literal at line 850, a function literal at line 840, …). 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.
git-project-staging-modal.OriginalGitProjectStagingModal (cyclomatic 71) packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:1550— git-project-staging-modal.OriginalGitProjectStagingModal has cyclomatic complexity 71 (threshold 15). Of this number, 20 points are the body's own statements and 51 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.
project-create-form.ProjectCreateForm (cyclomatic 71) packages/insomnia/src/ui/components/project/project-create-form.tsx:40— project-create-form.ProjectCreateForm has cyclomatic complexity 71 (threshold 15). Of this number, 38 points are the body's own statements and 33 belong to 10 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.
root.Root (cyclomatic 69) packages/insomnia/src/root.tsx:345— root.Root has cyclomatic complexity 69 (threshold 15). Most of this is not in the body itself: 2 of the 69 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 458, handleCurlPaste, a function literal at line 770, …). 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.Debug (cyclomatic 68) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx:164— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.Debug has cyclomatic complexity 68 (threshold 15). Of this number, 36 points are the body's own statements and 32 belong to 21 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.
url.Url (cyclomatic 65) packages/insomnia/src/ui/components/settings/llms/url.tsx:40— url.Url has cyclomatic complexity 65 (threshold 15). Of this number, 23 points are the body's own statements and 42 belong to 8 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.
use-sidebar-drag-and-drop.useSidebarDragAndDrop (cyclomatic 65) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:595— use-sidebar-drag-and-drop.useSidebarDragAndDrop has cyclomatic complexity 65 (threshold 15). Of this number, 54 points are the body's own statements and 11 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.
import-modal.ImportModal (cyclomatic 63) packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:205— import-modal.ImportModal has cyclomatic complexity 63 (threshold 15). Of this number, 20 points are the body's own statements and 43 belong to 10 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.
mcp-pane.McpPane (cyclomatic 63) packages/insomnia/src/ui/components/mcp/mcp-pane.tsx:89— mcp-pane.McpPane has cyclomatic complexity 63 (threshold 15). Most of this is not in the body itself: 7 of the 63 points are its own statements and the rest belongs to 21 function items inside it that branch (a function literal at line 119, a function literal at line 347, getServerCapabilities, …). 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.
command-palette.CommandPaletteCombobox (cyclomatic 62) packages/insomnia/src/ui/components/command-palette.tsx:102— command-palette.CommandPaletteCombobox has cyclomatic complexity 62 (threshold 15). Of this number, 25 points are the body's own statements and 37 belong to 19 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.
organization.$organizationId.project.$projectId.update.clientAction (cyclomatic 60) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.update.tsx:48— organization.$organizationId.project.$projectId.update.clientAction has cyclomatic complexity 60 (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.
git-sync-dropdown.GitSyncDropdown (cyclomatic 58) packages/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:43— git-sync-dropdown.GitSyncDropdown has cyclomatic complexity 58 (threshold 15). Of this number, 39 points are the body's own statements and 19 belong to 8 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.
tab-list.OrganizationTabList (cyclomatic 58) packages/insomnia/src/ui/components/tabs/tab-list.tsx:45— tab-list.OrganizationTabList has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 11 of the 58 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 160, a function literal at line 136, a function literal at line 250, …). 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.
use-sidebar-drag-and-drop.canDrop (cyclomatic 57) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:252— use-sidebar-drag-and-drop.canDrop has cyclomatic complexity 57 (threshold 15). Of this number, 53 points are the body's own statements and 4 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.
util.threeWayMerge (cyclomatic 56) packages/insomnia-vcs/src/util.ts:67— util.threeWayMerge has cyclomatic complexity 56 (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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.Component (cyclomatic 55) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:62— organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.Component has cyclomatic complexity 55 (threshold 15). Of this number, 36 points are the body's own statements and 19 belong to 11 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.
response-viewer.ResponseViewer (cyclomatic 55) packages/insomnia/src/ui/components/viewers/response-viewer.tsx:72— response-viewer.ResponseViewer has cyclomatic complexity 55 (threshold 15). Of this number, 30 points are the body's own statements and 25 belong to 8 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.
workspace-environments-edit-modal.WorkspaceEnvironmentsEditModal (cyclomatic 55) packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx:44— workspace-environments-edit-modal.WorkspaceEnvironmentsEditModal has cyclomatic complexity 55 (threshold 15). Of this number, 18 points are the body's own statements and 37 belong to 13 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.
websocket.openWebSocketConnection (cyclomatic 51) packages/insomnia/src/main/network/websocket.ts:174— websocket.openWebSocketConnection has cyclomatic complexity 51 (threshold 15). Of this number, 38 points are the body's own statements and 13 belong to 7 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.
mcp-request-pane.McpRequestPane (cyclomatic 50) packages/insomnia/src/ui/components/mcp/mcp-request-pane.tsx:94— mcp-request-pane.McpRequestPane has cyclomatic complexity 50 (threshold 15). Of this number, 23 points are the body's own statements and 27 belong to 8 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.
realtime-response-pane.RealtimeActiveResponsePane (cyclomatic 49) packages/insomnia/src/ui/components/websockets/realtime-response-pane.tsx:215— realtime-response-pane.RealtimeActiveResponsePane has cyclomatic complexity 49 (threshold 15). Of this number, 28 points are the body's own statements and 21 belong to 6 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.
invite-modal.MemberListItem (cyclomatic 48) packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx:291— invite-modal.MemberListItem has cyclomatic complexity 48 (threshold 15). Of this number, 30 points are the body's own statements and 18 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.
insomnia-v5.getCollection (cyclomatic 47) packages/insomnia/src/common/insomnia-v5.ts:665— insomnia-v5.getCollection has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 4 of the 47 points are its own statements and the rest belongs to one function literal inside it that branches (line 675). 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.
plugins.Plugins (cyclomatic 47) packages/insomnia/src/ui/components/settings/plugins.tsx:71— plugins.Plugins has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 15 of the 47 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 497, 203, 288, …). 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.
header-plan-indicator.HeaderPlanIndicator (cyclomatic 47) packages/insomnia/src/ui/components/header-plan-indicator.tsx:23— header-plan-indicator.HeaderPlanIndicator has cyclomatic complexity 47 (threshold 15). Of this number, 40 points are the body's own statements and 7 belong to 5 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.
libcurl-promise.createConfiguredCurlInstance (cyclomatic 46) packages/insomnia/src/main/network/libcurl-promise.ts:344— libcurl-promise.createConfiguredCurlInstance has cyclomatic complexity 46 (threshold 15). Of this number, 42 points are the body's own statements and 4 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.
index.traversePluginPath (cyclomatic 46) packages/insomnia/src/plugins/index.ts:189— index.traversePluginPath has cyclomatic complexity 46 (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.
insomnia-event-stream-context.InsomniaEventStreamProvider (cyclomatic 45) packages/insomnia/src/ui/context/app/insomnia-event-stream-context.tsx:88— insomnia-event-stream-context.InsomniaEventStreamProvider has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 2 of the 45 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 149, 113, 142, …). 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.
git-repo-form.GitRepoForm (cyclomatic 45) packages/insomnia/src/ui/components/project/git-repo-form.tsx:75— git-repo-form.GitRepoForm has cyclomatic complexity 45 (threshold 15). Of this number, 40 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.
window-utils.createWindow (cyclomatic 44) REDACTED:204— window-utils.createWindow has cyclomatic complexity 44 (threshold 15). Of this number, 19 points are the body's own statements and 25 belong to 15 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.
main.registerMainHandlers (cyclomatic 44) packages/insomnia/src/main/ipc/main.ts:384— main.registerMainHandlers has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 19 function literals inside it that branch (lines 614, 757, 811, …). 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.
import-export.ImportExport (cyclomatic 43) packages/insomnia/src/ui/components/settings/import-export.tsx:706— import-export.ImportExport has cyclomatic complexity 43 (threshold 15). Of this number, 28 points are the body's own statements and 15 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.
sync-staging-modal.SyncStagingModal (cyclomatic 43) packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx:113— sync-staging-modal.SyncStagingModal has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 2 of the 43 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 218, 329, 401, …). 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.
grpc-request-pane.GrpcRequestPane (cyclomatic 43) packages/insomnia/src/ui/components/panes/grpc-request-pane.tsx:62— grpc-request-pane.GrpcRequestPane has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 7 of the 43 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 84, handleRequestSend, a function literal at line 301, …). 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.
organization.$organizationId.project.$projectId.workspace.new.clientAction (cyclomatic 42) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.new.tsx:41— organization.$organizationId.project.$projectId.workspace.new.clientAction has cyclomatic complexity 42 (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.
event-view.MessageEventView (cyclomatic 42) packages/insomnia/src/ui/components/mcp/event-view.tsx:35— event-view.MessageEventView has cyclomatic complexity 42 (threshold 15). Of this number, 23 points are the body's own statements and 19 belong to 9 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.
v5.1.cleanHeadersAndParameters (cyclomatic 41) packages/insomnia/src/common/insomnia-schema-migrations/v5.1.ts:67— v5.1.cleanHeadersAndParameters has cyclomatic complexity 41 (threshold 15). Of this number, 21 points are the body's own statements and 20 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.
insomnia-v5.getInsomniaV5DataExport (cyclomatic 40) packages/insomnia/src/common/insomnia-v5.ts:1043— insomnia-v5.getInsomniaV5DataExport has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 11 of the 40 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 1114, getScriptFromResources, a function literal at line 1441, …). 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.
workspace-settings-modal.WorkspaceSettingsModal (cyclomatic 40) packages/insomnia/src/ui/components/modals/workspace-settings-modal.tsx:37— workspace-settings-modal.WorkspaceSettingsModal has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 10 of the 40 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 128, 49, 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.
network.tryToExecuteScript (cyclomatic 39) REDACTED:489— network.tryToExecuteScript has cyclomatic complexity 39 (threshold 15). Of this number, 32 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.
sandbox.checkSandboxViolations (cyclomatic 39) packages/insomnia/src/scripting/sandbox.ts:74— sandbox.checkSandboxViolations has cyclomatic complexity 39 (threshold 15). Of this number, 37 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
entity-diff-list.EntityDiffList (cyclomatic 39) packages/insomnia/src/ui/components/modals/visual-diff/entity-diff-list.tsx:64— entity-diff-list.EntityDiffList has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 13 of the 39 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 235, 145, 107, …). 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.
request-url-bar.RequestUrlBar (cyclomatic 39) packages/insomnia/src/ui/components/request-url-bar.tsx:59— request-url-bar.RequestUrlBar has cyclomatic complexity 39 (threshold 15). Of this number, 19 points are the body's own statements and 20 belong to 9 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.
sync-merge-modal.SyncMergeModal (cyclomatic 38) packages/insomnia/src/ui/components/modals/sync-merge-modal.tsx:62— sync-merge-modal.SyncMergeModal has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 187, 118, 223, …). 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.
auth.fromPreRequestAuth (cyclomatic 37) packages/insomnia-scripting-environment/src/objects/auth.ts:353— auth.fromPreRequestAuth has cyclomatic complexity 37 (threshold 15). Of this number, 16 points are the body's own statements and 21 belong to 5 function items inside it that branch. 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.
get-token.getOAuth2Token (cyclomatic 37) packages/insomnia/src/main/network/o-auth-2/get-token.ts:167— get-token.getOAuth2Token has cyclomatic complexity 37 (threshold 15). Of this number, 35 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.
curl.openCurlConnection (cyclomatic 37) packages/insomnia/src/main/network/curl.ts:137— curl.openCurlConnection has cyclomatic complexity 37 (threshold 15). Of this number, 17 points are the body's own statements and 20 belong to 3 function literals inside it that branch. 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.
first-request-creation.FirstRequestCreation (cyclomatic 37) packages/insomnia/src/ui/components/first-request-creation.tsx:128— first-request-creation.FirstRequestCreation has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 4 of the 37 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 373, handleCreateRequest, ensureWorkspaceId, …). 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.
invoke-method.invokePluginMethod (cyclomatic 36) packages/insomnia/src/plugins/invoke-method.ts:70— invoke-method.invokePluginMethod has cyclomatic complexity 36 (threshold 15). Of this number, 34 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
transport-streamable-http.wrappedFetch (cyclomatic 36) packages/insomnia/src/main/mcp/transport-streamable-http.ts:82— transport-streamable-http.wrappedFetch has cyclomatic complexity 36 (threshold 15). Of this number, 28 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.
diff-engine.collectEntities (cyclomatic 36) packages/insomnia/src/ui/components/modals/visual-diff/diff-engine.ts:353— diff-engine.collectEntities has cyclomatic complexity 36 (threshold 15). Of this number, 22 points are the body's own statements and 14 belong to 4 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.
invite-form.InviteForm (cyclomatic 36) packages/insomnia/src/ui/components/modals/invite-modal/invite-form.tsx:115— invite-form.InviteForm has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 15 of the 36 points are its own statements and the rest belongs to 11 function items inside it that branch (addEmail, handleInputKeyPress, a function literal at line 416, …). 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.
database-nedb.createNedbDatabase (cyclomatic 35) packages/insomnia-data/node-src/database/database-nedb.ts:47— database-nedb.createNedbDatabase has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 2 of the 35 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 565, flushChangesImpl, a function literal at line 242, …). 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.
command-search.commandSearch (cyclomatic 35) packages/insomnia-data/node-src/services/helpers/command-search.ts:19— command-search.commandSearch has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 11 of the 35 points are its own statements and the rest belongs to 8 function items inside it that branch (getRequestGroups, mapRequest, mapFile, …). 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.
app-data.updateAppDataOnDbChanges (cyclomatic 35) packages/insomnia/src/common/app-data.ts:239— app-data.updateAppDataOnDbChanges has cyclomatic complexity 35 (threshold 15). Of this number, 33 points are the body's own statements and 2 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.new.clientAction (cyclomatic 35) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.new.tsx:27— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.new.clientAction has cyclomatic complexity 35 (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.
konnect-sync-bar.KonnectSyncResultPanel (cyclomatic 35) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/konnect-sync-bar.tsx:289— konnect-sync-bar.KonnectSyncResultPanel has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs 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.
GitVCS.filesStatus (cyclomatic 34) packages/insomnia/src/sync/git/git-vcs.ts:482— GitVCS.filesStatus has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to one function literal inside it that branches (line 501). 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.
git-service.cloneGitRepoAction (cyclomatic 34) packages/insomnia/src/main/git-service.ts:1417— git-service.cloneGitRepoAction has cyclomatic complexity 34 (threshold 15). Of this number, 30 points are the body's own statements and 4 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.
environment-picker.EnvironmentPicker (cyclomatic 34) packages/insomnia/src/ui/components/environment-picker.tsx:41— environment-picker.EnvironmentPicker has cyclomatic complexity 34 (threshold 15). Of this number, 23 points are the body's own statements and 11 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.
request-group-pane.RequestGroupPane (cyclomatic 34) packages/insomnia/src/ui/components/panes/request-group-pane.tsx:25— request-group-pane.RequestGroupPane has cyclomatic complexity 34 (threshold 15). Of this number, 23 points are the body's own statements and 11 belong to 6 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.
use-insomnia-navigation.buildResourceUrl (cyclomatic 34) packages/insomnia/src/ui/hooks/use-insomnia-navigation.ts:198— use-insomnia-navigation.buildResourceUrl has cyclomatic complexity 34 (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.
GitVCS.fileStatus (cyclomatic 33) packages/insomnia/src/sync/git/git-vcs.ts:346— GitVCS.fileStatus has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 355, 442). 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.
ai-settings.AISettings (cyclomatic 33) packages/insomnia/src/ui/components/settings/ai-settings.tsx:13— ai-settings.AISettings has cyclomatic complexity 33 (threshold 15). Of this number, 26 points are the body's own statements and 7 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.
render.render::next (cyclomatic 32) packages/insomnia/src/common/render.ts:613— render.render::next has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
credentials.GitEditProviderOAuthForm (cyclomatic 32) packages/insomnia/src/ui/components/settings/credentials.tsx:57— credentials.GitEditProviderOAuthForm has cyclomatic complexity 32 (threshold 15). Of this number, 16 points are the body's own statements and 16 belong to 4 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.
libcurl-promise.curlRequest (cyclomatic 31) packages/insomnia/src/main/network/libcurl-promise.ts:104— libcurl-promise.curlRequest has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 105, 202, 250, …). 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.
git-branches-modal.LocalBranchItem (cyclomatic 31) packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:29— git-branches-modal.LocalBranchItem has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 9 of the 31 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 151, 45, 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.
sidebar-workspace-dropdown.SidebarWorkspaceDropdown (cyclomatic 31) packages/insomnia/src/ui/components/dropdowns/sidebar-workspace-dropdown.tsx:77— sidebar-workspace-dropdown.SidebarWorkspaceDropdown has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 15 of the 31 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 403, a function literal at line 276, a function literal at line 332, …). 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.
graph-ql-explorer.GraphQLExplorer (cyclomatic 31) packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:74— graph-ql-explorer.GraphQLExplorer has cyclomatic complexity 31 (threshold 15). Of this number, 22 points are the body's own statements and 9 belong to 6 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.
aws-credential-form.AWSCredentialForm (cyclomatic 31) packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:34— aws-credential-form.AWSCredentialForm has cyclomatic complexity 31 (threshold 15). Of this number, 22 points are the body's own statements and 9 belong to 2 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.
credentials.GitCredentialsList (cyclomatic 31) packages/insomnia/src/ui/components/settings/credentials.tsx:481— credentials.GitCredentialsList has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 625, 504, 522, …). 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.
openai.OpenAI (cyclomatic 31) packages/insomnia/src/ui/components/settings/llms/openai.tsx:14— openai.OpenAI has cyclomatic complexity 31 (threshold 15). Of this number, 17 points are the body's own statements and 14 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.
render.buildRenderContext (cyclomatic 30) packages/insomnia/src/common/render.ts:355— render.buildRenderContext has cyclomatic complexity 30 (threshold 15). Of this number, 23 points are the body's own statements and 7 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.
get-token.getExistingAccessTokenAndRefreshIfExpired (cyclomatic 30) packages/insomnia/src/main/network/o-auth-2/get-token.ts:406— get-token.getExistingAccessTokenAndRefreshIfExpired has cyclomatic complexity 30 (threshold 15). 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: 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.
plugin-name.validatePluginName (cyclomatic 30) packages/insomnia/src/common/utils/plugin-name.ts:12— plugin-name.validatePluginName has cyclomatic complexity 30 (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.
export-requests-modal.ExportRequestsModal (cyclomatic 30) packages/insomnia/src/ui/components/modals/export-requests-modal.tsx:192— export-requests-modal.ExportRequestsModal has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 11 function items inside it that branch (getSelectedRequestIds, setItemSelected, a function literal at line 218, …). 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.
import-modal.ImportResourcesForm (cyclomatic 30) packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:638— import-modal.ImportResourcesForm has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 670, a function literal at line 678, a function literal at line 695, …). 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.
mock-response-extractor.MockResponseExtractor (cyclomatic 30) packages/insomnia/src/ui/components/editors/mock-response-extractor.tsx:19— mock-response-extractor.MockResponseExtractor has cyclomatic complexity 30 (threshold 15). Of this number, 21 points are the body's own statements and 9 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.
response-pane.ResponsePane (cyclomatic 30) packages/insomnia/src/ui/components/panes/response-pane.tsx:43— response-pane.ResponsePane has cyclomatic complexity 30 (threshold 15). Of this number, 17 points are the body's own statements and 13 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.
gemini.Gemini (cyclomatic 30) packages/insomnia/src/ui/components/settings/llms/gemini.tsx:14— gemini.Gemini has cyclomatic complexity 30 (threshold 15). Of this number, 17 points are the body's own statements and 13 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.
gguf.GGUF (cyclomatic 30) packages/insomnia/src/ui/components/settings/llms/gguf.tsx:26— gguf.GGUF has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 80, 166, 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.
request-node.RequestNode (cyclomatic 30) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/request-node.tsx:134— request-node.RequestNode has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.clientAction (cyclomatic 29) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:960— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.clientAction has cyclomatic complexity 29 (threshold 15). Of this number, 25 points are the body's own statements and 4 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.
organization.Component (cyclomatic 29) packages/insomnia/src/routes/organization.tsx:173— organization.Component has cyclomatic complexity 29 (threshold 15). Of this number, 22 points are the body's own statements and 7 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.
konnect-settings-modal.KonnectSettingsModal (cyclomatic 29) packages/insomnia/src/ui/components/modals/konnect-settings-modal.tsx:14— konnect-settings-modal.KonnectSettingsModal has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 127, validateAndSetStatus, handleConnect, …). 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.
request-pane.RequestPane (cyclomatic 29) packages/insomnia/src/ui/components/panes/request-pane.tsx:44— request-pane.RequestPane has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 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.
claude.Claude (cyclomatic 29) packages/insomnia/src/ui/components/settings/llms/claude.tsx:13— claude.Claude has cyclomatic complexity 29 (threshold 15). Of this number, 17 points are the body's own statements and 12 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.
get-auth-header.getAuthHeader (cyclomatic 28) packages/insomnia/src/main/network/get-auth-header.ts:28— get-auth-header.getAuthHeader 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.
socket-io.openSocketIOConnection (cyclomatic 28) packages/insomnia/src/main/network/socket-io.ts:260— socket-io.openSocketIOConnection has cyclomatic complexity 28 (threshold 15). Of this number, 22 points are the body's own statements and 6 belong to 5 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.sendActionImplementation (cyclomatic 28) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.tsx:116— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.sendActionImplementation has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
sidebar-shortcut-actions-dropdown.SidebarShortcutActionsDropdown (cyclomatic 28) packages/insomnia/src/ui/components/dropdowns/sidebar-shortcut-actions-dropdown.tsx:33— sidebar-shortcut-actions-dropdown.SidebarShortcutActionsDropdown has cyclomatic complexity 28 (threshold 15). Of this number, 17 points are the body's own statements and 11 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.
key-value-editor.EnvironmentKVEditor::renderPairItem (cyclomatic 28) packages/insomnia/src/ui/components/editors/environment-key-value-editor/key-value-editor.tsx:329— key-value-editor.EnvironmentKVEditor::renderPairItem has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
request-result-card.RequestResultCard (cyclomatic 28) packages/insomnia/src/ui/components/panes/request-result-card.tsx:25— request-result-card.RequestResultCard has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
websocket-request-pane.WebSocketRequestPane (cyclomatic 28) packages/insomnia/src/ui/components/websockets/websocket-request-pane.tsx:187— websocket-request-pane.WebSocketRequestPane has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 belong to 5 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.
json.jsonPrettify (cyclomatic 28) packages/insomnia/src/ui/utils/prettify/json.ts:53— json.jsonPrettify 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.
organization.$organizationId.project.$projectId.workspace.new.createMockServer (cyclomatic 27) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.new.tsx:302— organization.$organizationId.project.$projectId.workspace.new.createMockServer has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
git-staging-modal.GitStagingModal (cyclomatic 27) packages/insomnia/src/ui/components/modals/git-staging-modal.tsx:30— git-staging-modal.GitStagingModal has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 138, a function literal at line 84, a function literal at line 113, …). 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.
mcp-pane.CollectionGridListItem (cyclomatic 27) packages/insomnia/src/ui/components/mcp/mcp-pane.tsx:551— mcp-pane.CollectionGridListItem has cyclomatic complexity 27 (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.
import-projects-modal.ImportProjectsModal (cyclomatic 27) packages/insomnia/src/ui/components/modals/import-modal/import-projects-modal.tsx:494— import-projects-modal.ImportProjectsModal 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 5 function items inside it that branch (processBulkProjectImport::startImportForProject, processBulkProjectImport, handleComplete, …). 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.
upload-runner-data-modal.UploadDataModal (cyclomatic 27) packages/insomnia/src/ui/components/modals/upload-runner-data-modal.tsx:65— upload-runner-data-modal.UploadDataModal has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 9 function items inside it that branch (parseFileContent, a function literal at line 184, handleFileSelect, …). 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.
workspace-pane-header.WorkspacePaneHeader (cyclomatic 27) packages/insomnia/src/ui/components/workspace/workspace-pane-header.tsx:21— workspace-pane-header.WorkspacePaneHeader has cyclomatic complexity 27 (threshold 15). Of this number, 22 points are the body's own statements and 5 belong to 4 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.
send-request.requestToCurlOptions (cyclomatic 26) packages/insomnia-scripting-environment/src/objects/send-request.ts:43— send-request.requestToCurlOptions has cyclomatic complexity 26 (threshold 15). Of this number, 24 points are the body's own statements and 2 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.
insomnia.initInsomniaObject (cyclomatic 26) packages/insomnia-scripting-environment/src/objects/insomnia.ts:144— insomnia.initInsomniaObject 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.
import.importResourcesToWorkspace (cyclomatic 26) packages/insomnia/src/common/import.ts:455— import.importResourcesToWorkspace has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 4 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.
insomnia-fetch.insomniaFetch (cyclomatic 26) packages/insomnia/src/common/insomnia-fetch.ts:22— insomnia-fetch.insomniaFetch 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.
auth-dropdown.castOneAuthTypeToAnother (cyclomatic 26) packages/insomnia/src/ui/components/dropdowns/auth-dropdown.tsx:27— auth-dropdown.castOneAuthTypeToAnother 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.
git-project-branches-modal.LocalBranchItem (cyclomatic 26) packages/insomnia/src/ui/components/modals/git-project-branches-modal.tsx:29— git-project-branches-modal.LocalBranchItem has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 131, 45, 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.
invite-modal.InviteModal (cyclomatic 26) packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx:78— invite-modal.InviteModal has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 161, 113, 119, …). 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.
row.Row (cyclomatic 26) packages/insomnia/src/ui/components/key-value-editor/row.tsx:49— row.Row has cyclomatic complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 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.
cloud-credential-modal.CloudCredentialModal (cyclomatic 26) packages/insomnia/src/ui/components/modals/cloud-credential-modal/cloud-credential-modal.tsx:27— cloud-credential-modal.CloudCredentialModal 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 6 function items inside it that branch (a function literal at line 122, exchangeAzureCode, a function literal at line 97, …). 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.
insomnia-v5-change-report.buildInsomniaChangeReport (cyclomatic 25) packages/insomnia/src/common/insomnia-v5-change-report.ts:267— insomnia-v5-change-report.buildInsomniaChangeReport 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.
vault-key-panel.VaultKeyPanel (cyclomatic 25) packages/insomnia/src/ui/components/settings/vault-key-panel.tsx:75— vault-key-panel.VaultKeyPanel has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 101, a function literal at line 108, a function literal at line 143, …). 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.
preview-mode-dropdown.PreviewModeDropdown (cyclomatic 25) packages/insomnia/src/ui/components/dropdowns/preview-mode-dropdown.tsx:22— preview-mode-dropdown.PreviewModeDropdown has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 8 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 70, 30, 122). 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.
shared.ScanResultsTable (cyclomatic 25) packages/insomnia/src/ui/components/modals/import-modal/shared.tsx:195— shared.ScanResultsTable has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 211, 258). 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.
mcp-url-bar.McpUrlActionBar (cyclomatic 25) packages/insomnia/src/ui/components/mcp/mcp-url-bar.tsx:48— mcp-url-bar.McpUrlActionBar 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 5 function literals inside it that branch (lines 98, 161, 191, …). 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.
hashicorp-credential-form.HashiCorpCredentialForm (cyclomatic 25) packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:36— hashicorp-credential-form.HashiCorpCredentialForm has cyclomatic complexity 25 (threshold 15). Of this number, 19 points are the body's own statements and 6 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.
sync-branches-modal.LocalBranchItem (cyclomatic 24) packages/insomnia/src/ui/components/modals/sync-branches-modal.tsx:27— sync-branches-modal.LocalBranchItem has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 44, 60, 75). 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.
event-log-view.getMessage (cyclomatic 24) packages/insomnia/src/ui/components/websockets/event-log-view.tsx:87— event-log-view.getMessage has cyclomatic complexity 24 (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.
openapi-3.generateParameterExample (cyclomatic 23) packages/insomnia/src/main/importers/importers/openapi-3.ts:557— openapi-3.generateParameterExample has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 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.
GitVCS.collectMergeConflicts (cyclomatic 23) packages/insomnia/src/sync/git/git-vcs.ts:1672— GitVCS.collectMergeConflicts 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.
private-host.isPrivateOrLoopbackHost (cyclomatic 23) packages/insomnia/src/main/private-host.ts:10— private-host.isPrivateOrLoopbackHost has cyclomatic complexity 23 (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.
lint-process.isPrivateOrLoopbackHost (cyclomatic 23) packages/insomnia/src/main/lint-process.mjs:17— lint-process.isPrivateOrLoopbackHost has cyclomatic complexity 23 (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.
import-modal.ScanResourcesForm (cyclomatic 23) packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:463— import-modal.ScanResourcesForm has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 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.
body-editor.BodyEditor (cyclomatic 23) packages/insomnia/src/ui/components/editors/body/body-editor.tsx:47— body-editor.BodyEditor 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 6 function items inside it that branch (renderBodyEditor, handleFileChange, a function literal at line 51, …). 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.
git-repository-select.GitRepositorySelect (cyclomatic 23) packages/insomnia/src/ui/components/git-credentials/git-repository-select.tsx:10— git-repository-select.GitRepositorySelect has cyclomatic complexity 23 (threshold 15). Of this number, 14 points are the body's own statements and 9 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.
request-pane.SocketIORequestPane (cyclomatic 23) packages/insomnia/src/ui/components/socket-io/request-pane.tsx:58— request-pane.SocketIORequestPane has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 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.
Response.to (cyclomatic 22) packages/insomnia-scripting-environment/src/objects/response.ts:208— Response.to has cyclomatic complexity 22 (threshold 15). 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 212, 322, 253, …). 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.
tokenize-args.tokenizeArgs (cyclomatic 22) packages/insomnia/src/common/templating/tokenize-args.ts:3— tokenize-args.tokenizeArgs 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.
git-project-branches-modal.GitProjectBranchesModal (cyclomatic 22) packages/insomnia/src/ui/components/modals/git-project-branches-modal.tsx:260— git-project-branches-modal.GitProjectBranchesModal 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 7 function literals inside it that branch (lines 323, 279, 293, …). 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.
git-branches-modal.GitBranchesModal (cyclomatic 22) packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:301— git-branches-modal.GitBranchesModal 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 7 function literals inside it that branch (lines 366, 321, 336, …). 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.
cookies-modal.CookieModifyModal (cyclomatic 22) packages/insomnia/src/ui/components/modals/cookies-modal.tsx:427— cookies-modal.CookieModifyModal has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 453, 537, 590). 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.
empty-node.EmptyNode (cyclomatic 22) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/empty-node.tsx:35— empty-node.EmptyNode has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 6 function items inside it that branch. 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.
curl.importCommand (cyclomatic 21) packages/insomnia/src/main/importers/importers/curl.ts:86— curl.importCommand has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
import.importResourcesToNewWorkspace (cyclomatic 21) packages/insomnia/src/common/import.ts:590— import.importResourcesToNewWorkspace 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, 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.
import.findExistingImportedWorkspace (cyclomatic 21) packages/insomnia/src/common/import.ts:772— import.findExistingImportedWorkspace has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
project.getAllLocalFiles (cyclomatic 21) packages/insomnia/src/common/project.ts:156— project.getAllLocalFiles has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 182). 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.
GitVCS.classifyStatus (cyclomatic 21) packages/insomnia/src/sync/git/git-vcs.ts:999— GitVCS.classifyStatus has cyclomatic complexity 21 (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.
common.writeEventLogAndNotify (cyclomatic 21) packages/insomnia/src/main/mcp/common.ts:239— common.writeEventLogAndNotify has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 4 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.
git-migration.$.MigrationView (cyclomatic 21) packages/insomnia/src/routes/git-migration.$.tsx:15— git-migration.$.MigrationView has cyclomatic complexity 21 (threshold 15). Of this number, 19 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.
import.scan.scanImportResources (cyclomatic 21) packages/insomnia/src/routes/import.scan.tsx:16— import.scan.scanImportResources has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
organization.$organizationId.project.$projectId.list-workspaces.getAllLocalFiles (cyclomatic 21) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.list-workspaces.tsx:16— organization.$organizationId.project.$projectId.list-workspaces.getAllLocalFiles has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 42). 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.
content-type-dropdown.ContentTypeDropdown::handleChangeMimeType (cyclomatic 21) packages/insomnia/src/ui/components/dropdowns/content-type-dropdown.tsx:48— content-type-dropdown.ContentTypeDropdown::handleChangeMimeType has cyclomatic complexity 21 (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.
request-settings-modal.RequestSettingsModal (cyclomatic 21) packages/insomnia/src/ui/components/modals/request-settings-modal.tsx:49— request-settings-modal.RequestSettingsModal has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to 5 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.
auth-input-row.AuthInputRow (cyclomatic 21) packages/insomnia/src/ui/components/editors/auth/components/auth-input-row.tsx:30— auth-input-row.AuthInputRow has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 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.
request-headers-editor.RequestHeadersEditor (cyclomatic 21) packages/insomnia/src/ui/components/editors/request-headers-editor.tsx:36— request-headers-editor.RequestHeadersEditor has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 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.
proto-files-modal.ProtoFilesModal (cyclomatic 21) packages/insomnia/src/ui/components/modals/proto-files-modal.tsx:170— proto-files-modal.ProtoFilesModal has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 6 function items inside it that branch (handleAddDirectory, a function literal at line 187, handleUpdate, …). 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.
cloud-service-credentials.CloudServiceCredentialList (cyclomatic 21) packages/insomnia/src/ui/components/settings/cloud-service-credentials.tsx:53— cloud-service-credentials.CloudServiceCredentialList has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 177, handleCreateCloudServiceCredential, a function literal at line 77). 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.
request.mergeClientCertificates (cyclomatic 20) packages/insomnia-scripting-environment/src/objects/request.ts:497— request.mergeClientCertificates 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.
VCS._merge (cyclomatic 20) packages/insomnia-vcs/src/vcs.ts:730— VCS._merge 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, 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.
parse-header-strings.parseHeaderStrings (cyclomatic 20) packages/insomnia/src/network/parse-header-strings.ts:33— parse-header-strings.parseHeaderStrings has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 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.
get-token.getToken (cyclomatic 20) packages/insomnia/src/main/network/o-auth-1/get-token.ts:43— get-token.getToken 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.
prompt-modal.PromptModal (cyclomatic 20) packages/insomnia/src/ui/components/modals/prompt-modal.tsx:46— prompt-modal.PromptModal has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 3 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.
api.protocol.registerInsomniaProtocols (cyclomatic 20) packages/insomnia/src/main/api.protocol.ts:23— api.protocol.registerInsomniaProtocols has cyclomatic complexity 20 (threshold 15). 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 68, 139, 52). 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.
git-service.relocateGitRepoAction (cyclomatic 20) packages/insomnia/src/main/git-service.ts:2037— git-service.relocateGitRepoAction 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.
git-service.pushToGitRemoteAction (cyclomatic 20) packages/insomnia/src/main/git-service.ts:2920— git-service.pushToGitRemoteAction 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.clientLoader (cyclomatic 20) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.tsx:85— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.clientLoader has cyclomatic complexity 20 (threshold 15). 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, 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.
sidebar-project-dropdown.ProjectDropdown (cyclomatic 20) packages/insomnia/src/ui/components/dropdowns/sidebar-project-dropdown.tsx:66— sidebar-project-dropdown.ProjectDropdown has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 5 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.
input-vault-key-modal.InputVaultKeyModal (cyclomatic 20) packages/insomnia/src/ui/components/modals/input-vault-key-modal.tsx:18— input-vault-key-modal.InputVaultKeyModal has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 84, 29, 45, …). 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.
tab.InsomniaTab (cyclomatic 20) packages/insomnia/src/ui/components/tabs/tab.tsx:81— tab.InsomniaTab has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function items inside it that branch (renderTabIcon, a function literal at line 177, a function literal at line 154, …). 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.
workspace-data.getAllCollectionChildrenAndMetasByWorkspaceIds (cyclomatic 19) packages/insomnia-data/node-src/services/app-data/workspace-data.ts:26— workspace-data.getAllCollectionChildrenAndMetasByWorkspaceIds has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 105, 135, 126, …). 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.
UrlMatchPattern.testPort (cyclomatic 19) packages/insomnia-scripting-environment/src/objects/urls.ts:547— UrlMatchPattern.testPort 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.
Cookie.parse (cyclomatic 19) packages/insomnia-scripting-environment/src/objects/cookies.ts:72— Cookie.parse has cyclomatic complexity 19 (threshold 15). Of this number, 13 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.
git-service.diffFileLoader (cyclomatic 19) packages/insomnia/src/main/git-service.ts:3518— git-service.diffFileLoader has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
generate-code-modal.GenerateCodeModal (cyclomatic 19) packages/insomnia/src/ui/components/modals/generate-code-modal.tsx:45— generate-code-modal.GenerateCodeModal 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.
body-tab-pane.SocketIOBodyTabPane (cyclomatic 19) packages/insomnia/src/ui/components/socket-io/body-tab-pane.tsx:50— body-tab-pane.SocketIOBodyTabPane has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 72, a function literal at line 113, handleChange, …). 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.
swagger-2.prepareBody (cyclomatic 18) packages/insomnia/src/main/importers/importers/swagger-2.ts:314— swagger-2.prepareBody 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.
templating-worker-database.readPluginModuleMap (cyclomatic 18) packages/insomnia/src/main/templating-worker-database.ts:228— templating-worker-database.readPluginModuleMap has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (walk, addModule). 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.
modal.Modal (cyclomatic 18) packages/insomnia/src/basic-components/modal.tsx:20— modal.Modal has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 53, a function literal at line 68, handleOpenChange). 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.
insomnia-v5-change-report.collectEntities (cyclomatic 18) packages/insomnia/src/common/insomnia-v5-change-report.ts:151— insomnia-v5-change-report.collectEntities has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (walkValue, walkEntity). 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.
git-service.checkoutGitBranchAction (cyclomatic 18) packages/insomnia/src/main/git-service.ts:2681— git-service.checkoutGitBranchAction 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.
organization.$organizationId.project.$projectId.workspace.update.clientAction (cyclomatic 18) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.update.tsx:19— organization.$organizationId.project.$projectId.workspace.update.clientAction 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.
mock-route-modal.MockRouteModal (cyclomatic 18) packages/insomnia/src/ui/components/modals/mock-route-modal.tsx:42— mock-route-modal.MockRouteModal has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 135, a function literal at line 146, …). 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.
git-remote-branch-select.GitRemoteBranchSelect (cyclomatic 18) packages/insomnia/src/ui/components/git-credentials/git-remote-branch-select.tsx:13— git-remote-branch-select.GitRemoteBranchSelect has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 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.
git-oauth-auth-banner.GitOauthAuthBanner (cyclomatic 18) packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx:37— git-oauth-auth-banner.GitOauthAuthBanner has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 47, 123, 111, …). 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.
use-sidebar-drag-and-drop.normalizeBoundaryTarget (cyclomatic 18) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:132— use-sidebar-drag-and-drop.normalizeBoundaryTarget 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.
action-bar.WebSocketActionBar (cyclomatic 18) packages/insomnia/src/ui/components/websockets/action-bar.tsx:31— action-bar.WebSocketActionBar has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 61, a function literal at line 101, a function literal at line 135, …). 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.
use-workspace-breadcrumb.useWorkspaceBreadcrumbs (cyclomatic 18) packages/insomnia/src/ui/components/workspace/use-workspace-breadcrumb.tsx:13— use-workspace-breadcrumb.useWorkspaceBreadcrumbs has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 46, 37). 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.
use-insomnia-navigation.getRouteIdForResource (cyclomatic 18) packages/insomnia/src/ui/hooks/use-insomnia-navigation.ts:174— use-insomnia-navigation.getRouteIdForResource 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.
request.mergeRequestBody (cyclomatic 17) packages/insomnia-scripting-environment/src/objects/request.ts:620— request.mergeRequestBody has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 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.
swagger-2.setupAuthentication (cyclomatic 17) packages/insomnia/src/main/importers/importers/swagger-2.ts:155— swagger-2.setupAuthentication has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 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.
insomnia-v5.getEnvironments (cyclomatic 17) packages/insomnia/src/common/insomnia-v5.ts:443— insomnia-v5.getEnvironments has cyclomatic complexity 17 (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.
import.resolveOperationId (cyclomatic 17) packages/insomnia/src/common/import.ts:710— import.resolveOperationId 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.normalizePropertyOrder (cyclomatic 17) packages/insomnia/src/common/insomnia-schema-migrations/index.ts:130— index.normalizePropertyOrder has cyclomatic complexity 17 (threshold 15). Of this number, 16 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.
deep-strict.deepStrict (cyclomatic 17) packages/insomnia/src/common/zod/deep-strict.ts:18— deep-strict.deepStrict has cyclomatic complexity 17 (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.
tooltip.Tooltip (cyclomatic 17) packages/insomnia/src/ui/components/tooltip.tsx:28— tooltip.Tooltip has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.clientLoader (cyclomatic 17) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.tsx:87— organization.$organizationId.project.$projectId.workspace.$workspaceId.clientLoader has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.mock-route.$mockRouteId.MockRouteRoute (cyclomatic 17) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.mock-route.$mockRouteId.tsx:148— organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.mock-route.$mockRouteId.MockRouteRoute has cyclomatic complexity 17 (threshold 15). 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 items inside it that branch (upsertBinOnRemoteFromResponse, upsertMockbinHar, a function literal at line 305). 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.
GitLabProvider.completeOAuth (cyclomatic 17) packages/insomnia/src/sync/git/providers/gitlab.ts:381— GitLabProvider.completeOAuth 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.
entity-splice.applyChange (cyclomatic 17) packages/insomnia/src/ui/components/modals/visual-diff/entity-splice.ts:314— entity-splice.applyChange 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.
sync-branches-modal.RemoteBranchItem (cyclomatic 17) packages/insomnia/src/ui/components/modals/sync-branches-modal.tsx:159— sync-branches-modal.RemoteBranchItem has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 175, 190). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
workspace-card-dropdown.WorkspaceCardDropdown (cyclomatic 17) packages/insomnia/src/ui/components/dropdowns/workspace-card-dropdown.tsx:94— workspace-card-dropdown.WorkspaceCardDropdown has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 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.
response-multipart-viewer.ResponseMultipartViewer (cyclomatic 17) packages/insomnia/src/ui/components/viewers/response-multipart-viewer.tsx:30— response-multipart-viewer.ResponseMultipartViewer 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 literals inside it that branch (lines 76, 47, 62, …). 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.
response-pane-utils.downloadResponseBody (cyclomatic 17) packages/insomnia/src/ui/components/panes/response-pane-utils.ts:6— response-pane-utils.downloadResponseBody 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.
credentials.GitProviderOAuthForm (cyclomatic 17) packages/insomnia/src/ui/components/settings/credentials.tsx:289— credentials.GitProviderOAuthForm 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, 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.
render.getRenderContext (cyclomatic 16) packages/insomnia/src/common/render.ts:715— render.getRenderContext has cyclomatic complexity 16 (threshold 15). 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, 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.
collection.flattenCollectionChildren (cyclomatic 16) packages/insomnia/src/common/collection.ts:9— collection.flattenCollectionChildren 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.
significant-diff-detection.findSystemChangeLines (cyclomatic 16) packages/insomnia/src/common/significant-diff-detection.ts:192— significant-diff-detection.findSystemChangeLines has cyclomatic complexity 16 (threshold 15). 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, 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.
RepoFileWatcher.flushWorkspacesToDisk (cyclomatic 16) packages/insomnia/src/sync/git/repo-file-watcher.ts:472— RepoFileWatcher.flushWorkspacesToDisk 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.
git-service.commitAndPushToGitRepoAction (cyclomatic 16) packages/insomnia/src/main/git-service.ts:2449— git-service.commitAndPushToGitRepoAction 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.
import.resources.clientAction (cyclomatic 16) packages/insomnia/src/routes/import.resources.tsx:52— import.resources.clientAction 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.
GitHubProvider.completeOAuth (cyclomatic 16) packages/insomnia/src/sync/git/providers/github.ts:293— GitHubProvider.completeOAuth has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
request-actions-dropdown.RequestActionsDropdown (cyclomatic 16) packages/insomnia/src/ui/components/dropdowns/request-actions-dropdown.tsx:49— request-actions-dropdown.RequestActionsDropdown has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 8 function items inside it that branch (copyAsCurl, a function literal at line 91, a function literal at line 101, …). 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.
response-history-dropdown.ResponseHistoryDropdown::renderResponseRow (cyclomatic 16) packages/insomnia/src/ui/components/dropdowns/response-history-dropdown.tsx:150— response-history-dropdown.ResponseHistoryDropdown::renderResponseRow 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.
cookies-modal.CookiesModal (cyclomatic 16) packages/insomnia/src/ui/components/modals/cookies-modal.tsx:53— cookies-modal.CookiesModal has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 183, handleFilterChange, handleCookieUpdate). 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.
use-project-navigation-sidebar-navigation.useProjectNavigationSidebarNavigation (cyclomatic 16) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-project-navigation-sidebar-navigation.ts:26— use-project-navigation-sidebar-navigation.useProjectNavigationSidebarNavigation has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 55, 102, 47). 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.
event-tab-pane.SocketIOEventTabPane (cyclomatic 16) packages/insomnia/src/ui/components/socket-io/event-tab-pane.tsx:57— event-tab-pane.SocketIOEventTabPane 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 items inside it that branch (handleChange, a function literal at line 75, handleDeleteEvent, …). 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.
edn.tokensToLines (cyclomatic 16) packages/insomnia/src/ui/utils/prettify/edn.ts:71— edn.tokensToLines 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.
router.getInitialEntry (cyclomatic 16) packages/insomnia/src/ui/utils/router.ts:88— router.getInitialEntry has cyclomatic complexity 16 (threshold 15). 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, 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.
Races the wall clock: custom with format "yyyy" returns the current 4-digit year packages/insomnia/src/common/templating/__tests__/local-template-tags.test.ts:395— This test reads `new Date()` and compares it against the value the code under test computed from its own clock read, compared exactly in `toBe(String(new Date().getFullYear()))`. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
FixmeComment packages/insomnia/src/basic-components/progress.tsx:12— // FIXME: use css variables for colors — 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.
project-navigation-sidebar.ProjectNavigationSidebarInner (cognitive 271) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:82— project-navigation-sidebar.ProjectNavigationSidebarInner has cognitive complexity 271 (threshold 15). Drivers by points: if/else 69 (125 pts), boolean chains 84, ternaries 28 (58 pts), loops 2 (3 pts), error handling 1 (nesting depth added 87). Of this number, 32 points are the body's own statements and 239 belong to 41 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.
tag-editor.TagEditor (cognitive 148) packages/insomnia/src/ui/components/templating/tag-editor.tsx:78— tag-editor.TagEditor has cognitive complexity 148 (threshold 15). Drivers by points: if/else 47 (64 pts), boolean chains 41, ternaries 19 (37 pts), loops 4, error handling 1 (2 pts) (nesting depth added 36). Most of this is not in the body itself: 13 of the 148 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 371, update, updateArg, …). 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.
organization.$organizationId.project.$projectId.update.clientAction (cognitive 125) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.update.tsx:48— organization.$organizationId.project.$projectId.update.clientAction has cognitive complexity 125 (threshold 15). Drivers by points: if/else 31 (85 pts), error handling 6 (14 pts), boolean chains 12, ternaries 5 (8 pts), loops 2 (6 pts) (nesting depth added 69). 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.
cli.go (cognitive 120) REDACTED:265— cli.go has cognitive complexity 120 (threshold 15). Drivers by points: if/else 39 (70 pts), boolean chains 24, ternaries 10 (12 pts), error handling 8 (11 pts), loops 2 (3 pts) (nesting depth added 37). Most of this is not in the body itself: 7 of the 120 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 533, a function literal at line 902, a function literal at line 376, …). 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.
app-data.updateAppDataOnDbChanges (cognitive 102) packages/insomnia/src/common/app-data.ts:239— app-data.updateAppDataOnDbChanges has cognitive complexity 102 (threshold 15). Drivers by points: if/else 27 (87 pts), loops 4 (11 pts), boolean chains 4 (nesting depth added 67). Of this number, 91 points are the body's own statements and 11 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.
git-project-sync-dropdown.GitProjectSyncDropdown (cognitive 102) packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:52— git-project-sync-dropdown.GitProjectSyncDropdown has cognitive complexity 102 (threshold 15). Drivers by points: boolean chains 36, if/else 28 (35 pts), ternaries 17 (30 pts), error handling 1 (nesting depth added 20). Of this number, 41 points are the body's own statements and 61 belong to 16 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.Runner (cognitive 101) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:155— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.Runner has cognitive complexity 101 (threshold 15). Drivers by points: if/else 28 (36 pts), boolean chains 27, ternaries 23 (27 pts), loops 3 (9 pts), error handling 2 (nesting depth added 18). Of this number, 27 points are the body's own statements and 74 belong to 27 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.
root.Root (cognitive 96) packages/insomnia/src/root.tsx:345— root.Root has cognitive complexity 96 (threshold 15). Drivers by points: if/else 44 (65 pts), boolean chains 21, ternaries 2 (6 pts), error handling 2 (4 pts) (nesting depth added 27). Most of this is not in the body itself: 1 of the 96 points is its own statement and the rest belongs to 12 function items inside it that branch (a function literal at line 458, handleCurlPaste, a function literal at line 410, …). 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.
insomnia-tab-context.InsomniaTabProvider (cognitive 94) packages/insomnia/src/ui/context/app/insomnia-tab-context.tsx:60— insomnia-tab-context.InsomniaTabProvider has cognitive complexity 94 (threshold 15). Drivers by points: if/else 43 (49 pts), boolean chains 32, ternaries 8 (12 pts), loops 1 (nesting depth added 10). Most of this is not in the body itself: 1 of the 94 points is its own statement and the rest belongs to 27 function literals inside it that branch (lines 190, 258, 568, …). 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.
auth.toPreRequestAuth (cognitive 92) packages/insomnia-scripting-environment/src/objects/auth.ts:597— auth.toPreRequestAuth has cognitive complexity 92 (threshold 15). Drivers by points: boolean chains 57, ternaries 15 (31 pts), match/switch 2 (3 pts), if/else 1 (nesting depth added 17). Of this number, 87 points are the body's own statements and 5 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.
project-settings-form.ProjectSettingsForm (cognitive 92) packages/insomnia/src/ui/components/project/project-settings-form.tsx:78— project-settings-form.ProjectSettingsForm has cognitive complexity 92 (threshold 15). Drivers by points: boolean chains 60, if/else 22 (24 pts), ternaries 8 (nesting depth added 2). Of this number, 53 points are the body's own statements and 39 belong to 16 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.
git-project-staging-modal.GeneratedCommitsForm (cognitive 87) packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:430— git-project-staging-modal.GeneratedCommitsForm has cognitive complexity 87 (threshold 15). Drivers by points: boolean chains 37, ternaries 18 (37 pts), if/else 10 (12 pts), error handling 1 (nesting depth added 21). Of this number, 45 points are the body's own statements and 42 belong to 12 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.
git-project-staging-modal.ManualCommitForm (cognitive 86) packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:819— git-project-staging-modal.ManualCommitForm has cognitive complexity 86 (threshold 15). Drivers by points: ternaries 21 (43 pts), boolean chains 25, if/else 15 (18 pts) (nesting depth added 25). Of this number, 54 points are the body's own statements and 32 belong to 11 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.
graph-ql-editor.GraphQLEditor (cognitive 81) packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx:232— graph-ql-editor.GraphQLEditor has cognitive complexity 81 (threshold 15). Drivers by points: boolean chains 36, if/else 23 (28 pts), ternaries 8 (10 pts), error handling 5, loops 2 (nesting depth added 7). Of this number, 23 points are the body's own statements and 58 belong to 15 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.
use-sidebar-drag-and-drop.canDrop (cognitive 81) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:252— use-sidebar-drag-and-drop.canDrop has cognitive complexity 81 (threshold 15). Drivers by points: if/else 26 (56 pts), boolean chains 22, ternaries 2 (3 pts) (nesting depth added 31). Of this number, 73 points are the body's own statements and 8 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.
organization.$organizationId.project.$projectId._index.Component (cognitive 79) packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:79— organization.$organizationId.project.$projectId._index.Component has cognitive complexity 79 (threshold 15). Drivers by points: boolean chains 44, ternaries 13 (24 pts), if/else 8 (11 pts) (nesting depth added 14). Of this number, 34 points are the body's own statements and 45 belong to 16 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.
key-value-editor.KeyValueEditor (cognitive 78) packages/insomnia/src/ui/components/key-value-editor/key-value-editor.tsx:81— key-value-editor.KeyValueEditor has cognitive complexity 78 (threshold 15). Drivers by points: boolean chains 48, if/else 16, ternaries 13 (14 pts) (nesting depth added 1). Of this number, 28 points are the body's own statements and 50 belong to 18 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.traversePluginPath (cognitive 77) packages/insomnia/src/plugins/index.ts:189— index.traversePluginPath has cognitive complexity 77 (threshold 15). Drivers by points: if/else 17 (46 pts), boolean chains 15, ternaries 2 (7 pts), loops 3 (6 pts), error handling 1 (3 pts) (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mcp-pane.McpPane (cognitive 77) packages/insomnia/src/ui/components/mcp/mcp-pane.tsx:89— mcp-pane.McpPane has cognitive complexity 77 (threshold 15). Drivers by points: if/else 22 (29 pts), boolean chains 27, ternaries 12 (17 pts), error handling 2 (4 pts) (nesting depth added 14). Most of this is not in the body itself: 5 of the 77 points are its own statements and the rest belongs to 21 function items inside it that branch (a function literal at line 119, a function literal at line 347, getServerCapabilities, …). 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.
use-sidebar-drag-and-drop.useSidebarDragAndDrop (cognitive 76) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:595— use-sidebar-drag-and-drop.useSidebarDragAndDrop has cognitive complexity 76 (threshold 15). Drivers by points: if/else 30 (43 pts), boolean chains 20, ternaries 8 (13 pts) (nesting depth added 18). Of this number, 65 points are the body's own statements and 11 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.
sync-dropdown.SyncDropdown (cognitive 75) packages/insomnia/src/ui/components/dropdowns/sync-dropdown.tsx:42— sync-dropdown.SyncDropdown has cognitive complexity 75 (threshold 15). Drivers by points: boolean chains 37, ternaries 18 (28 pts), if/else 10 (nesting depth added 10). Of this number, 56 points are the body's own statements and 19 belong to 7 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.
libcurl-promise.createConfiguredCurlInstance (cognitive 73) packages/insomnia/src/main/network/libcurl-promise.ts:344— libcurl-promise.createConfiguredCurlInstance has cognitive complexity 73 (threshold 15). Drivers by points: if/else 23 (29 pts), ternaries 10 (26 pts), boolean chains 11, loops 2 (5 pts), error handling 1 (2 pts) (nesting depth added 26). Of this number, 69 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.
GitVCS.diff (cognitive 72) packages/insomnia/src/sync/git/git-vcs.ts:642— GitVCS.diff has cognitive complexity 72 (threshold 15). Drivers by points: if/else 26 (38 pts), boolean chains 26, ternaries 6, error handling 1 (2 pts) (nesting depth added 13). None of this is in the body itself: all 72 points belong to 5 function items inside it that branch (a function literal at line 665, a function literal at line 840, formatDiffChanges, …). 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.
import-modal.ImportModal (cognitive 71) packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:205— import-modal.ImportModal has cognitive complexity 71 (threshold 15). Drivers by points: boolean chains 30, if/else 18 (27 pts), ternaries 8 (14 pts) (nesting depth added 15). Of this number, 20 points are the body's own statements and 51 belong to 10 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.
v5.1.cleanHeadersAndParameters (cognitive 67) packages/insomnia/src/common/insomnia-schema-migrations/v5.1.ts:67— v5.1.cleanHeadersAndParameters has cognitive complexity 67 (threshold 15). Drivers by points: if/else 16 (47 pts), boolean chains 18, loops 1 (2 pts) (nesting depth added 32). Of this number, 31 points are the body's own statements and 36 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.
tab-list.OrganizationTabList (cognitive 66) packages/insomnia/src/ui/components/tabs/tab-list.tsx:45— tab-list.OrganizationTabList has cognitive complexity 66 (threshold 15). Drivers by points: if/else 36 (44 pts), boolean chains 13, ternaries 4 (7 pts), loops 1, match/switch 1 (nesting depth added 11). Most of this is not in the body itself: 10 of the 66 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 160, a function literal at line 250, a function literal at line 136, …). 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.
websocket.openWebSocketConnection (cognitive 65) packages/insomnia/src/main/network/websocket.ts:174— websocket.openWebSocketConnection has cognitive complexity 65 (threshold 15). Drivers by points: if/else 23 (34 pts), boolean chains 17, ternaries 7 (13 pts), error handling 1 (nesting depth added 17). Of this number, 49 points are the body's own statements and 16 belong to 7 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.
url.Url (cognitive 63) packages/insomnia/src/ui/components/settings/llms/url.tsx:40— url.Url has cognitive complexity 63 (threshold 15). Drivers by points: boolean chains 25, if/else 18 (24 pts), ternaries 8 (12 pts), error handling 2 (nesting depth added 10). Of this number, 19 points are the body's own statements and 44 belong to 8 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.
insomnia-v5.getCollection (cognitive 62) packages/insomnia/src/common/insomnia-v5.ts:665— insomnia-v5.getCollection has cognitive complexity 62 (threshold 15). Drivers by points: boolean chains 36, if/else 11 (26 pts) (nesting depth added 15). Most of this is not in the body itself: 3 of the 62 points are its own statements and the rest belongs to one function literal inside it that branches (line 675). 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.Debug (cognitive 62) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.tsx:164— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.Debug has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 20 (26 pts), boolean chains 23, if/else 10 (12 pts), loops 1 (nesting depth added 8). Of this number, 26 points are the body's own statements and 36 belong to 21 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.
GitVCS.collectMergeConflicts (cognitive 61) packages/insomnia/src/sync/git/git-vcs.ts:1672— GitVCS.collectMergeConflicts has cognitive complexity 61 (threshold 15). Drivers by points: if/else 13 (41 pts), boolean chains 6, loops 2 (5 pts), ternaries 1 (5 pts), error handling 1 (4 pts) (nesting depth added 38). 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.
git-service.cloneGitRepoAction (cognitive 59) packages/insomnia/src/main/git-service.ts:1417— git-service.cloneGitRepoAction has cognitive complexity 59 (threshold 15). Drivers by points: if/else 30 (54 pts), error handling 3 (4 pts), boolean chains 1 (nesting depth added 25). Of this number, 55 points are the body's own statements and 4 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.clientAction (cognitive 59) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:960— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.clientAction has cognitive complexity 59 (threshold 15). Drivers by points: if/else 13 (36 pts), ternaries 4 (9 pts), boolean chains 6, error handling 2 (4 pts), loops 3 (4 pts) (nesting depth added 31). Of this number, 50 points are the body's own statements and 9 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.
response-viewer.ResponseViewer (cognitive 59) packages/insomnia/src/ui/components/viewers/response-viewer.tsx:72— response-viewer.ResponseViewer has cognitive complexity 59 (threshold 15). Drivers by points: if/else 22 (25 pts), boolean chains 19, ternaries 6 (9 pts), error handling 5 (6 pts) (nesting depth added 7). Of this number, 33 points are the body's own statements and 26 belong to 8 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.
realtime-response-pane.RealtimeActiveResponsePane (cognitive 58) packages/insomnia/src/ui/components/websockets/realtime-response-pane.tsx:215— realtime-response-pane.RealtimeActiveResponsePane has cognitive complexity 58 (threshold 15). Drivers by points: boolean chains 23, if/else 13 (18 pts), ternaries 10 (17 pts) (nesting depth added 12). Of this number, 26 points are the body's own statements and 32 belong to 6 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.
new-workspace-modal.NewWorkspaceModal (cognitive 57) packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx:52— new-workspace-modal.NewWorkspaceModal has cognitive complexity 57 (threshold 15). Drivers by points: boolean chains 42, ternaries 8, if/else 7. Most of this is not in the body itself: 9 of the 57 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 211, a function literal at line 132, a function literal at line 119, …). 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.
git-project-staging-modal.OriginalGitProjectStagingModal (cognitive 56) packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:1550— git-project-staging-modal.OriginalGitProjectStagingModal has cognitive complexity 56 (threshold 15). Drivers by points: boolean chains 31, ternaries 9 (13 pts), if/else 11 (12 pts) (nesting depth added 5). Most of this is not in the body itself: 14 of the 56 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 1763, a function literal at line 1623, afterStageOrUnstage, …). 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.Component (cognitive 54) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:62— organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.Component has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 22, ternaries 13 (21 pts), if/else 10 (11 pts) (nesting depth added 9). Of this number, 34 points are the body's own statements and 20 belong to 11 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.
git-sync-dropdown.GitSyncDropdown (cognitive 54) packages/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:43— git-sync-dropdown.GitSyncDropdown has cognitive complexity 54 (threshold 15). Drivers by points: ternaries 20 (26 pts), boolean chains 13, if/else 10 (13 pts), error handling 1 (2 pts) (nesting depth added 10). Of this number, 32 points are the body's own statements and 22 belong to 8 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.
workspace-environments-edit-modal.WorkspaceEnvironmentsEditModal (cognitive 54) packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx:44— workspace-environments-edit-modal.WorkspaceEnvironmentsEditModal has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 22, ternaries 13 (21 pts), if/else 10 (11 pts) (nesting depth added 9). Of this number, 18 points are the body's own statements and 36 belong to 13 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.
insomnia-event-stream-context.InsomniaEventStreamProvider (cognitive 53) packages/insomnia/src/ui/context/app/insomnia-event-stream-context.tsx:88— insomnia-event-stream-context.InsomniaEventStreamProvider has cognitive complexity 53 (threshold 15). Drivers by points: if/else 18 (31 pts), boolean chains 16, error handling 3 (6 pts) (nesting depth added 16). Most of this is not in the body itself: 1 of the 53 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 149, 113, 142, …). 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.
get-token.getOAuth2Token (cognitive 52) packages/insomnia/src/main/network/o-auth-2/get-token.ts:167— get-token.getOAuth2Token has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (19 pts), ternaries 8 (15 pts), boolean chains 9, error handling 4 (9 pts) (nesting depth added 16). Of this number, 50 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.
main.registerMainHandlers (cognitive 52) packages/insomnia/src/main/ipc/main.ts:384— main.registerMainHandlers has cognitive complexity 52 (threshold 15). Drivers by points: if/else 32 (34 pts), ternaries 4 (7 pts), error handling 5 (6 pts), boolean chains 4, loops 1 (nesting depth added 6). None of this is in the body itself: all 52 points belong to 19 function literals inside it that branch (lines 495, 614, 757, …). 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.
event-view.MessageEventView (cognitive 49) packages/insomnia/src/ui/components/mcp/event-view.tsx:35— event-view.MessageEventView has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 15, error handling 3 (8 pts), ternaries 4 (5 pts) (nesting depth added 13). Of this number, 20 points are the body's own statements and 29 belong to 9 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.
mcp-request-pane.McpRequestPane (cognitive 49) packages/insomnia/src/ui/components/mcp/mcp-request-pane.tsx:94— mcp-request-pane.McpRequestPane has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 28, if/else 15 (16 pts), ternaries 2 (3 pts), error handling 2 (nesting depth added 2). Of this number, 20 points are the body's own statements and 29 belong to 8 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.
project-create-form.ProjectCreateForm (cognitive 48) packages/insomnia/src/ui/components/project/project-create-form.tsx:40— project-create-form.ProjectCreateForm has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 29, if/else 13 (14 pts), ternaries 5 (nesting depth added 1). Of this number, 25 points are the body's own statements and 23 belong to 10 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.
request-url-bar.RequestUrlBar (cognitive 48) packages/insomnia/src/ui/components/request-url-bar.tsx:59— request-url-bar.RequestUrlBar has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 11 (18 pts), if/else 11 (16 pts), boolean chains 13, error handling 1 (nesting depth added 12). Of this number, 20 points are the body's own statements and 28 belong to 9 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.threeWayMerge (cognitive 47) packages/insomnia-vcs/src/util.ts:67— util.threeWayMerge has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (30 pts), boolean chains 16, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
import.findExistingImportedWorkspace (cognitive 47) packages/insomnia/src/common/import.ts:772— import.findExistingImportedWorkspace has cognitive complexity 47 (threshold 15). Drivers by points: if/else 10 (35 pts), loops 4 (7 pts), boolean chains 4, ternaries 1 (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.
command-palette.CommandPaletteCombobox (cognitive 47) packages/insomnia/src/ui/components/command-palette.tsx:102— command-palette.CommandPaletteCombobox has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 33, if/else 6 (7 pts), ternaries 6 (7 pts) (nesting depth added 2). Of this number, 24 points are the body's own statements and 23 belong to 19 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.
window-utils.createWindow (cognitive 46) REDACTED:204— window-utils.createWindow has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 12, ternaries 9, error handling 1 (2 pts), loops 1 (nesting depth added 2). Of this number, 21 points are the body's own statements and 25 belong to 15 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.
transport-streamable-http.wrappedFetch (cognitive 46) packages/insomnia/src/main/mcp/transport-streamable-http.ts:82— transport-streamable-http.wrappedFetch has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 16, if/else 9 (15 pts), ternaries 6 (11 pts), error handling 2 (4 pts) (nesting depth added 13). Of this number, 34 points are the body's own statements and 12 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.
sync-staging-modal.SyncStagingModal (cognitive 46) packages/insomnia/src/ui/components/modals/sync-staging-modal.tsx:113— sync-staging-modal.SyncStagingModal has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 18 (22 pts), boolean chains 19, if/else 4 (5 pts) (nesting depth added 5). Most of this is not in the body itself: 1 of the 46 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 218, 329, 401, …). 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.
render.render::next (cognitive 44) packages/insomnia/src/common/render.ts:613— render.render::next has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 9, loops 2 (4 pts), ternaries 1 (4 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.
git-migration.$.MigrationView (cognitive 44) packages/insomnia/src/routes/git-migration.$.tsx:15— git-migration.$.MigrationView has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 18 (42 pts), boolean chains 2 (nesting depth added 24). Of this number, 42 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.
diff-engine.collectEntities (cognitive 44) packages/insomnia/src/ui/components/modals/visual-diff/diff-engine.ts:353— diff-engine.collectEntities has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 13, ternaries 3 (9 pts), loops 1 (2 pts) (nesting depth added 11). Of this number, 30 points are the body's own statements and 14 belong to 4 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.
invite-modal.MemberListItem (cognitive 44) packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx:291— invite-modal.MemberListItem has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 21, if/else 10 (13 pts), ternaries 8 (10 pts) (nesting depth added 5). Of this number, 27 points are the body's own statements and 17 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.
organization.$organizationId.project.$projectId.workspace.new.clientAction (cognitive 43) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.new.tsx:41— organization.$organizationId.project.$projectId.workspace.new.clientAction has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (26 pts), boolean chains 13, ternaries 2 (3 pts), error handling 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.
import.importResourcesToWorkspace (cognitive 42) packages/insomnia/src/common/import.ts:455— import.importResourcesToWorkspace has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 11, loops 4 (7 pts), ternaries 1 (3 pts) (nesting depth added 16). Of this number, 34 points are the body's own statements and 8 belong to 4 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.
plugins.Plugins (cognitive 42) packages/insomnia/src/ui/components/settings/plugins.tsx:71— plugins.Plugins has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 21, ternaries 14 (16 pts), if/else 4, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 12 of the 42 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 497, 203, 566, …). 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.
render.buildRenderContext (cognitive 41) packages/insomnia/src/common/render.ts:355— render.buildRenderContext has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (26 pts), loops 8 (11 pts), boolean chains 4 (nesting depth added 15). Of this number, 33 points are the body's own statements and 8 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.
database-nedb.createNedbDatabase (cognitive 40) packages/insomnia-data/node-src/database/database-nedb.ts:47— database-nedb.createNedbDatabase has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (18 pts), loops 10 (14 pts), boolean chains 5, ternaries 3 (nesting depth added 6). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 13 function items inside it that branch (a function literal at line 565, flushChangesImpl, a function literal at line 530, …). 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.
command-search.commandSearch (cognitive 40) packages/insomnia-data/node-src/services/helpers/command-search.ts:19— command-search.commandSearch has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 12, loops 5, ternaries 4 (nesting depth added 6). Most of this is not in the body itself: 14 of the 40 points are its own statements and the rest belongs to 8 function items inside it that branch (getRequestGroups, mapRequest, mapFile, …). 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.
common.writeEventLogAndNotify (cognitive 40) packages/insomnia/src/main/mcp/common.ts:239— common.writeEventLogAndNotify has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (32 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 17). Of this number, 33 points are the body's own statements and 7 belong to 4 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.
header-plan-indicator.HeaderPlanIndicator (cognitive 40) packages/insomnia/src/ui/components/header-plan-indicator.tsx:23— header-plan-indicator.HeaderPlanIndicator has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 21, ternaries 11 (13 pts), if/else 6 (nesting depth added 2). Of this number, 33 points are the body's own statements and 7 belong to 5 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.
invite-form.InviteForm (cognitive 39) packages/insomnia/src/ui/components/modals/invite-modal/invite-form.tsx:115— invite-form.InviteForm has cognitive complexity 39 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 11, ternaries 5 (7 pts) (nesting depth added 4). Most of this is not in the body itself: 12 of the 39 points are its own statements and the rest belongs to 11 function items inside it that branch (addEmail, a function literal at line 416, a function literal at line 165, …). 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.
request-group-pane.RequestGroupPane (cognitive 39) packages/insomnia/src/ui/components/panes/request-group-pane.tsx:25— request-group-pane.RequestGroupPane has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 18, ternaries 8 (12 pts), if/else 6 (7 pts), error handling 1 (2 pts) (nesting depth added 6). Of this number, 26 points are the body's own statements and 13 belong to 6 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.
network.tryToExecuteScript (cognitive 38) REDACTED:489— network.tryToExecuteScript has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 21, if/else 8, ternaries 5 (8 pts), error handling 1 (nesting depth added 3). Of this number, 32 points are the body's own statements and 6 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.
sandbox.checkSandboxViolations (cognitive 38) packages/insomnia/src/scripting/sandbox.ts:74— sandbox.checkSandboxViolations has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 12, error handling 1 (2 pts), loops 2, ternaries 1 (nesting depth added 3). Of this number, 36 points are the body's own statements and 2 belong to one function item 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.
api.protocol.registerInsomniaProtocols (cognitive 38) packages/insomnia/src/main/api.protocol.ts:23— api.protocol.registerInsomniaProtocols has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (22 pts), ternaries 3 (9 pts), error handling 2 (4 pts), boolean chains 3 (nesting depth added 17). Most of this is not in the body itself: 4 of the 38 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 68, 139, 52). 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.
curl.openCurlConnection (cognitive 38) packages/insomnia/src/main/network/curl.ts:137— curl.openCurlConnection has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 16, if/else 11 (16 pts), loops 4, error handling 1, ternaries 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 22 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.
get-auth-header.getAuthHeader (cognitive 37) packages/insomnia/src/main/network/get-auth-header.ts:28— get-auth-header.getAuthHeader has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 8, error handling 2 (4 pts), ternaries 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.
GitVCS.filesStatus (cognitive 37) packages/insomnia/src/sync/git/git-vcs.ts:482— GitVCS.filesStatus has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 15, error handling 1 (3 pts), ternaries 2 (nesting depth added 5). None of this is in the body itself: all 37 points belong to one function literal inside it that branches (line 501). 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.
invoke-method.invokePluginMethod (cognitive 37) packages/insomnia/src/plugins/invoke-method.ts:70— invoke-method.invokePluginMethod has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 2 (8 pts), error handling 2 (6 pts), loops 2 (4 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 21). Of this number, 35 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
import.scan.scanImportResources (cognitive 36) packages/insomnia/src/routes/import.scan.tsx:16— import.scan.scanImportResources has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (19 pts), error handling 3 (9 pts), boolean chains 4, loops 2 (4 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.
first-request-creation.FirstRequestCreation (cognitive 36) packages/insomnia/src/ui/components/first-request-creation.tsx:128— first-request-creation.FirstRequestCreation has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16, ternaries 6 (8 pts), boolean chains 7, error handling 4 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 3 of the 36 points are its own statements and the rest belongs to 13 function items inside it that branch (handleCreateRequest, a function literal at line 373, handleCreateGithubLookupRequest, …). 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.
mcp-url-bar.McpUrlActionBar (cognitive 36) packages/insomnia/src/ui/components/mcp/mcp-url-bar.tsx:48— mcp-url-bar.McpUrlActionBar has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (26 pts), ternaries 3 (5 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 12). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 98, 161, 191, …). 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.
insomnia-v5.getInsomniaV5DataExport (cognitive 35) packages/insomnia/src/common/insomnia-v5.ts:1043— insomnia-v5.getInsomniaV5DataExport has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17, boolean chains 9, ternaries 3 (5 pts), error handling 3 (4 pts) (nesting depth added 3). Most of this is not in the body itself: 12 of the 35 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 1114, getScriptFromResources, getSpecFromResources, …). 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.
import.resolveOperationId (cognitive 35) packages/insomnia/src/common/import.ts:710— import.resolveOperationId has cognitive complexity 35 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 3 (6 pts), boolean chains 5, ternaries 1 (5 pts), error handling 1 (2 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.
insomnia-fetch.insomniaFetch (cognitive 35) packages/insomnia/src/common/insomnia-fetch.ts:22— insomnia-fetch.insomniaFetch has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 7 (8 pts), boolean chains 6, error handling 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.new.clientAction (cognitive 35) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.new.tsx:27— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.new.clientAction has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 20, if/else 8 (9 pts), ternaries 4, error handling 1 (2 pts) (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.
organization.$organizationId.project.$projectId.workspace.new.createMockServer (cognitive 35) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.new.tsx:302— organization.$organizationId.project.$projectId.workspace.new.createMockServer has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 11, error handling 3 (6 pts), ternaries 3 (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.
get-token.getExistingAccessTokenAndRefreshIfExpired (cognitive 34) packages/insomnia/src/main/network/o-auth-2/get-token.ts:406— get-token.getExistingAccessTokenAndRefreshIfExpired has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 10, ternaries 1 (2 pts), error handling 1 (nesting depth added 5). 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, 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.
import-export.ImportExport (cognitive 34) packages/insomnia/src/ui/components/settings/import-export.tsx:706— import-export.ImportExport has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 25, if/else 5 (6 pts), error handling 2 (3 pts) (nesting depth added 2). Of this number, 20 points are the body's own statements and 14 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.
GitVCS.fileStatus (cognitive 34) packages/insomnia/src/sync/git/git-vcs.ts:346— GitVCS.fileStatus has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 13, if/else 12, error handling 4 (7 pts), ternaries 2 (nesting depth added 3). None of this is in the body itself: all 34 points belong to 2 function literals inside it that branch (lines 355, 442). 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.
konnect-settings-modal.KonnectSettingsModal (cognitive 34) packages/insomnia/src/ui/components/modals/konnect-settings-modal.tsx:14— konnect-settings-modal.KonnectSettingsModal has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 12 (18 pts), if/else 7 (9 pts), boolean chains 6, loops 1 (nesting depth added 8). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 127, validateAndSetStatus, handleConnect, …). 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.
swagger-2.setupAuthentication (cognitive 33) packages/insomnia/src/main/importers/importers/swagger-2.ts:155— swagger-2.setupAuthentication has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (30 pts), loops 2, boolean chains 1 (nesting depth added 17). Of this number, 30 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.
tokenize-args.tokenizeArgs (cognitive 33) packages/insomnia/src/common/templating/tokenize-args.ts:3— tokenize-args.tokenizeArgs has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 9, 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.
plugin-name.validatePluginName (cognitive 33) packages/insomnia/src/common/utils/plugin-name.ts:12— plugin-name.validatePluginName has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (25 pts), boolean chains 8 (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.
response-history-dropdown.ResponseHistoryDropdown (cognitive 33) packages/insomnia/src/ui/components/dropdowns/response-history-dropdown.tsx:33— response-history-dropdown.ResponseHistoryDropdown has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 10 (11 pts), boolean chains 9 (nesting depth added 2). Most of this is not in the body itself: 5 of the 33 points are its own statements and the rest belongs to 6 function items inside it that branch (renderResponseRow, a function literal at line 124, a function literal at line 84, …). 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.
sidebar-workspace-dropdown.SidebarWorkspaceDropdown (cognitive 33) packages/insomnia/src/ui/components/dropdowns/sidebar-workspace-dropdown.tsx:77— sidebar-workspace-dropdown.SidebarWorkspaceDropdown has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 10, if/else 7, error handling 2 (nesting depth added 3). Most of this is not in the body itself: 15 of the 33 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 403, a function literal at line 276, a function literal at line 332, …). 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.
row.Row (cognitive 33) packages/insomnia/src/ui/components/key-value-editor/row.tsx:49— row.Row has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 13 (21 pts), boolean chains 12 (nesting depth added 8). Of this number, 27 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.
openai.OpenAI (cognitive 33) packages/insomnia/src/ui/components/settings/llms/openai.tsx:14— openai.OpenAI has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 18, if/else 9 (13 pts), error handling 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 13 of the 33 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 33, 81, 56, …). 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.
edn.tokensToLines (cognitive 33) packages/insomnia/src/ui/utils/prettify/edn.ts:71— edn.tokensToLines has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 1 (4 pts), boolean chains 3, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
send-request.requestToCurlOptions (cognitive 32) packages/insomnia-scripting-environment/src/objects/send-request.ts:43— send-request.requestToCurlOptions has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 8 (16 pts), boolean chains 9, if/else 3 (4 pts), match/switch 1 (3 pts) (nesting depth added 11). Of this number, 28 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.
VCS.status (cognitive 32) packages/insomnia-vcs/src/vcs.ts:165— VCS.status has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 3 (11 pts), ternaries 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openapi-3.generateParameterExample (cognitive 32) packages/insomnia/src/main/importers/importers/openapi-3.ts:557— openapi-3.generateParameterExample has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 5, loops 2 (5 pts) (nesting depth added 13). Of this number, 28 points are the body's own statements and 4 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.
environment-picker.EnvironmentPicker (cognitive 32) packages/insomnia/src/ui/components/environment-picker.tsx:41— environment-picker.EnvironmentPicker has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 16, ternaries 9 (15 pts), if/else 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 16 belong to 5 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.
gemini.Gemini (cognitive 32) packages/insomnia/src/ui/components/settings/llms/gemini.tsx:14— gemini.Gemini has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 17, if/else 9 (13 pts), error handling 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 13 of the 32 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 33, 77, 85). 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.
json.jsonPrettify (cognitive 32) packages/insomnia/src/ui/utils/prettify/json.ts:53— json.jsonPrettify has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 2, error handling 1 (2 pts), match/switch 1 (2 pts), 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.
curl.importCommand (cognitive 31) packages/insomnia/src/main/importers/importers/curl.ts:86— curl.importCommand has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 8, 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.
insomnia-v5-change-report.buildInsomniaChangeReport (cognitive 31) packages/insomnia/src/common/insomnia-v5-change-report.ts:267— insomnia-v5-change-report.buildInsomniaChangeReport has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 6 (8 pts), loops 3, error handling 2, 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.
GitVCS.discardChanges (cognitive 31) packages/insomnia/src/sync/git/git-vcs.ts:2112— GitVCS.discardChanges has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (29 pts), boolean chains 1, loops 1 (nesting depth added 20). 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.
mock-response-extractor.MockResponseExtractor (cognitive 31) packages/insomnia/src/ui/components/editors/mock-response-extractor.tsx:19— mock-response-extractor.MockResponseExtractor has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 8, ternaries 6 (7 pts), error handling 1 (nesting depth added 5). Of this number, 23 points are the body's own statements and 8 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.
response-pane.ResponsePane (cognitive 31) packages/insomnia/src/ui/components/panes/response-pane.tsx:43— response-pane.ResponsePane has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 10, if/else 10, ternaries 8 (10 pts), error handling 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 14 belong to 7 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.
Response.to (cognitive 29) packages/insomnia-scripting-environment/src/objects/response.ts:208— Response.to has cognitive complexity 29 (threshold 15). Drivers by points: if/else 22 (24 pts), error handling 4, boolean chains 1 (nesting depth added 2). None of this is in the body itself: all 29 points belong to 9 function literals inside it that branch (lines 322, 212, 253, …). 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.
import.importResourcesToNewWorkspace (cognitive 29) packages/insomnia/src/common/import.ts:590— import.importResourcesToNewWorkspace has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 7, loops 2, ternaries 1 (2 pts) (nesting depth added 7). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sync-merge-modal.SyncMergeModal (cognitive 29) packages/insomnia/src/ui/components/modals/sync-merge-modal.tsx:62— sync-merge-modal.SyncMergeModal has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 16, if/else 7 (8 pts), error handling 2 (4 pts), ternaries 1 (nesting depth added 3). None of this is in the body itself: all 29 points belong to 13 function literals inside it that branch (lines 187, 79, 91, …). 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.
GitVCS.buildManualResolutionFromTrees (cognitive 29) packages/insomnia/src/sync/git/git-vcs.ts:1457— GitVCS.buildManualResolutionFromTrees has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (18 pts), boolean chains 4, ternaries 1 (4 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.
sidebar-shortcut-actions-dropdown.SidebarShortcutActionsDropdown (cognitive 29) packages/insomnia/src/ui/components/dropdowns/sidebar-shortcut-actions-dropdown.tsx:33— sidebar-shortcut-actions-dropdown.SidebarShortcutActionsDropdown has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 11, if/else 3 (nesting depth added 6). Of this number, 15 points are the body's own statements and 14 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.
import-projects-modal.ImportProjectsModal (cognitive 29) packages/insomnia/src/ui/components/modals/import-modal/import-projects-modal.tsx:494— import-projects-modal.ImportProjectsModal has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 7 (9 pts), boolean chains 5, error handling 2, loops 1 (nesting depth added 3). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 5 function items inside it that branch (processBulkProjectImport::startImportForProject, processBulkProjectImport, handleComplete, …). 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.
ai-settings.AISettings (cognitive 29) packages/insomnia/src/ui/components/settings/ai-settings.tsx:13— ai-settings.AISettings has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 23, ternaries 4, if/else 2. Of this number, 22 points are the body's own statements and 7 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.
credentials.GitCredentialsList (cognitive 29) packages/insomnia/src/ui/components/settings/credentials.tsx:481— credentials.GitCredentialsList has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 16, if/else 6 (7 pts), ternaries 3 (6 pts) (nesting depth added 4). Most of this is not in the body itself: 5 of the 29 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 625, 522, 504, …). 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.
libcurl-promise.curlRequest (cognitive 28) packages/insomnia/src/main/network/libcurl-promise.ts:104— libcurl-promise.curlRequest has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 16, if/else 11, error handling 1. None of this is in the body itself: all 28 points belong to 5 function literals inside it that branch (lines 105, 202, 250, …). 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.
GitVCS.continueMerge (cognitive 28) packages/insomnia/src/sync/git/git-vcs.ts:1829— GitVCS.continueMerge has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (18 pts), error handling 2 (8 pts), loops 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sync.syncHttpRoute (cognitive 28) packages/insomnia/src/konnect/sync.ts:285— sync.syncHttpRoute has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (6 pts), ternaries 2 (6 pts), boolean chains 3 (nesting depth added 16). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
entity-diff-list.EntityDiffList (cognitive 28) packages/insomnia/src/ui/components/modals/visual-diff/entity-diff-list.tsx:64— entity-diff-list.EntityDiffList has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 11 (12 pts), boolean chains 9, if/else 6, match/switch 1 (nesting depth added 1). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 235, 145, 107, …). 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.
claude.Claude (cognitive 28) packages/insomnia/src/ui/components/settings/llms/claude.tsx:13— claude.Claude has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 17, if/else 7 (9 pts), error handling 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 32, 73, 81). 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.normalizePropertyOrder (cognitive 27) packages/insomnia/src/common/insomnia-schema-migrations/index.ts:130— index.normalizePropertyOrder has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 4 (8 pts), boolean chains 3 (nesting depth added 13). Of this number, 25 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.
git-service.relocateGitRepoAction (cognitive 27) packages/insomnia/src/main/git-service.ts:2037— git-service.relocateGitRepoAction has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (17 pts), error handling 5 (6 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
git-service.checkoutGitBranchAction (cognitive 27) packages/insomnia/src/main/git-service.ts:2681— git-service.checkoutGitBranchAction has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 5 (9 pts), error handling 4 (6 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.clientAction (cognitive 27) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.tsx:393— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.clientAction has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 2 (9 pts), boolean chains 5, error handling 1 (nesting depth added 14). 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, 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.
graph-ql-explorer.GraphQLExplorer (cognitive 27) packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer.tsx:74— graph-ql-explorer.GraphQLExplorer has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12, ternaries 7 (8 pts), boolean chains 7 (nesting depth added 1). 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, 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.
git-repo-form.GitRepoForm (cognitive 27) packages/insomnia/src/ui/components/project/git-repo-form.tsx:75— git-repo-form.GitRepoForm has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 27. 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.
RepoFileWatcher.flushWorkspacesToDisk (cognitive 26) packages/insomnia/src/sync/git/repo-file-watcher.ts:472— RepoFileWatcher.flushWorkspacesToDisk has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2, error handling 1 (2 pts), loops 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
socket-io.openSocketIOConnection (cognitive 26) packages/insomnia/src/main/network/socket-io.ts:260— socket-io.openSocketIOConnection has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, if/else 10, ternaries 2, error handling 1. Of this number, 20 points are the body's own statements and 6 belong to 5 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.sendActionImplementation (cognitive 26) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.tsx:116— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.send.sendActionImplementation has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 12, if/else 9, ternaries 4 (5 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
import-modal.ImportResourcesForm (cognitive 26) packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:638— import-modal.ImportResourcesForm has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 16, if/else 5 (6 pts), ternaries 3, loops 1 (nesting depth added 1). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 670, a function literal at line 678, a function literal at line 695, …). 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.
workspace-settings-modal.WorkspaceSettingsModal (cognitive 26) packages/insomnia/src/ui/components/modals/workspace-settings-modal.tsx:37— workspace-settings-modal.WorkspaceSettingsModal has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 20, if/else 6. Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 128, 49, 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.
request-pane.RequestPane (cognitive 26) packages/insomnia/src/ui/components/panes/request-pane.tsx:44— request-pane.RequestPane has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 19, ternaries 4, if/else 2, error handling 1. Of this number, 21 points are the body's own statements and 5 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.
workspace-pane-header.WorkspacePaneHeader (cognitive 26) packages/insomnia/src/ui/components/workspace/workspace-pane-header.tsx:21— workspace-pane-header.WorkspacePaneHeader has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 11, ternaries 6 (9 pts), if/else 4 (6 pts) (nesting depth added 5). Of this number, 19 points are the body's own statements and 7 belong to 4 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.
Url.initFields (cognitive 25) packages/insomnia-scripting-environment/src/objects/urls.ts:186— Url.initFields has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 7 (9 pts), boolean chains 4 (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.
insomnia.initInsomniaObject (cognitive 25) packages/insomnia-scripting-environment/src/objects/insomnia.ts:144— insomnia.initInsomniaObject has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 16, ternaries 7, if/else 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.
git-service.importLegacyInsomniaFolder (cognitive 25) packages/insomnia/src/main/git-service.ts:1160— git-service.importLegacyInsomniaFolder has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 3 (5 pts), boolean chains 1, error handling 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.
git-service.pushToGitRemoteAction (cognitive 25) packages/insomnia/src/main/git-service.ts:2920— git-service.pushToGitRemoteAction has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 8, error handling 2, ternaries 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.
sync.syncKonnect (cognitive 25) packages/insomnia/src/konnect/sync.ts:692— sync.syncKonnect has cognitive complexity 25 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 4 (7 pts), ternaries 2 (5 pts), error handling 2 (3 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.
auth-dropdown.castOneAuthTypeToAnother (cognitive 25) packages/insomnia/src/ui/components/dropdowns/auth-dropdown.tsx:27— auth-dropdown.castOneAuthTypeToAnother has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 16, if/else 9. 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.
auth-input-row.AuthInputRow (cognitive 25) packages/insomnia/src/ui/components/editors/auth/components/auth-input-row.tsx:30— auth-input-row.AuthInputRow has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 7, if/else 6 (7 pts) (nesting depth added 5). Of this number, 17 points are the body's own statements and 8 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.
request-result-card.RequestResultCard (cognitive 25) packages/insomnia/src/ui/components/panes/request-result-card.tsx:25— request-result-card.RequestResultCard has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 13, ternaries 8 (11 pts), if/else 1 (nesting depth added 3). 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.
cloud-service-credentials.CloudServiceCredentialList (cognitive 25) packages/insomnia/src/ui/components/settings/cloud-service-credentials.tsx:53— cloud-service-credentials.CloudServiceCredentialList has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 6). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 177, handleCreateCloudServiceCredential, a function literal at line 77). 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.
request-node.RequestNode (cognitive 25) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/request-node.tsx:134— request-node.RequestNode has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 13, ternaries 8 (10 pts), if/else 2 (nesting depth added 2). Of this number, 21 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.
websocket-request-pane.WebSocketRequestPane (cognitive 25) packages/insomnia/src/ui/components/websockets/websocket-request-pane.tsx:187— websocket-request-pane.WebSocketRequestPane has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 16, ternaries 6, if/else 2, error handling 1. Of this number, 17 points are the body's own statements and 8 belong to 5 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.
check-cycle-references.main (cognitive 25) scripts/circular-references/check-cycle-references.mjs:124— check-cycle-references.main has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (7 pts), ternaries 3 (6 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
workspace-data.getAllCollectionChildrenAndMetasByWorkspaceIds (cognitive 24) packages/insomnia-data/node-src/services/app-data/workspace-data.ts:26— workspace-data.getAllCollectionChildrenAndMetasByWorkspaceIds has cognitive complexity 24 (threshold 15). Drivers by points: if/else 17 (23 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 105, 135, 126, …). 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.
project.getDefaultProjectStorageType (cognitive 24) packages/insomnia-data/src/models/project.ts:147— project.getDefaultProjectStorageType has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (24 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.findDuplicatePluginNames::walk (cognitive 24) packages/insomnia/src/plugins/index.ts:129— index.findDuplicatePluginNames::walk has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 1 (3 pts), loops 2 (3 pts), 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.
stream-summary.extractCompleteTopLevelArrayElements (cognitive 24) packages/insomnia/src/common/stream-summary.ts:111— stream-summary.extractCompleteTopLevelArrayElements has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 4, 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.
sync.syncServiceWorkspace (cognitive 24) packages/insomnia/src/konnect/sync.ts:424— sync.syncServiceWorkspace has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 2 (6 pts), boolean chains 2, loops 1 (nesting depth added 9). Of this number, 22 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.
export-requests-modal.ExportRequestsModal (cognitive 24) packages/insomnia/src/ui/components/modals/export-requests-modal.tsx:192— export-requests-modal.ExportRequestsModal has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 9 (10 pts), loops 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 11 function items inside it that branch (setItemSelected, getSelectedRequestIds, a function literal at line 205, …). 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.
cloud-credential-modal.CloudCredentialModal (cognitive 24) packages/insomnia/src/ui/components/modals/cloud-credential-modal/cloud-credential-modal.tsx:27— cloud-credential-modal.CloudCredentialModal has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 6 (7 pts), ternaries 3, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (exchangeAzureCode, a function literal at line 122, a function literal at line 97, …). 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.
proto-files-modal.ProtoFilesModal (cognitive 24) packages/insomnia/src/ui/components/modals/proto-files-modal.tsx:170— proto-files-modal.ProtoFilesModal has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (13 pts), loops 4 (6 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 4). None of this is in the body itself: all 24 points belong to 6 function items inside it that branch (handleAddDirectory, a function literal at line 187, handleUpdate, …). 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.
swagger-2.prepareBody (cognitive 23) packages/insomnia/src/main/importers/importers/swagger-2.ts:314— swagger-2.prepareBody has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 9 (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.
render.getRenderContext (cognitive 23) packages/insomnia/src/common/render.ts:715— render.getRenderContext has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 5 (7 pts), boolean chains 4 (nesting depth added 8). 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
significant-diff-detection.cleanObject (cognitive 23) packages/insomnia/src/common/significant-diff-detection.ts:54— significant-diff-detection.cleanObject has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
organization.$organizationId.project.$projectId.delete.clientAction (cognitive 23) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.delete.tsx:14— organization.$organizationId.project.$projectId.delete.clientAction has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 4 (9 pts), boolean chains 2, error handling 1 (nesting depth added 9). 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
git-staging-modal.GitStagingModal (cognitive 23) packages/insomnia/src/ui/components/modals/git-staging-modal.tsx:30— git-staging-modal.GitStagingModal has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, ternaries 9, if/else 2. Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 138, a function literal at line 84, a function literal at line 113, …). 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.
body-editor.BodyEditor (cognitive 23) packages/insomnia/src/ui/components/editors/body/body-editor.tsx:47— body-editor.BodyEditor has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 10, if/else 9 (10 pts), ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (renderBodyEditor, handleFileChange, a function literal at line 51, …). 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.
request-headers-editor.RequestHeadersEditor (cognitive 23) packages/insomnia/src/ui/components/editors/request-headers-editor.tsx:36— request-headers-editor.RequestHeadersEditor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 7, ternaries 5, loops 2 (nesting depth added 3). Of this number, 13 points are the body's own statements and 10 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, 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.
use-insomnia-navigation.buildResourceUrl (cognitive 23) packages/insomnia/src/ui/hooks/use-insomnia-navigation.ts:198— use-insomnia-navigation.buildResourceUrl has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 10, match/switch 1 (nesting depth added 6). 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.
edn.tokenize (cognitive 23) packages/insomnia/src/ui/utils/prettify/edn.ts:17— edn.tokenize has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2, 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.
search.fuzzyMatchAll (cognitive 22) packages/insomnia-data/common-src/search.ts:19— search.fuzzyMatchAll has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 8). Of this number, 21 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.
VCS._merge (cognitive 22) packages/insomnia-vcs/src/vcs.ts:730— VCS._merge has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 7, ternaries 5 (7 pts), if/else 5 (6 pts), error handling 1 (2 pts) (nesting depth added 4). Of this number, 20 points are the body's own statements and 2 belong 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, 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.
sorting.httpMethodSort (cognitive 22) packages/insomnia/src/common/sorting.ts:44— sorting.httpMethodSort has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (9 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.
templating-worker-database.readPluginModuleMap (cognitive 22) packages/insomnia/src/main/templating-worker-database.ts:228— templating-worker-database.readPluginModuleMap has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, ternaries 1 (2 pts), error handling 1, loops 1 (nesting depth added 6). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (walk, addModule). 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.
insomnia-v5-change-report.collectEntities (cognitive 22) packages/insomnia/src/common/insomnia-v5-change-report.ts:151— insomnia-v5-change-report.collectEntities has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 3 (5 pts), loops 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (walkValue, walkEntity). 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.
insomnia-v5-change-report.formatChangeReportAsText (cognitive 22) packages/insomnia/src/common/insomnia-v5-change-report.ts:434— insomnia-v5-change-report.formatChangeReportAsText has cognitive complexity 22 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 6, ternaries 1 (4 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.
vault-key-panel.VaultKeyPanel (cognitive 22) packages/insomnia/src/ui/components/settings/vault-key-panel.tsx:75— vault-key-panel.VaultKeyPanel has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 10 (nesting depth added 2). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 108, a function literal at line 143, a function literal at line 101, …). 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.
RepoFileWatcher.registerDbChangeListener (cognitive 22) packages/insomnia/src/sync/git/repo-file-watcher.ts:382— RepoFileWatcher.registerDbChangeListener has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 3 (5 pts) (nesting depth added 9). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 383). 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.clientLoader (cognitive 22) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.tsx:85— organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.$requestId.clientLoader has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 5 (8 pts), boolean chains 3 (nesting depth added 5). Of this number, 20 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.
organization.$organizationId.project.new.createProjectImpl (cognitive 22) packages/insomnia/src/routes/organization.$organizationId.project.new.tsx:62— organization.$organizationId.project.new.createProjectImpl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 3, error handling 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.
organization.NetworkAndSyncIndicator (cognitive 22) packages/insomnia/src/routes/organization.tsx:48— organization.NetworkAndSyncIndicator has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (17 pts), boolean chains 3, if/else 1 (2 pts) (nesting depth added 9). Of this number, 19 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.
grpc-request-pane.GrpcRequestPane::handleRequestSend (cognitive 22) packages/insomnia/src/ui/components/panes/grpc-request-pane.tsx:147— grpc-request-pane.GrpcRequestPane::handleRequestSend has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 3 (5 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
auth.fromPreRequestAuth (cognitive 21) packages/insomnia-scripting-environment/src/objects/auth.ts:353— auth.fromPreRequestAuth has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 3 (5 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 7). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (findValueInOauth2Options, findValueInKvArray, a function literal at line 428, …). 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.
parse-header-strings.parseHeaderStrings (cognitive 21) packages/insomnia/src/network/parse-header-strings.ts:33— parse-header-strings.parseHeaderStrings has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 4). Of this number, 18 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.
import.extractErrorMessages (cognitive 21) packages/insomnia/src/common/import.ts:305— import.extractErrorMessages has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 6 (9 pts), loops 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (walkError, a function literal at line 319). 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.
prompt-modal.PromptModal (cognitive 21) packages/insomnia/src/ui/components/modals/prompt-modal.tsx:46— prompt-modal.PromptModal has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (10 pts), if/else 5 (6 pts), boolean chains 5 (nesting depth added 4). Of this number, 11 points are the body's own statements and 10 belong to 3 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.
git-service.commitAndPushToGitRepoAction (cognitive 21) packages/insomnia/src/main/git-service.ts:2449— git-service.commitAndPushToGitRepoAction has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 4, ternaries 2 (4 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.
import.resources.clientAction (cognitive 21) packages/insomnia/src/routes/import.resources.tsx:52— import.resources.clientAction has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, ternaries 1 (3 pts), loops 1 (2 pts), error handling 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.
git-project-branches-modal.GitProjectBranchesModal (cognitive 21) packages/insomnia/src/ui/components/modals/git-project-branches-modal.tsx:260— git-project-branches-modal.GitProjectBranchesModal has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 12, ternaries 7, if/else 2. Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 323, 279, 293, …). 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.
entity-splice.applyChange (cognitive 21) packages/insomnia/src/ui/components/modals/visual-diff/entity-splice.ts:314— entity-splice.applyChange has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 pts), ternaries 1 (3 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
git-branches-modal.LocalBranchItem (cognitive 21) packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:29— git-branches-modal.LocalBranchItem has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 6, ternaries 4 (5 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 151, 45, 76, …). 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.
git-branches-modal.GitBranchesModal (cognitive 21) packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:301— git-branches-modal.GitBranchesModal has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 12, ternaries 7, if/else 2. Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 366, 321, 336, …). 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.
aws-credential-form.AWSCredentialForm (cognitive 21) packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:34— aws-credential-form.AWSCredentialForm has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 13, if/else 5, ternaries 3. Of this number, 13 points are the body's own statements and 8 belong to 2 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.
import-projects-modal.FileField (cognitive 21) packages/insomnia/src/ui/components/modals/import-modal/import-projects-modal.tsx:95— import-projects-modal.FileField has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (4 pts), ternaries 1 (nesting depth added 10). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 133, 106, 124, …). 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.
credentials.GitEditProviderOAuthForm (cognitive 21) packages/insomnia/src/ui/components/settings/credentials.tsx:57— credentials.GitEditProviderOAuthForm has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 19, if/else 1, ternaries 1. Of this number, 13 points are the body's own statements and 8 belong to 4 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.
use-insomnia-navigation.getRouteIdForResource (cognitive 21) packages/insomnia/src/ui/hooks/use-insomnia-navigation.ts:174— use-insomnia-navigation.getRouteIdForResource has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17 (21 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.
multipart.buildMultipart (cognitive 20) packages/insomnia/src/main/network/multipart.ts:16— multipart.buildMultipart has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 7, error handling 2 (4 pts), loops 1 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 17, 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.
collection.flattenCollectionChildren (cognitive 20) packages/insomnia/src/common/collection.ts:9— collection.flattenCollectionChildren has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (7 pts), loops 4 (6 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.
project.getAllLocalFiles (cognitive 20) packages/insomnia/src/common/project.ts:156— project.getAllLocalFiles has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 8, error handling 1 (2 pts), if/else 1 (nesting depth added 3). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 182). 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.
find-unknown-field-ranges.findUnknownFieldRanges (cognitive 20) packages/insomnia/src/common/zod/find-unknown-field-ranges.ts:14— find-unknown-field-ranges.findUnknownFieldRanges has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sync.syncGrpcRoute (cognitive 20) packages/insomnia/src/konnect/sync.ts:144— sync.syncGrpcRoute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 10). 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.
organization.$organizationId.project.$projectId.list-workspaces.getAllLocalFiles (cognitive 20) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.list-workspaces.tsx:16— organization.$organizationId.project.$projectId.list-workspaces.getAllLocalFiles has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 8, error handling 1 (2 pts), if/else 1 (nesting depth added 3). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 42). 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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.mock-route.$mockRouteId.MockRouteRoute (cognitive 20) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.mock-route.$mockRouteId.tsx:148— organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.mock-route.$mockRouteId.MockRouteRoute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, ternaries 4 (5 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch (upsertBinOnRemoteFromResponse, upsertMockbinHar, a function literal at line 305). 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.
organization.$organizationId.project.$projectId.workspace.update.clientAction (cognitive 20) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.update.tsx:19— organization.$organizationId.project.$projectId.workspace.update.clientAction has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 8 (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.
organization.Component (cognitive 20) packages/insomnia/src/routes/organization.tsx:173— organization.Component has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, ternaries 5, if/else 3. Of this number, 13 points are the body's own statements and 7 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.
preview-mode-dropdown.PreviewModeDropdown (cognitive 20) packages/insomnia/src/ui/components/dropdowns/preview-mode-dropdown.tsx:22— preview-mode-dropdown.PreviewModeDropdown has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 6, if/else 4, error handling 2 (nesting depth added 2). 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 70, 30, 122). 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.
mock-route-modal.MockRouteModal (cognitive 20) packages/insomnia/src/ui/components/modals/mock-route-modal.tsx:42— mock-route-modal.MockRouteModal has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 3 (5 pts), error handling 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (handleSubmit, a function literal at line 135, a function literal at line 146, …). 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.
git-repository-select.GitRepositorySelect (cognitive 20) packages/insomnia/src/ui/components/git-credentials/git-repository-select.tsx:10— git-repository-select.GitRepositorySelect has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 13, if/else 5, ternaries 2. Of this number, 10 points are the body's own statements and 10 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.
invite-modal.InviteModal (cognitive 20) packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx:78— invite-modal.InviteModal has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 15, if/else 3, ternaries 2. Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 161, 113, 119, …). 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.
request-pane.SocketIORequestPane (cognitive 20) packages/insomnia/src/ui/components/socket-io/request-pane.tsx:58— request-pane.SocketIORequestPane has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 15, ternaries 3, error handling 1, if/else 1. Of this number, 15 points are the body's own statements and 5 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.
router.getInitialEntry (cognitive 20) packages/insomnia/src/ui/utils/router.ts:88— router.getInitialEntry has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, error handling 2 (3 pts), ternaries 1 (2 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.
isPrivateOrLoopbackHost (cognitive 20) packages/insomnia/src/main/lint-process.mjs:17— isPrivateOrLoopbackHost has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, ternaries 3 (5 pts), if/else 3 (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.
url-matches-cert-host.urlMatchesCertHost (cognitive 19) packages/insomnia-data/common-src/url-matches-cert-host.ts:6— url-matches-cert-host.urlMatchesCertHost has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, error handling 2 (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.
generate-autocomplete.walk (cognitive 19) REDACTED:31— generate-autocomplete.walk has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), boolean chains 3 (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.
get-token.getToken (cognitive 19) packages/insomnia/src/main/network/o-auth-1/get-token.ts:43— get-token.getToken has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 8, loops 1 (2 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
significant-diff-detection.findMetaLineIntervals::walk (cognitive 19) packages/insomnia/src/common/significant-diff-detection.ts:318— significant-diff-detection.findMetaLineIntervals::walk has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
git-service.loadGitRepository (cognitive 19) packages/insomnia/src/main/git-service.ts:772— git-service.loadGitRepository has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
git-service.diffFileLoader (cognitive 19) packages/insomnia/src/main/git-service.ts:3518— git-service.diffFileLoader has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 6, error handling 2 (3 pts), if/else 2 (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.
git-service.runAllGitRepoMigrations (cognitive 19) packages/insomnia/src/main/git-service.ts:3941— git-service.runAllGitRepoMigrations has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 3 (5 pts), boolean chains 3, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 4004, 3969). 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.
GitLabProvider.renewCredential (cognitive 19) packages/insomnia/src/sync/git/providers/gitlab.ts:493— GitLabProvider.renewCredential has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 2 (3 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.
session.migrateFromLocalStorage (cognitive 19) packages/insomnia/src/ui/account/session.ts:148— session.migrateFromLocalStorage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (3 pts), loops 1 (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.
git-project-branches-modal.LocalBranchItem (cognitive 19) packages/insomnia/src/ui/components/modals/git-project-branches-modal.tsx:29— git-project-branches-modal.LocalBranchItem has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 5, ternaries 4 (5 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 131, 45, 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.
hashicorp-credential-form.HashiCorpCredentialForm (cognitive 19) packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:36— hashicorp-credential-form.HashiCorpCredentialForm has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, if/else 2, ternaries 2, error handling 1. Of this number, 12 points are the body's own statements and 7 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.
import-projects-modal.selectDir (cognitive 19) packages/insomnia/src/ui/components/modals/import-modal/import-projects-modal.tsx:35— import-projects-modal.selectDir has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 60, 52). 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.
response-pane-utils.downloadResponseBody (cognitive 19) packages/insomnia/src/ui/components/panes/response-pane-utils.ts:6— response-pane-utils.downloadResponseBody has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, 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.
runner-result-history-pane.RunnerResultHistoryPane (cognitive 19) packages/insomnia/src/ui/components/panes/runner-result-history-pane.tsx:28— runner-result-history-pane.RunnerResultHistoryPane has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 3 (6 pts), ternaries 1 (nesting depth added 12). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 34). 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.
use-sidebar-drag-and-drop.normalizeBoundaryTarget (cognitive 19) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:132— use-sidebar-drag-and-drop.normalizeBoundaryTarget has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4 (8 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
body-tab-pane.SocketIOBodyTabPane (cognitive 19) packages/insomnia/src/ui/components/socket-io/body-tab-pane.tsx:50— body-tab-pane.SocketIOBodyTabPane has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 5, error handling 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 72, a function literal at line 113, handleChange, …). 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.
action-bar.WebSocketActionBar (cognitive 19) packages/insomnia/src/ui/components/websockets/action-bar.tsx:31— action-bar.WebSocketActionBar has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 101, a function literal at line 61, a function literal at line 135, …). 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.
event-log-view.getMessage (cognitive 19) packages/insomnia/src/ui/components/websockets/event-log-view.tsx:87— event-log-view.getMessage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 7, match/switch 1 (nesting depth added 6). 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.
render.buildEnvironmentRenderLayers (cognitive 18) packages/insomnia/src/common/render.ts:129— render.buildEnvironmentRenderLayers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 3 (6 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stream-summary.candidateJsonPayloadsFromSseText (cognitive 18) packages/insomnia/src/common/stream-summary.ts:51— stream-summary.candidateJsonPayloadsFromSseText has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
git-repo-migration.flushWorkspacesToDisk (cognitive 18) packages/insomnia/src/sync/git/git-repo-migration.ts:291— git-repo-migration.flushWorkspacesToDisk has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (5 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 6). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 302). 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.
entry.main._launchApp (cognitive 18) packages/insomnia/src/entry.main.ts:258— entry.main._launchApp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2 (nesting depth added 8). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 282, 262, 317, …). 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.
sync.syncWsRoute (cognitive 18) packages/insomnia/src/konnect/sync.ts:216— sync.syncWsRoute has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 9). 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.
private-host.isPrivateOrLoopbackHost (cognitive 18) packages/insomnia/src/main/private-host.ts:10— private-host.isPrivateOrLoopbackHost has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 3 (5 pts), if/else 3 (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.
organization.$organizationId.project.$projectId.workspace.$workspaceId.clientLoader (cognitive 18) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.tsx:87— organization.$organizationId.project.$projectId.workspace.$workspaceId.clientLoader has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, error handling 1 (2 pts), ternaries 2 (nesting depth added 3). Of this number, 14 points are the body's own statements and 4 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.
entity-splice.locateEntity (cognitive 18) packages/insomnia/src/ui/components/modals/visual-diff/entity-splice.ts:124— entity-splice.locateEntity has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, ternaries 1 (2 pts) (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.
generate-code-modal.GenerateCodeModal (cognitive 18) packages/insomnia/src/ui/components/modals/generate-code-modal.tsx:45— generate-code-modal.GenerateCodeModal has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, if/else 4, error handling 2, ternaries 2. Of this number, 10 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.
sidebar-project-dropdown.ProjectDropdown (cognitive 18) packages/insomnia/src/ui/components/dropdowns/sidebar-project-dropdown.tsx:66— sidebar-project-dropdown.ProjectDropdown has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 14, ternaries 2 (3 pts), if/else 1 (nesting depth added 1). Of this number, 9 points are the body's own statements and 9 belong to 5 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.
event-tab-pane.SocketIOEventTabPane (cognitive 18) packages/insomnia/src/ui/components/socket-io/event-tab-pane.tsx:57— event-tab-pane.SocketIOEventTabPane has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 18 points belong to 6 function items inside it that branch (handleChange, a function literal at line 75, handleDeleteEvent, …). 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.
use-workspace-breadcrumb.useWorkspaceBreadcrumbs (cognitive 18) packages/insomnia/src/ui/components/workspace/use-workspace-breadcrumb.tsx:13— use-workspace-breadcrumb.useWorkspaceBreadcrumbs has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 3 (4 pts) (nesting depth added 1). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 46, 37). 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.
router.getInitialRouteForOrganization (cognitive 18) packages/insomnia/src/ui/utils/router.ts:36— router.getInitialRouteForOrganization has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 2 (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.
PropertyBase.findInParents (cognitive 17) packages/insomnia-scripting-environment/src/objects/properties.ts:76— PropertyBase.findInParents has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 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.
UrlMatchPattern.testPort (cognitive 17) packages/insomnia-scripting-environment/src/objects/urls.ts:547— UrlMatchPattern.testPort has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (6 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Cookie.parse (cognitive 17) packages/insomnia-scripting-environment/src/objects/cookies.ts:72— Cookie.parse has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts) (nesting depth added 1). Of this number, 12 points are the body's own statements and 5 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.
graceful-rename.renameWithRetry (cognitive 17) packages/insomnia-vcs/src/store/drivers/graceful-rename.ts:16— graceful-rename.renameWithRetry has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 2 (4 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.
mask-or-decrypt-vault-data.maskOrDecryptVaultDataIfNecessary (cognitive 17) packages/insomnia/src/common/templating/mask-or-decrypt-vault-data.ts:15— mask-or-decrypt-vault-data.maskOrDecryptVaultDataIfNecessary has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitVCS.pullWithConflictSupport (cognitive 17) packages/insomnia/src/sync/git/git-vcs.ts:1288— GitVCS.pullWithConflictSupport has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 2 (4 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.
git-service.pullFromGitRemote (cognitive 17) packages/insomnia/src/main/git-service.ts:3086— git-service.pullFromGitRemote has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, ternaries 2, 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.
mcp.performConnection (cognitive 17) packages/insomnia/src/main/network/mcp.ts:297— mcp.performConnection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (4 pts), error handling 2, boolean chains 1 (nesting depth added 4). Of this number, 12 points are the body's own statements and 5 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.
diff.diff (cognitive 17) packages/insomnia/src/sync/delta/diff.ts:22— diff.diff has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
git-oauth-auth-banner.GitOauthAuthBanner (cognitive 17) packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx:37— git-oauth-auth-banner.GitOauthAuthBanner has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (6 pts), error handling 1 (2 pts) (nesting depth added 2). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 123, 111, 47, …). 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.
input-vault-key-modal.InputVaultKeyModal (cognitive 17) packages/insomnia/src/ui/components/modals/input-vault-key-modal.tsx:18— input-vault-key-modal.InputVaultKeyModal has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 4, ternaries 2. Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 84, 29, 38, …). 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.
konnect-sync-bar.KonnectSyncResultPanel (cognitive 17) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/konnect-sync-bar.tsx:289— konnect-sync-bar.KonnectSyncResultPanel has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 17. 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.
SidebarDropTargetDelegate.classify (cognitive 17) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:446— SidebarDropTargetDelegate.classify has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). Of this number, 16 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.
tab.InsomniaTab (cognitive 17) packages/insomnia/src/ui/components/tabs/tab.tsx:81— tab.InsomniaTab has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 5, ternaries 3. None of this is in the body itself: all 17 points belong to 5 function items inside it that branch (renderTabIcon, a function literal at line 177, a function literal at line 154, …). 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.
querystring.deconstructQueryStringToParams (cognitive 16) packages/insomnia-data/common-src/querystring.ts:29— querystring.deconstructQueryStringToParams has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, error handling 2 (4 pts), if/else 2 (3 pts), 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.
request.mergeRequestBody (cognitive 16) packages/insomnia-scripting-environment/src/objects/request.ts:620— request.mergeRequestBody has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 2, match/switch 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 5). Of this number, 12 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.
util.preMergeCheck (cognitive 16) packages/insomnia-vcs/src/util.ts:416— util.preMergeCheck has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, 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.
curl.convert (cognitive 16) packages/insomnia/src/main/importers/importers/curl.ts:468— curl.convert has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 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.
insomnia-1.importRequestItem (cognitive 16) packages/insomnia/src/main/importers/importers/insomnia-1.ts:65— insomnia-1.importRequestItem has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (6 pts), boolean chains 5, if/else 4 (5 pts) (nesting depth added 4). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 66, 99). 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.
insomnia-v5.getEnvironments (cognitive 16) packages/insomnia/src/common/insomnia-v5.ts:443— insomnia-v5.getEnvironments has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 15, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
significant-diff-detection.findSystemChangeLines (cognitive 16) packages/insomnia/src/common/significant-diff-detection.ts:192— significant-diff-detection.findSystemChangeLines has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 4, loops 2, match/switch 1 (2 pts), error handling 1 (nesting depth added 3). 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.
add-key-combination-modal.AddKeyCombinationModal::handleKeyDown (cognitive 16) packages/insomnia/src/ui/components/modals/add-key-combination-modal.tsx:43— add-key-combination-modal.AddKeyCombinationModal::handleKeyDown has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 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.
git-repo-migration.moveDirectoryContents (cognitive 16) packages/insomnia/src/sync/git/git-repo-migration.ts:82— git-repo-migration.moveDirectoryContents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 4 (6 pts), boolean chains 1 (nesting depth added 5). 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 literal inside it that branches (line 91). 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.
migrations.migrateGitLabConnectedRepositories (cognitive 16) packages/insomnia/src/main/git/migrations.ts:109— migrations.migrateGitLabConnectedRepositories has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (4 pts), boolean chains 3 (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.
GitHubProvider.completeOAuth (cognitive 16) packages/insomnia/src/sync/git/providers/github.ts:293— GitHubProvider.completeOAuth has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 5, if/else 2, error handling 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.
GitLabProvider.completeOAuth (cognitive 16) packages/insomnia/src/sync/git/providers/gitlab.ts:381— GitLabProvider.completeOAuth has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 4, if/else 3, error handling 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.
content-type-dropdown.ContentTypeDropdown::handleChangeMimeType (cognitive 16) packages/insomnia/src/ui/components/dropdowns/content-type-dropdown.tsx:48— content-type-dropdown.ContentTypeDropdown::handleChangeMimeType has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 13, if/else 3. 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.
request-actions-dropdown.RequestActionsDropdown (cognitive 16) packages/insomnia/src/ui/components/dropdowns/request-actions-dropdown.tsx:49— request-actions-dropdown.RequestActionsDropdown has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5, ternaries 4 (5 pts), boolean chains 3, error handling 3 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 8 function items inside it that branch (copyAsCurl, a function literal at line 91, a function literal at line 101, …). 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.
import-modal.ScanResourcesForm (cognitive 16) packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:463— import-modal.ScanResourcesForm has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 15, if/else 1. Of this number, 13 points are the body's own statements and 3 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.
encryption.startInvite (cognitive 16) packages/insomnia/src/ui/components/modals/invite-modal/encryption.ts:114— encryption.startInvite has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (5 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.
mcp-pane.CollectionGridListItem (cognitive 16) packages/insomnia/src/ui/components/mcp/mcp-pane.tsx:551— mcp-pane.CollectionGridListItem has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 12, ternaries 4. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
response-multipart-viewer.ResponseMultipartViewer (cognitive 16) packages/insomnia/src/ui/components/viewers/response-multipart-viewer.tsx:30— response-multipart-viewer.ResponseMultipartViewer has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 6, error handling 2, ternaries 1. Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 76, 47, 62, …). 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.
upload-runner-data-modal.UploadDataModal::parseFileContent (cognitive 16) packages/insomnia/src/ui/components/modals/upload-runner-data-modal.tsx:72— upload-runner-data-modal.UploadDataModal::parseFileContent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
konnect-sync-bar.useKonnectSyncBar.syncKonnectProjectsAndNotify (cognitive 16) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/konnect-sync-bar.tsx:89— konnect-sync-bar.useKonnectSyncBar.syncKonnectProjectsAndNotify has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 8). Of this number, 12 points are the body's own statements and 4 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.
use-toggle-environment-type.useToggleEnvironmentType.toggleEnvironmentType (cognitive 16) packages/insomnia/src/ui/hooks/use-toggle-environment-type.tsx:12— use-toggle-environment-type.useToggleEnvironmentType.toggleEnvironmentType has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (6 pts), ternaries 2 (nesting depth added 1). Of this number, 14 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.
Cross-context type PersonalPlanType (insomnia-api → insomnia-data) packages/insomnia-data/src/models/organization.ts:33— PersonalPlanType (context insomnia-api) is exposed in insomnia-data's public surface via organization.formatCurrentPlanType — couples the contexts.
Cross-context type InsoEvent (insomnia-analytics → insomnia-inso) packages/insomnia-inso/src/analytics.ts:59— InsoEvent (context insomnia-analytics) is exposed in insomnia-inso's public surface via analytics.trackInsoEvent — couples the contexts.
Cross-context type Compression (insomnia-data → insomnia) packages/insomnia/src/entry.hidden-window-preload.ts:23— Compression (context insomnia-data) is exposed in insomnia's public surface via HiddenBrowserWindowToMainBridgeAPI.readCurlResponse — couples the contexts.
Cross-context type GitRepoCredentials (insomnia-data → insomnia) packages/insomnia/src/sync/git/get-oauth2-format-name.ts:3— GitRepoCredentials (context insomnia-data) is exposed in insomnia's public surface via get-oauth2-format-name.getOauth2FormatName — couples the contexts.
Cross-context type McpServerPrimitiveTypes (insomnia-data → insomnia) packages/insomnia/src/ui/components/mcp/types.ts:26— McpServerPrimitiveTypes (context insomnia-data) is exposed in insomnia's public surface via PrimitiveTypeItem.type — couples the contexts.
Cross-context type EnvironmentType (insomnia-data → insomnia) packages/insomnia/src/ui/hooks/use-toggle-environment-type.tsx:12— EnvironmentType (context insomnia-data) is exposed in insomnia's public surface via use-toggle-environment-type.useToggleEnvironmentType.toggleEnvironmentType — couples the contexts.
Cross-context type WorkspaceChildren (insomnia-data → insomnia) packages/insomnia/src/ui/hooks/use-workspace-data.ts:11— WorkspaceChildren (context insomnia-data) is exposed in insomnia's public surface via use-workspace-data.useWorkspaceData — couples the contexts.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Change-coupling hub: organization.$organizationId.project.$projectId._index.tsx → sidebar-project-dropdown.tsx, workspace-sync-dropdown.tsx, workspace-duplicate-modal.tsx packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx— `packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx` changes together with 3 other files — `packages/insomnia/src/ui/components/dropdowns/sidebar-project-dropdown.tsx`, `packages/insomnia/src/ui/components/dropdowns/workspace-sync-dropdown.tsx`, `packages/insomnia/src/ui/components/modals/workspace-duplicate-modal.tsx` — 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.
Low cohesion: GitHubProvider (LCOM4 4) packages/insomnia/src/sync/git/providers/github.ts:76— GitHubProvider'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.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 1007 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P12 · CI test-gate honesty· Workspace package's tests never run by CI · ×1
Workspace package's tests never run by CI packages/insomnia-smoke-test/package.json:51— `packages/insomnia-smoke-test` is a workspace package with 246 test(s) in 81 file(s) (e.g. `packages/insomnia-smoke-test/tests/critical/backup.test.ts`, `packages/insomnia-smoke-test/tests/critical/bundling.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Duplication concentrated across 16 sibling directories (71 clone groups) packages/insomnia/src/ui/components/socket-io/request-pane.tsx:196— 71 duplicated blocks under packages/insomnia/src/ui/components/ have copies in at least two of the sibling directories dropdowns, editors, git, git-credentials, graph-ql-explorer, key-value-editor (+10 more sibling(s) not listed) — 55 of them are reported below, and 16 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 71 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 71 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 71 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 9 sibling directories (45 clone groups) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:64— 45 duplicated blocks under packages/insomnia/src/ have copies in at least two of the sibling directories common, main, network, plugins, routes, runtimes (+3 more sibling(s) not listed) — 36 of them are reported below, and 9 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 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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 6 sibling directories (11 clone groups) packages/insomnia-inso/src/commands/lint-specification.ts:23— 11 duplicated blocks under packages/ have copies in at least two of the sibling directories insomnia, insomnia-data, insomnia-inso, insomnia-scripting-environment, insomnia-testing, insomnia-vcs — 7 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 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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.
R10 · Code Duplication· Duplicated block with local edits (351 matched lines × 2 locations) · ×1
Duplicated block with local edits (351 matched lines × 2 locations) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:64— packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.environment.tsx:64 · packages/insomnia/src/ui/components/modals/workspace-environments-edit-modal.tsx:68 — the two spans are one implementation copied and then locally edited — 1828 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.
Wholesale file copy (277 identical lines × 2 files) packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:1— packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:1 · packages/insomnia/src/ui/components/modals/git-project-branches-modal.tsx:1 — these 2 files are line-for-line copies of one another — 277 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 (195 matched lines × 2 locations) · ×1
Duplicated block with local edits (195 matched lines × 2 locations) packages/insomnia/src/sync/git/providers/github.ts:92— packages/insomnia/src/sync/git/providers/github.ts:92 · packages/insomnia/src/sync/git/providers/gitlab.ts:156 — the two spans are one implementation copied and then locally edited — 1124 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 (147 matched lines × 2 locations) · ×1
Duplicated block with local edits (147 matched lines × 2 locations) packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:532— packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:532 · packages/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:255 — the two spans are one implementation copied and then locally edited — 622 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 (145 lines × 2 locations) packages/insomnia/src/ui/components/settings/llms/gemini.tsx:38— packages/insomnia/src/ui/components/settings/llms/gemini.tsx:38 · packages/insomnia/src/ui/components/settings/llms/openai.tsx:42 — 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.
R10 · Code Duplication· Duplicated block with local edits (145 matched lines × 2 locations) · ×1
Duplicated block with local edits (145 matched lines × 2 locations) packages/insomnia/src/ui/components/settings/llms/gguf.tsx:24— packages/insomnia/src/ui/components/settings/llms/gguf.tsx:24 · packages/insomnia/src/ui/components/settings/llms/url.tsx:38 — the two spans are one implementation copied and then locally edited — 840 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 (139 matched lines × 2 locations) · ×1
Duplicated block with local edits (139 matched lines × 2 locations) packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:57— packages/insomnia/src/ui/components/modals/cloud-credential-modal/aws-credential-form.tsx:57 · packages/insomnia/src/ui/components/modals/cloud-credential-modal/hashicorp-credential-form.tsx:64 — the two spans are one implementation copied and then locally edited — 644 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 (136 matched lines × 2 locations) · ×1
Duplicated block with local edits (136 matched lines × 2 locations) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.tsx:114— packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.mock-server.tsx:114 · packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.test.tsx:123 — the two spans are one implementation copied and then locally edited — 635 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.
Wholesale file copy (114 identical lines × 2 files) packages/insomnia/src/ui/components/settings/llms/claude.tsx:1— packages/insomnia/src/ui/components/settings/llms/claude.tsx:1 · packages/insomnia/src/ui/components/settings/llms/openai.tsx:1 — these 2 files are line-for-line copies of one another — 114 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.
Duplicated block (105 lines × 3 locations) packages/insomnia/src/ui/components/settings/llms/claude.tsx:58— packages/insomnia/src/ui/components/settings/llms/claude.tsx:58 · packages/insomnia/src/ui/components/settings/llms/gemini.tsx:62 · packages/insomnia/src/ui/components/settings/llms/openai.tsx:66 — the 3 copies are spread across 3 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 (97 lines × 2 locations) packages/insomnia/src/ui/components/socket-io/request-pane.tsx:196— packages/insomnia/src/ui/components/socket-io/request-pane.tsx:196 · packages/insomnia/src/ui/components/websockets/websocket-request-pane.tsx:348 — 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 (96 lines × 2 locations) packages/insomnia/src/common/project.ts:156— packages/insomnia/src/common/project.ts:156 · packages/insomnia/src/routes/organization.$organizationId.project.$projectId.list-workspaces.tsx:16 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (94 matched lines × 2 locations) · ×1
Duplicated block with local edits (94 matched lines × 2 locations) packages/insomnia/src/ui/components/modals/request-settings-modal.tsx:137— packages/insomnia/src/ui/components/modals/request-settings-modal.tsx:137 · packages/insomnia/src/ui/components/modals/request-settings-modal.tsx:327 — the two spans are one implementation copied and then locally edited — 429 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 (88 matched lines × 2 locations) · ×1
Duplicated block with local edits (88 matched lines × 2 locations) packages/insomnia/src/ui/components/settings/credentials.tsx:69— packages/insomnia/src/ui/components/settings/credentials.tsx:69 · packages/insomnia/src/ui/components/settings/credentials.tsx:297 — the two spans are one implementation copied and then locally edited — 515 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 (79 matched lines × 2 locations) · ×1
Duplicated block with local edits (79 matched lines × 2 locations) packages/insomnia/src/templating/index.ts:29— packages/insomnia/src/templating/index.ts:29 · packages/insomnia/src/ui/templating/worker.ts:26 — the two spans are one implementation copied and then locally edited — 630 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.
Wholesale file copy (78 identical lines × 2 files) packages/insomnia/src/ui/components/modals/git-log-modal.tsx:1— packages/insomnia/src/ui/components/modals/git-log-modal.tsx:1 · packages/insomnia/src/ui/components/modals/git-project-log-modal.tsx:1 — these 2 files are line-for-line copies of one another — 78 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.
Duplicated block (58 lines × 2 locations) packages/insomnia/src/ui/components/dropdowns/request-actions-dropdown.tsx:293— packages/insomnia/src/ui/components/dropdowns/request-actions-dropdown.tsx:293 · packages/insomnia/src/ui/components/dropdowns/request-group-actions-dropdown.tsx:332 — 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.
R10 · Code Duplication· Duplicated block with local edits (54 matched lines × 2 locations) · ×1
Duplicated block with local edits (54 matched lines × 2 locations) packages/insomnia/src/script-executor.ts:60— packages/insomnia/src/script-executor.ts:60 · packages/insomnia/src/scripting/run-script.ts:80 — the two spans are one implementation copied and then locally edited — 323 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 (54 lines × 3 locations) packages/insomnia/src/ui/components/panes/request-pane.tsx:244— packages/insomnia/src/ui/components/panes/request-pane.tsx:244 · packages/insomnia/src/ui/components/socket-io/request-pane.tsx:240 · packages/insomnia/src/ui/components/websockets/websocket-request-pane.tsx:392 — the 3 copies are spread across 3 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.
Wholesale file copy (53 identical lines × 2 files) packages/insomnia/src/plugins/themes/default.ts:1— packages/insomnia/src/plugins/themes/default.ts:1 · packages/insomnia/src/plugins/themes/legacy.ts:1 — these 2 files are line-for-line copies of one another — 53 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.
Duplicated block (53 lines × 2 locations) packages/insomnia/src/ui/components/project/project-create-form.tsx:431— packages/insomnia/src/ui/components/project/project-create-form.tsx:431 · packages/insomnia/src/ui/components/project/project-settings-form.tsx:745 — 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 (51 lines × 3 locations) packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx:122— packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx:122 · packages/insomnia/src/ui/components/settings/credentials.tsx:229 · packages/insomnia/src/ui/components/settings/credentials.tsx:341 — the 3 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 (51 lines × 2 locations) packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:680— packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:680 · packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:998 — 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 (47 lines × 2 locations) packages/insomnia/src/sync/git/git-vcs.ts:1463— packages/insomnia/src/sync/git/git-vcs.ts:1463 · packages/insomnia/src/sync/git/git-vcs.ts:1687 — 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 (45 matched lines × 2 locations) · ×1
Duplicated block with local edits (45 matched lines × 2 locations) packages/insomnia/src/ui/components/panes/request-test-result-pane.tsx:169— packages/insomnia/src/ui/components/panes/request-test-result-pane.tsx:169 · packages/insomnia/src/ui/components/panes/runner-test-result-pane.tsx:94 — the two spans are one implementation copied and then locally edited — 191 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 (44 lines × 2 locations) packages/insomnia-data/node-src/services/socket-io-request-meta.ts:4— packages/insomnia-data/node-src/services/socket-io-request-meta.ts:4 · packages/insomnia-data/node-src/services/websocket-request-meta.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.
R10 · Code Duplication· Duplicated block with local edits (42 matched lines × 2 locations) · ×1
Duplicated block with local edits (42 matched lines × 2 locations) packages/insomnia/src/routes/ai.generate-commit-messages.tsx:10— packages/insomnia/src/routes/ai.generate-commit-messages.tsx:10 · packages/insomnia/src/routes/ai.mcp-generate-sampling-response.tsx:20 — the two spans are one implementation copied and then locally edited — 201 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 (40 lines × 2 locations) packages/insomnia/src/ui/components/command-palette.tsx:323— packages/insomnia/src/ui/components/command-palette.tsx:323 · packages/insomnia/src/ui/components/command-palette.tsx:422 — 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 (38 lines × 2 locations) packages/insomnia/src/sync/git/git-vcs.ts:490— packages/insomnia/src/sync/git/git-vcs.ts:490 · packages/insomnia/src/sync/git/git-vcs.ts:654 — 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.
Complex function toPreRequestAuth (cyclomatic 87, cognitive 88) packages/insomnia-scripting-environment/src/objects/auth.ts:597— toPreRequestAuth has cyclomatic complexity 87 and cognitive complexity 88; 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 ProjectSettingsForm (cyclomatic 86, cognitive 71) packages/insomnia/src/ui/components/project/project-settings-form.tsx:78— ProjectSettingsForm has cyclomatic complexity 86 and cognitive complexity 71; 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 SpecView (cyclomatic 77, cognitive 70) packages/insomnia/src/ui/components/spec-view.tsx:136— SpecView has cyclomatic complexity 77 and cognitive complexity 70; 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 clientAction (cyclomatic 62, cognitive 128) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.update.tsx:48— clientAction has cyclomatic complexity 62 and cognitive complexity 128; 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.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 57, cognitive 81) · ×1
Complex function run (cyclomatic 57, cognitive 81) packages/insomnia/src/common/templating/local-template-tags.ts:570— run has cyclomatic complexity 57 and cognitive complexity 81; 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 map (cyclomatic 57, cognitive 66) packages/insomnia/src/sync/git/git-vcs.ts:665— map has cyclomatic complexity 57 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 threeWayMerge (cyclomatic 56, cognitive 53) packages/insomnia-vcs/src/util.ts:67— threeWayMerge has cyclomatic complexity 56 and cognitive complexity 53; 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 canDrop (cyclomatic 53, cognitive 75) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:252— canDrop has cyclomatic complexity 53 and cognitive complexity 75; 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 traversePluginPath (cyclomatic 52, cognitive 84) packages/insomnia/src/plugins/index.ts:189— traversePluginPath has cyclomatic complexity 52 and cognitive complexity 84; 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 SyncDropdown (cyclomatic 50, cognitive 45) packages/insomnia/src/ui/components/dropdowns/sync-dropdown.tsx:42— SyncDropdown has cyclomatic complexity 50 and cognitive complexity 45; 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 49, cognitive 73) packages/insomnia/src/root.tsx:458— (anonymous) has cyclomatic complexity 49 and cognitive complexity 73; 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 48, cognitive 58) packages/insomnia/src/common/insomnia-v5.ts:675— (anonymous) has cyclomatic complexity 48 and cognitive complexity 58; 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 GitProjectSyncDropdown (cyclomatic 48, cognitive 35) packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:52— GitProjectSyncDropdown has cyclomatic complexity 48 and cognitive complexity 35; 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 61) packages/insomnia/src/ui/components/templating/tag-editor.tsx:371— (anonymous) has cyclomatic complexity 44 and cognitive complexity 61; 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 createConfiguredCurlInstance (cyclomatic 43, cognitive 70) packages/insomnia/src/main/network/libcurl-promise.ts:344— createConfiguredCurlInstance has cyclomatic complexity 43 and cognitive complexity 70; 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 clientAction (cyclomatic 42, cognitive 46) packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.new.tsx:41— clientAction has cyclomatic complexity 42 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 onMove (cyclomatic 41, cognitive 64) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:693— onMove has cyclomatic complexity 41 and cognitive complexity 64; 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 HeaderPlanIndicator (cyclomatic 41, cognitive 38) packages/insomnia/src/ui/components/header-plan-indicator.tsx:23— HeaderPlanIndicator has cyclomatic complexity 41 and cognitive complexity 38; 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 GitSyncDropdown (cyclomatic 41, cognitive 30) packages/insomnia/src/ui/components/dropdowns/git-sync-dropdown.tsx:43— GitSyncDropdown has cyclomatic complexity 41 and cognitive complexity 30; 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 40, cognitive 76) packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:183— (anonymous) has cyclomatic complexity 40 and cognitive complexity 76; 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.
R3 · Large Files· packages/insomnia/src/main/git-service.ts · ×1
packages/insomnia/src/main/git-service.ts: 3782 lines of code packages/insomnia/src/main/git-service.ts:1— packages/insomnia/src/main/git-service.ts has 3782 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/insomnia/src/ui/components/modals/git-project-staging-modal.tsx · ×1
packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx: 2146 lines of code packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx:1— packages/insomnia/src/ui/components/modals/git-project-staging-modal.tsx has 2146 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/insomnia/src/sync/git/git-vcs.ts · ×1
packages/insomnia/src/sync/git/git-vcs.ts: 1977 lines of code packages/insomnia/src/sync/git/git-vcs.ts:1— packages/insomnia/src/sync/git/git-vcs.ts has 1977 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/insomnia/src/common/insomnia-v5.ts · ×1
packages/insomnia/src/common/insomnia-v5.ts: 1437 lines of code packages/insomnia/src/common/insomnia-v5.ts:1— packages/insomnia/src/common/insomnia-v5.ts has 1437 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/insomnia/src/ui/components/spec-view.tsx · ×1
packages/insomnia/src/ui/components/spec-view.tsx: 1367 lines of code packages/insomnia/src/ui/components/spec-view.tsx:1— packages/insomnia/src/ui/components/spec-view.tsx has 1367 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/insomnia-vcs/src/vcs.ts · ×1
packages/insomnia-vcs/src/vcs.ts: 1272 lines of code packages/insomnia-vcs/src/vcs.ts:1— packages/insomnia-vcs/src/vcs.ts has 1272 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/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx · ×1
packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx: 1199 lines of code packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:1— packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx has 1199 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/insomnia/src/sync/git/repo-file-watcher.ts · ×1
packages/insomnia/src/sync/git/repo-file-watcher.ts: 1194 lines of code packages/insomnia/src/sync/git/repo-file-watcher.ts:1— packages/insomnia/src/sync/git/repo-file-watcher.ts has 1194 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/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx · ×1
packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx: 1151 lines of code packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx:1— packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.runner.tsx has 1151 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/insomnia/src/main/templating-worker-database.ts · ×1
packages/insomnia/src/main/templating-worker-database.ts: 1090 lines of code packages/insomnia/src/main/templating-worker-database.ts:1— packages/insomnia/src/main/templating-worker-database.ts has 1090 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: 1006 lines of code REDACTED:1— REDACTED has 1006 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/insomnia/src/ui/components/settings/import-export.tsx · ×1
packages/insomnia/src/ui/components/settings/import-export.tsx: 972 lines of code packages/insomnia/src/ui/components/settings/import-export.tsx:1— packages/insomnia/src/ui/components/settings/import-export.tsx has 972 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/insomnia/src/common/templating/local-template-tags.ts · ×1
packages/insomnia/src/common/templating/local-template-tags.ts: 960 lines of code packages/insomnia/src/common/templating/local-template-tags.ts:1— packages/insomnia/src/common/templating/local-template-tags.ts has 960 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: 944 lines of code REDACTED:1— REDACTED has 944 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/insomnia/src/common/render.ts · ×1
packages/insomnia/src/common/render.ts: 931 lines of code packages/insomnia/src/common/render.ts:1— packages/insomnia/src/common/render.ts has 931 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/insomnia/src/ui/components/example-openapi-specs.ts · ×1
packages/insomnia/src/ui/components/example-openapi-specs.ts: 920 lines of code packages/insomnia/src/ui/components/example-openapi-specs.ts:1— packages/insomnia/src/ui/components/example-openapi-specs.ts has 920 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/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx · ×1
packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx: 888 lines of code packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx:1— packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/use-sidebar-drag-and-drop.tsx has 888 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/insomnia/src/main/ipc/main.ts · ×1
packages/insomnia/src/main/ipc/main.ts: 879 lines of code packages/insomnia/src/main/ipc/main.ts:1— packages/insomnia/src/main/ipc/main.ts has 879 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/insomnia/src/main/importers/importers/postman.ts · ×1
packages/insomnia/src/main/importers/importers/postman.ts: 854 lines of code packages/insomnia/src/main/importers/importers/postman.ts:1— packages/insomnia/src/main/importers/importers/postman.ts has 854 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: 838 lines of code REDACTED:1— REDACTED has 838 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/insomnia/src/ui/components/modals/import-modal/import-modal.tsx · ×1
packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx: 827 lines of code packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx:1— packages/insomnia/src/ui/components/modals/import-modal/import-modal.tsx has 827 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/insomnia/src/root.tsx · ×1
packages/insomnia/src/root.tsx: 801 lines of code packages/insomnia/src/root.tsx:1— packages/insomnia/src/root.tsx 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· packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx · ×1
packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx: 799 lines of code packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx:1— packages/insomnia/src/ui/components/dropdowns/git-project-sync-dropdown.tsx has 799 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/insomnia/src/common/import.ts · ×1
packages/insomnia/src/common/import.ts: 797 lines of code packages/insomnia/src/common/import.ts:1— packages/insomnia/src/common/import.ts has 797 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/insomnia-scripting-environment/src/objects/auth.ts · ×1
packages/insomnia-scripting-environment/src/objects/auth.ts: 761 lines of code packages/insomnia-scripting-environment/src/objects/auth.ts:1— packages/insomnia-scripting-environment/src/objects/auth.ts has 761 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/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx · ×1
packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx: 744 lines of code packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx:1— packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx has 744 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/insomnia/src/ui/components/project/project-settings-form.tsx · ×1
packages/insomnia/src/ui/components/project/project-settings-form.tsx: 741 lines of code packages/insomnia/src/ui/components/project/project-settings-form.tsx:1— packages/insomnia/src/ui/components/project/project-settings-form.tsx has 741 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/insomnia/src/ui/components/modals/new-workspace-modal.tsx · ×1
packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx: 738 lines of code packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx:1— packages/insomnia/src/ui/components/modals/new-workspace-modal.tsx has 738 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/insomnia/src/ui/components/templating/tag-editor.tsx · ×1
packages/insomnia/src/ui/components/templating/tag-editor.tsx: 734 lines of code packages/insomnia/src/ui/components/templating/tag-editor.tsx:1— packages/insomnia/src/ui/components/templating/tag-editor.tsx has 734 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/insomnia/src/main/importers/importers/openapi-3.ts · ×1
packages/insomnia/src/main/importers/importers/openapi-3.ts: 731 lines of code packages/insomnia/src/main/importers/importers/openapi-3.ts:1— packages/insomnia/src/main/importers/importers/openapi-3.ts has 731 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/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx · ×1
packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx: 727 lines of code packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx:1— packages/insomnia/src/routes/organization.$organizationId.project.$projectId._index.tsx has 727 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/insomnia/src/ui/components/settings/plugins.tsx · ×1
packages/insomnia/src/ui/components/settings/plugins.tsx: 720 lines of code packages/insomnia/src/ui/components/settings/plugins.tsx:1— packages/insomnia/src/ui/components/settings/plugins.tsx has 720 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/insomnia/src/konnect/sync.ts · ×1
packages/insomnia/src/konnect/sync.ts: 697 lines of code packages/insomnia/src/konnect/sync.ts:1— packages/insomnia/src/konnect/sync.ts has 697 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/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx · ×1
packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx: 681 lines of code packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx:1— packages/insomnia/src/ui/components/modals/invite-modal/invite-modal.tsx has 681 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: 679 lines of code REDACTED:1— REDACTED has 679 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/insomnia-scripting-environment/src/objects/request.ts · ×1
packages/insomnia-scripting-environment/src/objects/request.ts: 677 lines of code packages/insomnia-scripting-environment/src/objects/request.ts:1— packages/insomnia-scripting-environment/src/objects/request.ts has 677 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/insomnia/src/ui/components/settings/credentials.tsx · ×1
packages/insomnia/src/ui/components/settings/credentials.tsx: 672 lines of code packages/insomnia/src/ui/components/settings/credentials.tsx:1— packages/insomnia/src/ui/components/settings/credentials.tsx has 672 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/insomnia/src/plugins/index.ts · ×1
packages/insomnia/src/plugins/index.ts: 666 lines of code packages/insomnia/src/plugins/index.ts:1— packages/insomnia/src/plugins/index.ts has 666 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: 650 lines of code REDACTED:1— REDACTED has 650 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/insomnia/src/ui/components/mcp/mcp-pane.tsx · ×1
packages/insomnia/src/ui/components/mcp/mcp-pane.tsx: 648 lines of code packages/insomnia/src/ui/components/mcp/mcp-pane.tsx:1— packages/insomnia/src/ui/components/mcp/mcp-pane.tsx has 648 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Unlisted import '@fortawesome/fontawesome-common-types' packages/insomnia/src/ui/components/icon.tsx:1— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unlisted import '@react-types/menu' packages/insomnia/src/ui/components/base/dropdown/dropdown.tsx:2— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unlisted import '@react-types/overlays' packages/insomnia/src/ui/components/base/dropdown/dropdown.tsx:3— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unlisted import '@react-types/shared' packages/insomnia/src/basic-components/select-popover.tsx:1— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unlisted import '@sentry/core' packages/insomnia/src/common/sentry.ts:1— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unlisted import 'graphql-language-service' packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx:18— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unlisted import '@docusaurus/plugin-content-docs' packages/insomnia-component-docs/sidebars.ts:1— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unused dependency 'dependency-cruiser' — Declared in the root REDACTED 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 '@docusaurus/module-type-aliases' — Declared in packages/insomnia-component-docs/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 'clsx' — Declared in packages/insomnia-component-docs/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.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) packages/insomnia/src/sync/git/utils.ts:100— `spawn` pipes `stderr` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `proc.stderr`, while `proc.stdout` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stderr (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`proc.stderr.on('data', …)`, or `proc.stderr.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×1
Untrusted text written into markup unescaped packages/insomnia/src/ui/components/markdown-preview.tsx:62— `compiled` 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.
X29 · Per-element action decided by a fixed element· Per-element action decided by a fixed element · ×1
Per-element action decided by a fixed element packages/insomnia/src/ui/utils.ts:33— This loop runs once per element of `moves`, and the statement it guards acts on the element it is on — `moves[j]`. The test deciding whether that statement runs does not: `b > a` reads `moves[i]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 29, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
No direct assertions: after-response scripts: transient vars, assertions, and environment/global persistence packages/insomnia-smoke-test/tests/smoke/after-response-script-features.test.ts:9— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: insomnia.expect covers each matcher (equal/property/lengthOf/include/within/keys) and test.skip is reported packages/insomnia-smoke-test/tests/smoke/after-response-script-features.test.ts:147— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: can send requests packages/insomnia-smoke-test/tests/smoke/app.test.ts:5— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: can chain multiple requests packages/insomnia-smoke-test/tests/smoke/chained-responses.test.ts:6— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: Discard, branch and commit actions packages/insomnia-smoke-test/tests/smoke/cloud-sync.test.ts:42— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: Push actions packages/insomnia-smoke-test/tests/smoke/cloud-sync.test.ts:121— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: Check delete workspace locally and remotely packages/insomnia-smoke-test/tests/smoke/cloud-sync.test.ts:155— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: Delete an unsynced remote file from the project dashboard packages/insomnia-smoke-test/tests/smoke/cloud-sync.test.ts:184— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: keeps concurrently-activated workspaces on their own backend project packages/insomnia-smoke-test/tests/smoke/cloud-sync.test.ts:211— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: Command palette - can switch between requests and workspaces packages/insomnia-smoke-test/tests/smoke/command-palette.test.ts:6— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: redacts the timeline file and the response document packages/insomnia-smoke-test/tests/smoke/confidential-redaction.test.ts:83— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: redacts the timeline of a request re-sent by a template tag packages/insomnia-smoke-test/tests/smoke/confidential-redaction.test.ts:112— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: redacts a Basic Auth header derived from a confidential value packages/insomnia-smoke-test/tests/smoke/confidential-redaction.test.ts:131— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: writes plaintext to the timeline when the setting is off packages/insomnia-smoke-test/tests/smoke/confidential-redaction.test.ts:152— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: create and send a cookie packages/insomnia-smoke-test/tests/smoke/cookie-editor-interactions.test.ts:16— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: support __Host- prefix packages/insomnia-smoke-test/tests/smoke/cookie-editor-interactions.test.ts:62— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: cookie list should update when cookie is updated packages/insomnia-smoke-test/tests/smoke/cookie-editor-interactions.test.ts:89— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: upload custom ruleset, lint reflects it, persists after app relaunch packages/insomnia-smoke-test/tests/smoke/custom-lint-rules.test.ts:192— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: remove custom ruleset reverts to default OAS, persists after app relaunch packages/insomnia-smoke-test/tests/smoke/custom-lint-rules.test.ts:233— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: uploading a ruleset with disallowed keys shows an error and leaves default ruleset active packages/insomnia-smoke-test/tests/smoke/custom-lint-rules.test.ts:255— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: upload custom ruleset in a synced design project packages/insomnia-smoke-test/tests/smoke/custom-lint-rules.test.ts:299— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: same user, different machine: ruleset survives push → pull round-trip packages/insomnia-smoke-test/tests/smoke/custom-lint-rules.test.ts:328— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: different users: ruleset uploaded by user A is visible to user B after pull packages/insomnia-smoke-test/tests/smoke/custom-lint-rules.test.ts:358— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: 4a. upload ruleset via UI mirrors to .spectral.yaml on disk packages/insomnia-smoke-test/tests/smoke/custom-lint-rules.test.ts:415— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: 4b. .spectral.yaml on disk syncs to UI badge packages/insomnia-smoke-test/tests/smoke/custom-lint-rules.test.ts:427— No conventional assertion call was detected, and 243 of 243 tests in `packages/insomnia-smoke-test` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
+ 218 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel packages/insomnia/customSign.js:12— `packages/insomnia/customSign.js` reports through `console.*` at line 12 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 packages/insomnia/customSign.js:18— `packages/insomnia/customSign.js` reports through `console.*` at line 18 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 packages/insomnia/customSign.js:25— `packages/insomnia/customSign.js` reports through `console.*` at line 25 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 packages/insomnia/customSign.js:31— `packages/insomnia/customSign.js` reports through `console.*` at line 31 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 packages/insomnia/customSign.js:34— `packages/insomnia/customSign.js` reports through `console.*` at line 34 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 packages/insomnia/customSign.js:36— `packages/insomnia/customSign.js` reports through `console.*` at line 36 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 packages/insomnia/customSign.js:39— `packages/insomnia/customSign.js` reports through `console.*` at line 39 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 packages/insomnia/customSign.js:41— `packages/insomnia/customSign.js` reports through `console.*` at line 41 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 packages/insomnia/src/entry.hidden-window-preload.ts:39— `packages/insomnia/src/entry.hidden-window-preload.ts` reports through `console.*` at line 39 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 packages/insomnia/src/entry.hidden-window.ts:50— `packages/insomnia/src/entry.hidden-window.ts` reports through `console.*` at line 50 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 packages/insomnia/src/entry.hidden-window.ts:58— `packages/insomnia/src/entry.hidden-window.ts` reports through `console.*` at line 58 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 packages/insomnia/src/entry.plugin-window.ts:23— `packages/insomnia/src/entry.plugin-window.ts` reports through `console.*` at line 23 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 packages/insomnia/src/entry.plugin-window.ts:39— `packages/insomnia/src/entry.plugin-window.ts` reports through `console.*` at line 39 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 packages/insomnia/src/entry.preload.ts:371— `packages/insomnia/src/entry.preload.ts` reports through `console.*` at line 371 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 packages/insomnia/src/script-executor.ts:25— `packages/insomnia/src/script-executor.ts` reports through `console.*` at line 25 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 packages/insomnia/src/script-executor.ts:73— `packages/insomnia/src/script-executor.ts` reports through `console.*` at line 73 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 packages/insomnia/src/script-executor.ts:74— `packages/insomnia/src/script-executor.ts` reports through `console.*` at line 74 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 packages/insomnia/src/entry.client.tsx:87— `packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 87 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 packages/insomnia/src/entry.client.tsx:144— `packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 144 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 packages/insomnia/src/entry.client.tsx:164— `packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 164 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 packages/insomnia/src/entry.client.tsx:170— `packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 170 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 packages/insomnia/src/entry.client.tsx:185— `packages/insomnia/src/entry.client.tsx` reports through `console.*` at line 185 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 packages/insomnia/src/entry.server.tsx:56— `packages/insomnia/src/entry.server.tsx` reports through `console.*` at line 56 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 packages/insomnia/src/root.tsx:89— `packages/insomnia/src/root.tsx` 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 packages/insomnia/src/root.tsx:744— `packages/insomnia/src/root.tsx` reports through `console.*` at line 744 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 packages/insomnia/src/ui/hooks/use-organization-features.tsx:38— `!!organizationId && !models.organization.isLocalOrganizationId(organizationId)` appears character-identically in 2 files — packages/insomnia/src/ui/hooks/use-organization-features.tsx, packages/insomnia/src/ui/hooks/use-remote-files.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 packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx:140— `!(typeof code === 'string') || !(typeof state === 'string')` appears character-identically in 2 files — packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx, packages/insomnia/src/ui/components/settings/credentials.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 packages/insomnia/src/ui/components/settings/llms/gguf.tsx:186— `!Number.isNaN(value) && value >= 0 && value <= 1` appears character-identically in 2 files — packages/insomnia/src/ui/components/settings/llms/gguf.tsx, packages/insomnia/src/ui/components/settings/llms/url.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 packages/insomnia/src/ui/components/settings/llms/gguf.tsx:168— `!Number.isNaN(value) && value >= 0 && value <= 2` appears character-identically in 2 files — packages/insomnia/src/ui/components/settings/llms/gguf.tsx, packages/insomnia/src/ui/components/settings/llms/url.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 packages/insomnia/src/ui/components/settings/llms/claude.tsx:172— `!hasLoadedModels || !selectedModel || (isCurrentBackend && !hasChanges)` appears character-identically in 3 files — packages/insomnia/src/ui/components/settings/llms/claude.tsx, packages/insomnia/src/ui/components/settings/llms/gemini.tsx, packages/insomnia/src/ui/components/settings/llms/openai.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 packages/insomnia/src/templating/index.ts:37— `!hasTemplateInterpolationSymbols && !hasTemplateTagSymbols && !hasTemplateCommentSymbols` appears character-identically in 2 files — packages/insomnia/src/templating/index.ts, packages/insomnia/src/ui/templating/worker.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 packages/insomnia/src/templating/index.ts:101— `!ignoreUndefinedEnvVariable && liquidAll && liquidAllTagMetadata` appears character-identically in 2 files — packages/insomnia/src/templating/index.ts, packages/insomnia/src/ui/templating/worker.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 packages/insomnia/src/main/network/socket-io.ts:311— `!options.suppressUserAgent && !request.disableUserAgentHeader && !hasUserAgentHeader` appears character-identically in 2 files — packages/insomnia/src/main/network/socket-io.ts, packages/insomnia/src/main/network/websocket.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 packages/insomnia/src/ui/components/mcp/event-view.tsx:85— `!responseFilter || responseFilterHistory.includes(responseFilter)` appears character-identically in 3 files — packages/insomnia/src/ui/components/mcp/event-view.tsx, packages/insomnia/src/ui/components/panes/response-pane.tsx, packages/insomnia/src/ui/components/socket-io/event-view.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 packages/insomnia/src/runtimes/network/network-adapter.node.ts:68— `!settingStoreCookies || !setCookieStrings.length` appears character-identically in 2 files — packages/insomnia/src/runtimes/network/network-adapter.node.ts, packages/insomnia/src/runtimes/network/network-adapter.renderer.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 packages/insomnia/src/main/api.protocol.ts:92— `!shouldBypassProxyForHost(hostname, noProxy) && proxyHost` appears character-identically in 2 files — packages/insomnia/src/main/api.protocol.ts, packages/insomnia/src/main/network/libcurl-promise.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 packages/insomnia/src/ui/components/modals/git-branches-modal.tsx:196— `'errors' in result && result.errors && result.errors?.length > 0` appears character-identically in 2 files — packages/insomnia/src/ui/components/modals/git-branches-modal.tsx, packages/insomnia/src/ui/components/modals/git-project-branches-modal.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 packages/insomnia/src/ui/components/mcp/event-view.tsx:141— `('previewMode' in activeRequestMeta && activeRequestMeta.previewMode) || PREVIEW_MODE_SOURCE` appears character-identically in 2 files — packages/insomnia/src/ui/components/mcp/event-view.tsx, packages/insomnia/src/ui/components/websockets/event-view.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 packages/insomnia/src/ui/components/.client/codemirror/code-editor.tsx:482— `(await handleGetRenderContext())?.keys || []` appears character-identically in 2 files — packages/insomnia/src/ui/components/.client/codemirror/code-editor.tsx, packages/insomnia/src/ui/components/.client/codemirror/one-line-editor.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 packages/insomnia-data/node-src/services/mcp-response.ts:37— `(await settingsService.get()).filterResponsesByEnv && 'environmentId' in patch` appears character-identically in 3 files — packages/insomnia-data/node-src/services/mcp-response.ts, packages/insomnia-data/node-src/services/socket-io-response.ts, packages/insomnia-data/node-src/services/websocket-response.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 packages/insomnia/src/main/network/socket-io.ts:195— `(caCertficatePath && (await insecureReadFile(caCertficatePath))) || tls.rootCertificates.join('\n')` appears character-identically in 2 files — packages/insomnia/src/main/network/socket-io.ts, packages/insomnia/src/main/network/websocket.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 packages/insomnia/src/ui/components/git-credentials/git-custom-credential-form.tsx:31— `(formData.get('authorEmail') as string) || ''` appears character-identically in 2 files — packages/insomnia/src/ui/components/git-credentials/git-custom-credential-form.tsx, packages/insomnia/src/ui/components/settings/credentials.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 packages/insomnia/src/ui/components/git-credentials/git-custom-credential-form.tsx:30— `(formData.get('authorName') as string) || ''` appears character-identically in 2 files — packages/insomnia/src/ui/components/git-credentials/git-custom-credential-form.tsx, packages/insomnia/src/ui/components/settings/credentials.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 packages/insomnia/src/common/project.ts:236— `(hasUnsavedChanges && modifiedLocally) || gitRepository?.cachedGitLastCommitTime || lastModifiedTimestamp` appears character-identically in 2 files — packages/insomnia/src/common/project.ts, packages/insomnia/src/routes/organization.$organizationId.project.$projectId.list-workspaces.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 packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx:52— `(prevState === 'submitting' || prevState === 'loading') && completeSignInFetcher.state === 'idle' && completeSignInFetcher.data && !complete…` appears character-identically in 2 files — packages/insomnia/src/ui/components/git/git-oauth-auth-banner.tsx, packages/insomnia/src/ui/components/settings/credentials.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 packages/insomnia-inso/src/commands/lint-specification.ts:32— `Boolean(url.hostname) && !isPrivateOrLoopbackHost(url.hostname.toLowerCase())` appears character-identically in 2 files — packages/insomnia-inso/src/commands/lint-specification.ts, packages/insomnia/src/main/lint-process.mjs. 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 packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.test.test-suite.$testSuiteId.tsx:149— `[request.method] || 'bg-(--hl-md) text-(--color-font)'` appears character-identically in 2 files — packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.test.test-suite.$testSuiteId.tsx, packages/insomnia/src/ui/components/modals/export-requests-modal.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 packages/insomnia/src/main/lint-process.mjs:24— `a === 0 || a === 127 || a === 10 || (a === 172 && b >= 16 && b <= 31) || (a === 192 && b === 168) || (a === 169 && b === 254)` appears character-identically in 2 files — packages/insomnia/src/main/lint-process.mjs, packages/insomnia/src/main/private-host.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 packages/insomnia/src/main/network/socket-io.ts:290— `activeEnvironment || (await services.environment.getOrCreateForParentId(options.workspaceId))` appears character-identically in 2 files — packages/insomnia/src/main/network/socket-io.ts, packages/insomnia/src/main/network/websocket.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 packages/insomnia/src/main/mcp/common.ts:139— `activeEnvironmentId && (await services.environment.getById(activeEnvironmentId))` appears character-identically in 4 files — packages/insomnia/src/main/mcp/common.ts, packages/insomnia/src/main/network/socket-io.ts, packages/insomnia/src/main/network/websocket.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Deprecated: @koa/router REDACTED:3134— @koa/router 13.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to v15 or higher. All reported bugs in this version are fixed in newer releases, dependencies have been updated, and security has been improved.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: boolean REDACTED:10550— boolean 3.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:15022— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:15235— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:16034— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash.get REDACTED:18413— lodash.get 4.4.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use the optional chaining (?.) operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash.isequal REDACTED:18432— lodash.isequal 4.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:19062— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: node-domexception REDACTED:19352— node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:22421— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: sourcemap-codec REDACTED:23424— sourcemap-codec 1.4.8 is resolved in REDACTED and is marked deprecated by its publisher: "Please use @jridgewell/sourcemap-codec instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:24286— rimraf 2.6.3 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: whatwg-encoding REDACTED:25996— whatwg-encoding 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: acorn-dynamic-import REDACTED:4473— acorn-dynamic-import 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is probably built in to whatever tool you're using. If you still need it... idk". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:9234— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: sourcemap-codec REDACTED:17378— sourcemap-codec 1.4.8 is resolved in REDACTED and is marked deprecated by its publisher: "Please use @jridgewell/sourcemap-codec instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Orphaned file packages/insomnia/src/sync/git/mem-client.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/insomnia/src/plugins/context/request.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/insomnia-data/__mocks__/uuid.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/insomnia-data/common-src/keyboard-keys.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/insomnia/src/ui/utils/prettify/json.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/insomnia/src/main/ipc/automock.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/insomnia/src/__mocks__/@getinsomnia/node-libcurl.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/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-search-results.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 packages/insomnia/src/ui/utils/prettify/edn.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/insomnia-testing/src/run/javascript-reporter.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/insomnia/src/main/network/o-auth-1/get-token.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/insomnia/src/plugins/context/response.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/insomnia/src/main/importers/importers/har.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/insomnia/src/sync/delta/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 packages/insomnia-inso/src/db/models/environment.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/insomnia-vcs/src/store/index.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.
Silent fallback default in catch packages/insomnia-api/src/spaces.ts:64— `readProblemJson` 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 packages/insomnia-data/common-src/ndjson.ts:12— `deserializeNDJSON` 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 packages/insomnia-scripting-environment/src/objects/urls.ts:633— `resolveProtocolForProxy` swallows every exception into `return 'https:'` — 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 packages/insomnia/src/main/har.ts:408— `getCookiesForUrl` 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 packages/insomnia/src/common/import-deep-link.ts:32— `sanitizeUrlAndExtractOrigin` 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 packages/insomnia/src/common/zod/find-unknown-field-ranges.ts:72— `findUnknownFieldRanges` 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 packages/insomnia/src/ui/analytics.ts:39— `readPendingImportAttribution` 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 packages/insomnia/src/main/ipc/cookies.ts:52— `getCookiesForUrl` 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 packages/insomnia/src/main/proxy.ts:65— `insomniaIntegrationHosts` 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 packages/insomnia/src/konnect/migrate-konnect-organization.ts:26— `readCachedOrganizations` 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 packages/insomnia/src/main/templating-worker-database-surface.ts:162— `stringifyHandlerResult` 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 packages/insomnia/src/routes/organization.$organizationId.collaborators-search.tsx:29— `clientLoader` 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 packages/insomnia/src/ui/components/dropdowns/method-selector.tsx:23— `readRecentMethods` 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 packages/insomnia/src/ui/components/project/utils.tsx:37— `getLastCloneParentDir` 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 packages/insomnia/src/ui/components/sidebar/project-navigation-sidebar/project-navigation-sidebar.tsx:151— `readLocalStorageString` (in `ProjectNavigationSidebarInner`) 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.
Mock-dominated test: registers the merge conflict listener once packages/insomnia/src/ui/utils/__tests__/insomnia-sync.test.ts:18— This test sets up 3 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: routes merge conflict modal callbacks back through the sync bridge packages/insomnia/src/ui/utils/__tests__/insomnia-sync.test.ts:39— 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: warns and skips the dialog when activeResponse is null packages/insomnia/src/ui/components/panes/__tests__/response-pane-utils.test.ts:23— This test sets up 3 test doubles (for example `vi.spyOn`) 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: warns and skips the dialog when activeRequest is null packages/insomnia/src/ui/components/panes/__tests__/response-pane-utils.test.ts:33— This test sets up 3 test doubles (for example `vi.spyOn`) 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: copies the body from disk instead of writing an empty file packages/insomnia/src/ui/components/panes/__tests__/response-pane-utils.test.ts:128— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) 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: prefers the streaming copy over an in-memory buffer for the raw export packages/insomnia/src/ui/components/panes/__tests__/response-pane-utils.test.ts:179— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) 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: returns early when initializing a workspace backend project without a session packages/insomnia/src/main/__tests__/sync-initialization.test.ts:85— 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 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: skips workspace backend initialization when the workspace already has git metadata packages/insomnia/src/main/__tests__/sync-initialization.test.ts:95— 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: skips syncing a new workspace when the project is not remote packages/insomnia/src/main/__tests__/sync-initialization.test.ts:104— 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 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: skips syncing a new workspace when cloud sync is disabled packages/insomnia/src/main/__tests__/sync-initialization.test.ts:115— 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 5 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: initializes and pushes a new workspace for cloud sync-enabled remote projects packages/insomnia/src/main/__tests__/sync-initialization.test.ts:129— 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 6 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.
Outdated (npm): commander packages/insomnia-inso/package.json:61— commander is pinned at 12.1.0; registry.npmjs.org publishes 15.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): content-disposition REDACTED:99— content-disposition is pinned at 0.5.4; registry.npmjs.org publishes 3.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): fuzzysort packages/insomnia-data/package.json:41— fuzzysort is pinned at 1.9.0; registry.npmjs.org publishes 4.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): hosted-git-info REDACTED:117— hosted-git-info is pinned at 5.2.1; registry.npmjs.org publishes 10.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): marked REDACTED:134— marked is pinned at 5.1.2; registry.npmjs.org publishes 18.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): uuid packages/insomnia-data/package.json:43— uuid is pinned at 11.1.1; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 6 significant file(s) lose their only recent owner: packages/insomnia/src/ui/components/trail-lines.tsx, packages/insomnia/src/common/stream-summary.ts, packages/insomnia-data/node-src/database/repair-database.ts, packages/insomnia/src/ui/components/keydown-binder.ts, packages/insomnia-data/node-src/services/mcp-response.ts, packages/insomnia/src/common/api-specs.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: packages/insomnia/src/ui/components/dropdowns/sidebar-shortcut-actions-dropdown.tsx, packages/insomnia/src/ui/components/templating/external-vault/external-vault-form.tsx, packages/insomnia-data/src/models/cloud-credential.ts, packages/insomnia/src/ui/components/dropdowns/actions/create-actions.ts, packages/insomnia-data/src/services/types.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 5 significant file(s) lose their only recent owner: packages/insomnia-vcs/src/backend-projects.ts, packages/insomnia/src/routes/organization.$organizationId.project.tsx, packages/insomnia/src/ui/components/unsynced-file-delete-button.tsx, packages/insomnia/src/ui/components/project/git-repo-scan-result.tsx, packages/insomnia/src/ui/components/modals/konnect-org-migration-modal.tsx. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/insomnia/src/ui/components/settings/llms/url.tsx, packages/insomnia-api/src/spaces.ts, packages/insomnia/src/ui/components/settings/llms/url-utils.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/insomnia/src/routes/git-migration.$.tsx, packages/insomnia/scripts/generate-schema.ts, packages/insomnia/src/routes/organization.$organizationId.project.$projectId.workspace.$workspaceId.debug.request.delete.test.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/insomnia-scripting-environment/src/objects/headers.ts, packages/insomnia-scripting-environment/src/objects/folders.ts, packages/insomnia-scripting-environment/src/objects/variables.ts. Pair on, review, or document these before any departure.
Fat interface: IDatabase (19 required operations) packages/insomnia-data/src/database/types.ts:48— `IDatabase` declares 19 required operations: `batchModifyDocs`, `bufferChanges`, `bufferChangesIndefinitely`, `count`, `docCreate`, `docUpdate`, `duplicate`, `find`, `findOne`, `flushChanges`, `init`, `insert`, `onChange`, `remove`, `removeWhere`, `unsafeRemove`, `update`, `withAncestors`, `getWithDescendants`. 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.
Fat interface: PluginsBridgeAPI (18 required operations) packages/insomnia/src/common/plugins/bridge-types.ts:150— `PluginsBridgeAPI` declares 18 required operations: `getThemes`, `getPlugins`, `getActivePlugins`, `reloadPlugins`, `getRequestActions`, `getRequestGroupActions`, `getWorkspaceActions`, `getDocumentActions`, `executeAction`, `getTemplateTags`, `runTemplateTagAction`, `getBundlePlugins`, `executePluginMainAction`, `hasRequestHooks`, `hasResponseHooks`, `applyRequestHooks`, `applyResponseHooks`, `getBridgeMetrics`. 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.
Fat interface: SyncBridgeMethods (24 required operations) packages/insomnia/src/main/cloud-sync/ipc.ts:26— `SyncBridgeMethods` declares 24 required operations: `archiveProject`, `checkout`, `compareRemoteBranch`, `fork`, `getBranchNames`, `getCurrentBranchName`, `getHistory`, `getHistoryCount`, `getRemoteBranchNames`, `getVersion`, `merge`, `pull`, `push`, `removeBranch`, `removeRemoteBranch`, `rollback`, `rollbackToLatest`, `stage`, `status`, `switchAndCreateBackendProjectIfNotExist`, `takeSnapshot`, `unstage`, `getActiveBackendProject`, `hasBackendProject`. 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.
Fat interface: RendererToMainBridgeAPI (51 required operations) packages/insomnia/src/main/ipc/main.ts:218— `RendererToMainBridgeAPI` declares 51 required operations: `runTests`, `loginStateChange`, `openInBrowser`, `restart`, `halfSecondAfterAppStart`, `openDeepLink`, `manualUpdateCheck`, `applyUpdateAndRestart`, `getUpdateStatus`, `backup`, `restoreBackup`, `setMenuBarVisibility`, `multipartBufferToArray`, `writeFile`, `deleteCompiledRuleset`, `refreshCompiledRuleset`, `writeResponseBodyToFile`, `getAuthHeader`, `getOAuth2Token`, `secureReadFile`, `insecureReadFile`, `insecureReadFileWithEncoding`, `readDir`, `readOrCreateDataDir`, `on`, `trackAnalyticsEvent`, `trackPageView`, `setCurrentOrganizationId`, `showNunjucksContextMenu`, `showContextMenu`, `lintSpec`, `bundleSpectralRuleset`, `createPlugin`, `getExecution`, `addExecutionStep`, `startExecution`, `completeExecutionStep`, `updateLatestStepName`, `extractJsonFileFromPostmanDataDumpArchive`, `getLocalStorageDataFromFileOrigin`, and 11 more. 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.
Disabled test packages/insomnia-inso/src/commands/lint-specification.test.ts:45— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/insomnia-smoke-test/tests/smoke/mock.test.ts:5— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/insomnia/src/common/utils/vault.test.ts:73— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/insomnia/src/common/utils/vault.test.ts:83— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
IC1 · Incompleteness & stubs· Empty method body · ×2
Empty method body packages/insomnia-data/__schemas__/model-schemas.ts:35— `certificates` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body packages/insomnia-vcs/src/__schemas__/model-schemas.ts:35— `certificates` has an empty body — confirm it's an intentional no-op and not an unfinished method.
R7 · Dead Code· Unused export 'GRANT_TYPE_REFRESH' · ×2
Unused export 'GRANT_TYPE_REFRESH' packages/insomnia/src/common/constants.ts:280— Nothing imports this binding — it is safe to review for removal.
Unused export 'GRANT_TYPE_REFRESH' packages/insomnia/src/main/network/o-auth-2/get-token.ts:52— Nothing imports this binding — it is safe to review for removal.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: packages/insomnia-smoke-test packages/insomnia-smoke-test/tests/smoke/after-response-script-features.test.ts:9— No conventional assertion call was detected in 243 of 243 tests in `packages/insomnia-smoke-test` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 5 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 (32 single-owned of 603 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; 603 of the 1310 production source files in this repository met that bar). They are anonymized user #7 (2 file(s)), anonymized user #8 (2 file(s)), anonymized user #9 (1 file(s)), anonymized user #10 (1 file(s)), anonymized user #11 (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: packages/insomnia/src/scripting/quickjs-script-engine.ts, packages/insomnia/src/common/plugins/sandbox-mode.ts, packages/insomnia/src/ui/components/socket-io/event-tab-pane.tsx, packages/insomnia/src/ui/hooks/image-cache.tsx, packages/insomnia-data/common-src/faker-functions.ts, packages/insomnia/src/sync/git/http-client.ts, packages/insomnia/src/ui/components/unsaved-changes-confirm-dialog.tsx.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 11 project(s) overshoot their size bounds, lowering Project Cohesion to 6.5/10. The most over is `packages/insomnia` (146085 LoC, 1548 module-visible types across 108 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 16 of 603 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 603 of the 1310 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/insomnia/src/sync/git/mem-client.ts, packages/insomnia/src/plugins/context/request.ts, packages/insomnia-data/__mocks__/uuid.ts, packages/insomnia-data/common-src/keyboard-keys.ts, packages/insomnia/src/ui/utils/prettify/json.ts, packages/insomnia/src/main/ipc/automock.ts, packages/insomnia/src/__mocks__/@getinsomnia/node-libcurl.ts, packages/insomnia/src/ui/components/graph-ql-explorer/graph-ql-explorer-search-results.tsx (and 8 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
README/code drift packages/insomnia-smoke-test/README.md:5— packages/insomnia-smoke-test/README.md links to `CLI.md`, but `packages/insomnia-smoke-test/CLI.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/insomnia-smoke-test`.
R7 · Dead Code· Unused export 'authOptionsToParams' · ×1
Unused export 'authOptionsToParams' packages/insomnia-scripting-environment/src/objects/auth.ts:190— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'backendProjectWithTeamSchema' · ×1
Unused export 'backendProjectWithTeamSchema' packages/insomnia-vcs/src/__schemas__/type-schemas.ts:25— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'snapshotStateEntrySchema' · ×1
Unused export 'snapshotStateEntrySchema' packages/insomnia-vcs/src/__schemas__/type-schemas.ts:57— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'resolveComponentSchemaRefs' · ×1
Unused export 'resolveComponentSchemaRefs' packages/insomnia/src/common/api-specs.ts:65— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getInsomniaVaultSrpSecret' · ×1
Unused export 'getInsomniaVaultSrpSecret' packages/insomnia/src/common/constants.ts:39— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getAppSynopsis' · ×1
Unused export 'getAppSynopsis' packages/insomnia/src/common/constants.ts:42— Nothing imports this binding — it is safe to review for removal.
Unused export 'LandingPage' packages/insomnia/src/common/sentry.ts:22— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'RegisterProtocolOptions' · ×1
Unused export 'RegisterProtocolOptions' packages/insomnia/src/main/api.protocol.ts:14— Nothing imports this binding — it is safe to review for removal.
Unused export 'GitChange' packages/insomnia/src/main/git-service.ts:3221— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getGitLabOauthApiURL' · ×1
Unused export 'getGitLabOauthApiURL' packages/insomnia/src/main/git-service.ts:3869— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'mockResponseMethods' · ×1
Unused export 'mockResponseMethods' packages/insomnia/src/main/ipc/automock.ts:22— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'McpRequestOptions' · ×1
Unused export 'McpRequestOptions' packages/insomnia/src/main/mcp/types.ts:12— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'GRANT_TYPE_IMPLICIT' · ×1
Unused export 'GRANT_TYPE_IMPLICIT' packages/insomnia/src/main/network/o-auth-2/get-token.ts:49— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'GRANT_TYPE_PASSWORD' · ×1
Unused export 'GRANT_TYPE_PASSWORD' packages/insomnia/src/main/network/o-auth-2/get-token.ts:50— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'GRANT_TYPE_CLIENT_CREDENTIALS' · ×1
Unused export 'GRANT_TYPE_CLIENT_CREDENTIALS' packages/insomnia/src/main/network/o-auth-2/get-token.ts:51— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'GRANT_TYPE_MCP_AUTH_FLOW' · ×1
Unused export 'GRANT_TYPE_MCP_AUTH_FLOW' packages/insomnia/src/main/network/o-auth-2/get-token.ts:53— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'PKCE_CHALLENGE_PLAIN' · ×1
Unused export 'PKCE_CHALLENGE_PLAIN' packages/insomnia/src/main/network/o-auth-2/get-token.ts:82— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'SocketIOEventLog' · ×1
Unused export 'SocketIOEventLog' packages/insomnia/src/main/network/socket-io.ts:88— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'WebSocketConnection' · ×1
Unused export 'WebSocketConnection' packages/insomnia/src/main/network/websocket.ts:42— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'WebSocketEventLog' · ×1
Unused export 'WebSocketEventLog' packages/insomnia/src/main/network/websocket.ts:78— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'reloadPluginsInWindow' · ×1
Unused export 'reloadPluginsInWindow' REDACTED:289— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getAppUserDataPath' · ×1
Unused export 'getAppUserDataPath' REDACTED:331— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'ExecuteScriptContext' · ×1
Unused export 'ExecuteScriptContext' packages/insomnia/src/network/concurrency.renderer.ts:17— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'requestModelSchema' · ×1
Unused export 'requestModelSchema' packages/insomnia/src/sync/__schemas__/model-schemas.ts:39— Nothing imports this binding — it is safe to review for removal.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 7/15 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted REDACTED:1033— `debug` at line 1033 is called with an argument built by `join(' ')` (line 1033), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Null assertions (`!`) reduce the strict null checking score — ~1.2 `!` null assertions per 1k TypeScript source lines — 211 assertion(s) across the 176805 source line(s) of the 1217 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/insomnia/src/ui/components/project/project-settings-form.tsx (17), packages/insomnia/src/ui/components/workspace/use-workspace-breadcrumb.tsx (10), packages/insomnia/src/konnect/sync.ts (9). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated (npm): @apidevtools/swagger-parser — @apidevtools/swagger-parser is pinned at 12.1.0; registry.npmjs.org publishes 13.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @customerio/cdp-analytics-browser — @customerio/cdp-analytics-browser is pinned at 0.5.9; registry.npmjs.org publishes 0.8.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docusaurus/core — @docusaurus/core is pinned at 3.9.2; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docusaurus/preset-classic — @docusaurus/preset-classic is pinned at 3.9.2; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docusaurus/theme-live-codeblock — @docusaurus/theme-live-codeblock is pinned at 3.9.2; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fortawesome/fontawesome-svg-core — @fortawesome/fontawesome-svg-core is pinned at 6.7.2; registry.npmjs.org publishes 7.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fortawesome/free-brands-svg-icons — @fortawesome/free-brands-svg-icons is pinned at 6.7.2; registry.npmjs.org publishes 7.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fortawesome/free-regular-svg-icons — @fortawesome/free-regular-svg-icons is pinned at 6.7.2; registry.npmjs.org publishes 7.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fortawesome/free-solid-svg-icons — @fortawesome/free-solid-svg-icons is pinned at 6.7.2; registry.npmjs.org publishes 7.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fortawesome/react-fontawesome — @fortawesome/react-fontawesome is pinned at 3.3.0; registry.npmjs.org publishes 3.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @getinsomnia/insomnia-v3-fetch — @getinsomnia/insomnia-v3-fetch is pinned at 1.0.27; registry.npmjs.org publishes 1.0.34 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @grpc/proto-loader — @grpc/proto-loader is pinned at 0.7.15; registry.npmjs.org publishes 0.8.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @react-router/fs-routes — @react-router/fs-routes is pinned at 7.18.2; registry.npmjs.org publishes 8.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @react-router/node — @react-router/node is pinned at 7.18.2; registry.npmjs.org publishes 8.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @react-router/serve — @react-router/serve is pinned at 7.18.2; registry.npmjs.org publishes 8.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @rjsf/core — @rjsf/core is pinned at 6.8.0; registry.npmjs.org publishes 6.11.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @rjsf/utils — @rjsf/utils is pinned at 6.8.0; registry.npmjs.org publishes 6.11.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @rjsf/validator-ajv8 — @rjsf/validator-ajv8 is pinned at 6.8.0; registry.npmjs.org publishes 6.11.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @segment/analytics-node — @segment/analytics-node is pinned at 2.2.1; registry.npmjs.org publishes 3.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @sentry/electron — @sentry/electron is pinned at 7.20.0; registry.npmjs.org publishes 8.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @stoplight/spectral-core — @stoplight/spectral-core is pinned at 1.22.0; registry.npmjs.org publishes 1.24.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @stoplight/spectral-formats — @stoplight/spectral-formats is pinned at 1.8.2; registry.npmjs.org publishes 1.9.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @stoplight/spectral-ruleset-bundler — @stoplight/spectral-ruleset-bundler is pinned at 1.7.0; registry.npmjs.org publishes 1.8.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @stoplight/spectral-rulesets — @stoplight/spectral-rulesets is pinned at 1.22.1; registry.npmjs.org publishes 1.23.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tailwindcss/postcss — @tailwindcss/postcss is pinned at 4.1.17; registry.npmjs.org publishes 4.3.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): (unnamed test) packages/insomnia-smoke-test/tests/smoke/paste-curl-import.test.ts:98— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/insomnia-smoke-test/tests/migration/git-repo-onboarding.test.ts:54— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/insomnia-smoke-test/tests/migration/local-to-cloud-projects.test.ts:4— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/insomnia/src/ui/components/settings/text-array-setting.test.ts:167— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/insomnia/src/plugins/__tests__/registry-cross-plugin-reachability.test.ts:111— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
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 17 file(s) — `packages/insomnia-component-docs/docusaurus.config.ts`, `packages/insomnia-data/node-src/services/index.ts`, `packages/insomnia-data/src/models/index.ts`, `packages/insomnia/react-router.config.ts`, `packages/insomnia/src/common/import-deep-link.ts`, … (+12 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 01a178f7-a8ef-77ea-a27e-815b9cc481b7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 146 · Warnings: 1446 · Recommendations: 445 · Info: 86 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 16:07 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.