Public report of warp-tech/warpgate, published 27 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). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 27 October 2026, 10:53 UTC · Survey ID cd_d3a2e66116d747a8bcee012852ee9edc
warp-tech/warpgate
Measured 27 October 2026, 10:50 UTC, at code version ab83bb3
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: Suite not runnable in-image and no committed report.
CAI scoreAt riskDown 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 86,279 lines of product code in 30 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Code Health, 49
Findings by how serious they are
31 critical358 serious109 minor
8 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
27 October 2026, 10:50 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 ▸
88of 88 dimensions measured by tools.
430of 498 findings point to an exact file and line, so you can open each one in the code. The other 68 concern the repository as a whole, such as missing documentation.
88dimensions across 8 lenses, read from 86,279 lines of product code in 30 projects.
warp-tech/warpgate is rated At risk because critical security findings are open. It scores 60 out of 100, which the At risk rating leaves unchanged.
Code Health, at 49, is the weakest lens and counts most in the score. The best first step is removing the unused code, worth about 8 points. Recording design decisions comes next, worth about 2 points. Raising Code Health to 70 would lift the score to about 68.
Seven pipeline steps install packages that can change without warning. Five known security holes in the packages the code depends on can be used by attackers, and five settings leave the servers or containers unsafe. Pinning what the pipeline installs, updating the vulnerable packages and correcting the unsafe settings would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and the two passwords or keys in the code need replacing, with the old ones switched off. The six sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 86,279 lines, about €95,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.
Large Files · warpgate-web/src/admin/config/Parameters.svelte: 1278 lines of code warpgate-web/src/admin/config/Parameters.svelte
Large Files · warpgate-web/src/admin/log-viewer/LogViewer.svelte: 1092 lines of code warpgate-web/src/admin/log-viewer/LogViewer.svelte
Large Files · warpgate-web/src/admin/config/targets/Target.svelte: 693 lines of code warpgate-web/src/admin/config/targets/Target.svelte
Large Files · warpgate-web/src/admin/config/users/User.svelte: 587 lines of code warpgate-web/src/admin/config/users/User.svelte
Large Files · warpgate-web/src/gateway/WebSsh.svelte: 523 lines of code warpgate-web/src/gateway/WebSsh.svelte
Large Files · warpgate-web/src/common/ConnectionInstructions.svelte: 505 lines of code warpgate-web/src/common/ConnectionInstructions.svelte
Large Files · warpgate-web/src/admin/config/users/CredentialEditor.svelte: 490 lines of code warpgate-web/src/admin/config/users/CredentialEditor.svelte
Large Files · warpgate-web/src/gateway/TicketRequests.svelte: 419 lines of code warpgate-web/src/gateway/TicketRequests.svelte
Large Files · warpgate-web/src/gateway/Login.svelte: 406 lines of code warpgate-web/src/gateway/Login.svelte
Large Files · warpgate-web/src/gateway/TargetList.svelte: 406 lines of code warpgate-web/src/gateway/TargetList.svelte
Exception handling · Swallowed exception (caught, then discarded) warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte
Exception handling · Swallowed exception (caught, then discarded) warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte
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: 134 findings
These 134 critical or serious findings were in the previous survey, on 13 October 2026, and are gone from this one. The first 100 are listed here.
Large Files · warpgate-web/src/admin/config/Parameters.svelte: 1154 lines of code warpgate-web/src/admin/config/Parameters.svelte
Large Files · warpgate-web/src/admin/log-viewer/LogViewer.svelte: 1060 lines of code warpgate-web/src/admin/log-viewer/LogViewer.svelte
Large Files · warpgate-web/src/admin/config/targets/Target.svelte: 652 lines of code warpgate-web/src/admin/config/targets/Target.svelte
Large Files · warpgate-web/src/admin/config/users/User.svelte: 568 lines of code warpgate-web/src/admin/config/users/User.svelte
Large Files · warpgate-web/src/gateway/WebSsh.svelte: 497 lines of code warpgate-web/src/gateway/WebSsh.svelte
Large Files · warpgate-web/src/common/ConnectionInstructions.svelte: 495 lines of code warpgate-web/src/common/ConnectionInstructions.svelte
Large Files · warpgate-web/src/admin/config/users/CredentialEditor.svelte: 480 lines of code warpgate-web/src/admin/config/users/CredentialEditor.svelte
Large Files · warpgate-web/src/gateway/TicketRequests.svelte: 413 lines of code warpgate-web/src/gateway/TicketRequests.svelte
Dead Code · Dead file (~372 LoC) REDACTED
Dead Code · Dead file (~321 LoC) warpgate-web/src/admin/config/users/User.svelte
Dead Code · Dead file (~309 LoC) warpgate-web/src/gateway/WebSsh.svelte
Dead Code · Dead file (~192 LoC) warpgate-web/src/gateway/TargetList.svelte
Dead Code · Dead file (~142 LoC) warpgate-web/src/admin/config/ldap/LdapServer.svelte
Dead Code · Dead file (~100 LoC) warpgate-web/src/admin/status/Sessions.svelte
Dead Code · Dead file (~97 LoC) warpgate-web/src/admin/config/secret-backends/SecretBackends.svelte
Dead Code · Dead file (~97 LoC) warpgate-web/src/admin/status/Session.svelte
Dead Code · Dead file (~95 LoC) warpgate-web/src/admin/config/SSHKeys.svelte
Dead Code · Dead file (~95 LoC) warpgate-web/src/gateway/lib/ReconnectingWebSocket.svelte.ts
Dead Code · Dead file (~91 LoC) warpgate-web/src/admin/config/secret-backends/SecretBackendModal.svelte
Dead Code · Dead file (~91 LoC) warpgate-web/src/admin/config/targets/Targets.svelte
Dead Code · Dead file (~90 LoC) warpgate-web/src/admin/config/ldap/CreateLdapServer.svelte
Dead Code · Dead file (~89 LoC) warpgate-web/src/admin/config/target-groups/TargetGroup.svelte
Dead Code · Dead file (~88 LoC) warpgate-web/src/admin/config/Config.svelte
Dead Code · Dead file (~83 LoC) warpgate-web/src/admin/config/targets/ssh/Options.svelte
Dead Code · Dead file (~83 LoC) warpgate-web/src/common/AsyncButton.svelte
Dead Code · Dead file (~81 LoC) warpgate-web/src/admin/status/KubernetesRecording.svelte
Dead Code · Dead file (~80 LoC) warpgate-web/src/admin/status/LoginProtection.svelte
Dead Code · Dead file (~77 LoC) warpgate-web/src/admin/config/AccessRole.svelte
Dead Code · Dead file (~75 LoC) warpgate-web/src/admin/config/ldap/LdapUserBrowser.svelte
Dead Code · Dead file (~73 LoC) warpgate-web/src/admin/config/targets/http/HeadersEditor.svelte
Dead Code · Dead file (~73 LoC) warpgate-web/src/gateway/OutOfBandAuth.svelte
Dead Code · Dead file (~71 LoC) warpgate-web/src/admin/config/Tickets.svelte
Dead Code · Dead file (~69 LoC) warpgate-web/src/common/approvalRequests.ts
Dead Code · Dead file (~68 LoC) warpgate-web/src/gateway/lib/certificateStore.ts
Dead Code · Dead file (~66 LoC) warpgate-web/src/gateway/CreateApiTokenModal.svelte
Dead Code · Dead file (~63 LoC) warpgate-web/src/admin/AnalyticsConsentModal.svelte
Dead Code · Dead file (~62 LoC) warpgate-web/src/admin/config/CreateTicket.svelte
Dead Code · Dead file (~60 LoC) warpgate-web/src/admin/PublicKeyCredentialModal.svelte
Dead Code · Dead file (~59 LoC) warpgate-web/src/theme/index.ts
Dead Code · Dead file (~56 LoC) warpgate-web/src/common/RequestsButton.svelte
Dead Code · Dead file (~52 LoC) warpgate-web/src/admin/CreatePasswordModal.svelte
Dead Code · Dead file (~51 LoC) warpgate-web/src/admin/player/latestWins.ts
Dead Code · Dead file (~50 LoC) warpgate-web/src/admin/config/Policies.svelte
Dead Code · Dead file (~50 LoC) warpgate-web/src/admin/config/users/Users.svelte
Dead Code · Dead file (~50 LoC) warpgate-web/src/admin/lib/LogoInput.svelte
Dead Code · Dead file (~50 LoC) warpgate-web/src/admin/player/PlayerToolbar.svelte
Dead Code · Dead file (~50 LoC) warpgate-web/src/gateway/ApiTokenManager.svelte
Dead Code · Dead file (~48 LoC) warpgate-web/src/admin/config/targets/ChooseTargetKind.svelte
Dead Code · Dead file (~46 LoC) warpgate-web/src/admin/config/ldap/LdapConnectionFields.svelte
Dead Code · Dead file (~45 LoC) warpgate-web/src/admin/config/ClientKeyModal.svelte
Dead Code · Dead file (~43 LoC) warpgate-web/src/common/DurationInput.svelte
Dead Code · Dead file (~42 LoC) warpgate-web/src/common/Brand.svelte
Dead Code · Dead file (~39 LoC) warpgate-web/src/common/CopyButton.svelte
Dead Code · Dead file (~39 LoC) warpgate-web/src/common/Pagination.svelte
Dead Code · Dead file (~39 LoC) warpgate-web/src/common/WebClientStatus.svelte
Dead Code · Dead file (~38 LoC) warpgate-web/src/admin/SsoCredentialModal.svelte
Dead Code · Dead file (~38 LoC) warpgate-web/src/admin/config/targets/ssh/KeyCheckerResult.svelte
Dead Code · Dead file (~38 LoC) warpgate-web/src/common/NavListItem.svelte
Dead Code · Dead file (~37 LoC) warpgate-web/src/admin/config/ldap/LdapServers.svelte
Dead Code · Dead file (~37 LoC) warpgate-web/src/admin/config/target-groups/CreateTargetGroup.svelte
Dead Code · Dead file (~36 LoC) warpgate-web/src/admin/config/GenerateClientKeyModal.svelte
Dead Code · Dead file (~36 LoC) warpgate-web/src/admin/status/Recording.svelte
Dead Code · Dead file (~36 LoC) warpgate-web/src/common/VirtualList.svelte
Dead Code · Dead file (~35 LoC) warpgate-web/src/admin/config/AccessRoles.svelte
Dead Code · Dead file (~35 LoC) warpgate-web/src/admin/config/ldap/common.ts
Dead Code · Dead file (~33 LoC) warpgate-web/src/admin/Log.svelte
Dead Code · Dead file (~33 LoC) warpgate-web/src/admin/config/users/AllowedIpRangesEditor.svelte
Dead Code · Dead file (~32 LoC) warpgate-web/src/admin/config/AdminRolePermissionsBadge.svelte
Dead Code · Dead file (~32 LoC) warpgate-web/src/gateway/lib/shellEscape.ts
Dead Code · Dead file (~31 LoC) warpgate-web/src/common/InfoBox.svelte
Dead Code · Dead file (~31 LoC) warpgate-web/src/gateway/lib/webClientSession.ts
Dead Code · Dead file (~28 LoC) warpgate-web/src/admin/config/target-groups/TargetGroups.svelte
Dead Code · Dead file (~27 LoC) warpgate-web/src/common/ticketRequestStatus.ts
Dead Code · Dead file (~26 LoC) warpgate-web/src/admin/AnalyticsPreview.svelte
Dead Code · Dead file (~26 LoC) warpgate-web/src/common/groups.ts
Dead Code · Dead file (~26 LoC) warpgate-web/src/common/reauth.ts
Dead Code · Dead file (~25 LoC) warpgate-web/src/admin/config/CreateAdminRole.svelte
Dead Code · Dead file (~25 LoC) warpgate-web/src/admin/config/SidebarNavContainer.svelte
Dead Code · Dead file (~25 LoC) warpgate-web/src/common/AuthBar.svelte
Dead Code · Dead file (~23 LoC) warpgate-web/src/admin/config/CreateRole.svelte
Dead Code · Dead file (~23 LoC) warpgate-web/src/admin/config/CreateUser.svelte
Dead Code · Dead file (~23 LoC) warpgate-web/src/gateway/Root.svelte
Dead Code · Dead file (~22 LoC) warpgate-web/src/admin/config/AdminRoles.svelte
Dead Code · Dead file (~22 LoC) warpgate-web/src/admin/status/Status.svelte
Dead Code · Dead file (~22 LoC) warpgate-web/src/gateway/lib/webSessions.ts
Dead Code · Dead file (~21 LoC) warpgate-web/src/common/ThemeSwitcher.svelte
Dead Code · Dead file (~20 LoC) warpgate-web/src/admin/config/targets/vnc/Options.svelte
Dead Code · Dead file (~20 LoC) warpgate-web/src/gateway/MfaSetup.svelte
Rebuild cost: about €95,000 · Estimate
Cost to rebuild
€32,000 to €160,000, for 528 to 1,674 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Low, 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.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 86,279 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
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Raises the score by about 8 points · Medium effort · Dead Code
2
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 2 points · Low effort · ADR Quality
3
Resolve the 2 Dead code finding(s) in Explicit Debt — start with CryptoUtils.cs (2).
Raises the score by about 2 points · Low effort · Explicit Debt
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 €95,000 to build again, about 0.7 person-years of work. Its weakest lens is Code Health, at 49 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
830 modules, with 1495 dependencies between them. 16 loops run through 69 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 790 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.
ironrdp_dvc uses warpgate_database_protocols.io.encode, so a change to warpgate_database_protocols.io.encode can break ironrdp_dvc, while a change to ironrdp_dvc can't break warpgate_database_protocols.io.encode.
Position
Below the diagonal: ironrdp_dvc uses a module listed above it, which is the healthy direction.
ironrdp_egfx.pdu.common uses warpgate_database_protocols.io.decode, so a change to warpgate_database_protocols.io.decode can break ironrdp_egfx.pdu.common, while a change to ironrdp_egfx.pdu.common can't break warpgate_database_protocols.io.decode.
Position
Below the diagonal: ironrdp_egfx.pdu.common uses a module listed above it, which is the healthy direction.
ironrdp_egfx.pdu.common uses warpgate_database_protocols.io.encode, so a change to warpgate_database_protocols.io.encode can break ironrdp_egfx.pdu.common, while a change to ironrdp_egfx.pdu.common can't break warpgate_database_protocols.io.encode.
Position
Below the diagonal: ironrdp_egfx.pdu.common uses a module listed above it, which is the healthy direction.
ironrdp_pdu.basic_output.fast_path uses warpgate_database_protocols.io.decode, so a change to warpgate_database_protocols.io.decode can break ironrdp_pdu.basic_output.fast_path, while a change to ironrdp_pdu.basic_output.fast_path can't break warpgate_database_protocols.io.decode.
Position
Below the diagonal: ironrdp_pdu.basic_output.fast_path uses a module listed above it, which is the healthy direction.
ironrdp_pdu.basic_output.fast_path uses warpgate_database_protocols.io.encode, so a change to warpgate_database_protocols.io.encode can break ironrdp_pdu.basic_output.fast_path, while a change to ironrdp_pdu.basic_output.fast_path can't break warpgate_database_protocols.io.encode.
Position
Below the diagonal: ironrdp_pdu.basic_output.fast_path uses a module listed above it, which is the healthy direction.
ironrdp_pdu.gcc uses warpgate_database_protocols.io.decode, so a change to warpgate_database_protocols.io.decode can break ironrdp_pdu.gcc, while a change to ironrdp_pdu.gcc can't break warpgate_database_protocols.io.decode.
Position
Below the diagonal: ironrdp_pdu.gcc uses a module listed above it, which is the healthy direction.
ironrdp_pdu.gcc uses warpgate_database_protocols.io.encode, so a change to warpgate_database_protocols.io.encode can break ironrdp_pdu.gcc, while a change to ironrdp_pdu.gcc can't break warpgate_database_protocols.io.encode.
Position
Below the diagonal: ironrdp_pdu.gcc uses a module listed above it, which is the healthy direction.
ironrdp_pdu.geometry uses warpgate_database_protocols.io.decode, so a change to warpgate_database_protocols.io.decode can break ironrdp_pdu.geometry, while a change to ironrdp_pdu.geometry can't break warpgate_database_protocols.io.decode.
Position
Below the diagonal: ironrdp_pdu.geometry uses a module listed above it, which is the healthy direction.
ironrdp_pdu.geometry uses warpgate_database_protocols.io.encode, so a change to warpgate_database_protocols.io.encode can break ironrdp_pdu.geometry, while a change to ironrdp_pdu.geometry can't break warpgate_database_protocols.io.encode.
Position
Below the diagonal: ironrdp_pdu.geometry uses a module listed above it, which is the healthy direction.
warpgate_common.auth.cred uses warpgate_common.config, so a change to warpgate_common.config can break warpgate_common.auth.cred, while a change to warpgate_common.auth.cred can't break warpgate_common.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
warpgate_core.recordings uses warpgate_common.state, so a change to warpgate_common.state can break warpgate_core.recordings, while a change to warpgate_core.recordings can't break warpgate_common.state.
Position
Below the diagonal: warpgate_core.recordings uses a module listed above it, which is the healthy direction.
warpgate_core.recordings uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_core.recordings, while a change to warpgate_core.recordings can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_core.recordings uses a module listed above it, which is the healthy direction.
warpgate_core.recordings uses warpgate_db_entities.AdminRole, so a change to warpgate_db_entities.AdminRole can break warpgate_core.recordings, while a change to warpgate_core.recordings can't break warpgate_db_entities.AdminRole.
Position
Below the diagonal: warpgate_core.recordings uses a module listed above it, which is the healthy direction.
warpgate_database_protocols.mysql.protocol.text.query uses warpgate_database_protocols.io.decode, so a change to warpgate_database_protocols.io.decode can break warpgate_database_protocols.mysql.protocol.text.query, while a change to warpgate_database_protocols.mysql.protocol.text.query can't break warpgate_database_protocols.io.decode.
Position
Below the diagonal: warpgate_database_protocols.mysql.protocol.text.query uses a module listed above it, which is the healthy direction.
warpgate_database_protocols.mysql.protocol.text.query uses warpgate_database_protocols.io.encode, so a change to warpgate_database_protocols.io.encode can break warpgate_database_protocols.mysql.protocol.text.query, while a change to warpgate_database_protocols.mysql.protocol.text.query can't break warpgate_database_protocols.io.encode.
Position
Below the diagonal: warpgate_database_protocols.mysql.protocol.text.query uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in warpgate_database_protocols.mysql.protocol.text.query uses a type in warpgate_database_protocols.mysql.protocol.capabilities.
warpgate_database_protocols.mysql.protocol.text.query uses warpgate_database_protocols.mysql.protocol.capabilities, so a change to warpgate_database_protocols.mysql.protocol.capabilities can break warpgate_database_protocols.mysql.protocol.text.query, while a change to warpgate_database_protocols.mysql.protocol.text.query can't break warpgate_database_protocols.mysql.protocol.capabilities.
Position
Below the diagonal: warpgate_database_protocols.mysql.protocol.text.query uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in ironrdp_egfx.pdu.cmd uses a type in warpgate_database_protocols.io.decode. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ironrdp_egfx.pdu.cmd uses warpgate_database_protocols.io.decode, so a change to warpgate_database_protocols.io.decode can break ironrdp_egfx.pdu.cmd, while a change to ironrdp_egfx.pdu.cmd can't break warpgate_database_protocols.io.decode.
Position
Below the diagonal: ironrdp_egfx.pdu.cmd uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in ironrdp_egfx.pdu.cmd uses a type in warpgate_database_protocols.io.encode. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ironrdp_egfx.pdu.cmd uses warpgate_database_protocols.io.encode, so a change to warpgate_database_protocols.io.encode can break ironrdp_egfx.pdu.cmd, while a change to ironrdp_egfx.pdu.cmd can't break warpgate_database_protocols.io.encode.
Position
Below the diagonal: ironrdp_egfx.pdu.cmd uses a module listed above it, which is the healthy direction.
ironrdp_egfx.pdu.cmd uses ironrdp_dvc, so a change to ironrdp_dvc can break ironrdp_egfx.pdu.cmd, while a change to ironrdp_egfx.pdu.cmd can't break ironrdp_dvc.
Position
Below the diagonal: ironrdp_egfx.pdu.cmd uses a module listed above it, which is the healthy direction.
ironrdp_egfx.pdu.cmd uses ironrdp_egfx.pdu.common, so a change to ironrdp_egfx.pdu.common can break ironrdp_egfx.pdu.cmd, while a change to ironrdp_egfx.pdu.cmd can't break ironrdp_egfx.pdu.common.
Position
Below the diagonal: ironrdp_egfx.pdu.cmd uses a module listed above it, which is the healthy direction.
ironrdp_egfx.pdu.cmd uses ironrdp_pdu.geometry, so a change to ironrdp_pdu.geometry can break ironrdp_egfx.pdu.cmd, while a change to ironrdp_egfx.pdu.cmd can't break ironrdp_pdu.geometry.
Position
Below the diagonal: ironrdp_egfx.pdu.cmd uses a module listed above it, which is the healthy direction.
warpgate_core.recordings.desktop uses warpgate_core.protocols.desktop, so a change to warpgate_core.protocols.desktop can break warpgate_core.recordings.desktop, while a change to warpgate_core.recordings.desktop can't break warpgate_core.protocols.desktop.
Position
Below the diagonal: warpgate_core.recordings.desktop uses a module listed above it, which is the healthy direction.
warpgate_core.recordings.desktop uses warpgate_core.recordings, so a change to warpgate_core.recordings can break warpgate_core.recordings.desktop, while a change to warpgate_core.recordings.desktop can't break warpgate_core.recordings.
Position
Below the diagonal: warpgate_core.recordings.desktop uses a module listed above it, which is the healthy direction.
ironrdp_egfx.client uses ironrdp_dvc, so a change to ironrdp_dvc can break ironrdp_egfx.client, while a change to ironrdp_egfx.client can't break ironrdp_dvc.
Position
Below the diagonal: ironrdp_egfx.client uses a module listed above it, which is the healthy direction.
ironrdp_egfx.client uses ironrdp_egfx.pdu.common, so a change to ironrdp_egfx.pdu.common can break ironrdp_egfx.client, while a change to ironrdp_egfx.client can't break ironrdp_egfx.pdu.common.
Position
Below the diagonal: ironrdp_egfx.client uses a module listed above it, which is the healthy direction.
ironrdp_egfx.client uses ironrdp_pdu.geometry, so a change to ironrdp_pdu.geometry can break ironrdp_egfx.client, while a change to ironrdp_egfx.client can't break ironrdp_pdu.geometry.
Position
Below the diagonal: ironrdp_egfx.client uses a module listed above it, which is the healthy direction.
ironrdp_egfx.client uses ironrdp_egfx.pdu.cmd, so a change to ironrdp_egfx.pdu.cmd can break ironrdp_egfx.client, while a change to ironrdp_egfx.client can't break ironrdp_egfx.pdu.cmd.
Position
Below the diagonal: ironrdp_egfx.client uses a module listed above it, which is the healthy direction.
sspi.auth_identity uses sspi.secret, so a change to sspi.secret can break sspi.auth_identity, while a change to sspi.auth_identity can't break sspi.secret.
Position
Below the diagonal: sspi.auth_identity uses a module listed above it, which is the healthy direction.
sspi.auth_identity uses ironrdp_connector, so a change to ironrdp_connector can break sspi.auth_identity, while a change to sspi.auth_identity can't break ironrdp_connector.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
warpgate_common.config.target uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_common.config.target, while a change to warpgate_common.config.target can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_common.config.target uses a module listed above it, which is the healthy direction.
warpgate_common.config.target uses warpgate_db_entities.AdminRole, so a change to warpgate_db_entities.AdminRole can break warpgate_common.config.target, while a change to warpgate_common.config.target can't break warpgate_db_entities.AdminRole.
Position
Below the diagonal: warpgate_common.config.target uses a module listed above it, which is the healthy direction.
warpgate_common.config.target uses sspi.secret, so a change to sspi.secret can break warpgate_common.config.target, while a change to warpgate_common.config.target can't break sspi.secret.
Position
Below the diagonal: warpgate_common.config.target uses a module listed above it, which is the healthy direction.
sspi uses ironrdp_pdu.basic_output.fast_path, so a change to ironrdp_pdu.basic_output.fast_path can break sspi, while a change to sspi can't break ironrdp_pdu.basic_output.fast_path.
Position
Below the diagonal: sspi uses a module listed above it, which is the healthy direction.
warpgate_common.config uses warpgate_common.state, so a change to warpgate_common.state can break warpgate_common.config, while a change to warpgate_common.config can't break warpgate_common.state.
Position
Below the diagonal: warpgate_common.config uses a module listed above it, which is the healthy direction.
warpgate_common.config uses warpgate_common.types.listen_endpoint, so a change to warpgate_common.types.listen_endpoint can break warpgate_common.config, while a change to warpgate_common.config can't break warpgate_common.types.listen_endpoint.
Position
Below the diagonal: warpgate_common.config uses a module listed above it, which is the healthy direction.
warpgate_common.config uses warpgate_db_entities.AdminRole, so a change to warpgate_db_entities.AdminRole can break warpgate_common.config, while a change to warpgate_common.config can't break warpgate_db_entities.AdminRole.
Position
Below the diagonal: warpgate_common.config uses a module listed above it, which is the healthy direction.
warpgate_common.config uses warpgate_tls.cert, so a change to warpgate_tls.cert can break warpgate_common.config, while a change to warpgate_common.config can't break warpgate_tls.cert.
Position
Below the diagonal: warpgate_common.config uses a module listed above it, which is the healthy direction.
warpgate_common.config uses warpgate_common.auth.cred, so a change to warpgate_common.auth.cred can break warpgate_common.config, while a change to warpgate_common.config can't break warpgate_common.auth.cred.
Position
Below the diagonal: warpgate_common.config uses a module listed above it, which is the healthy direction.
warpgate_common.config uses sspi.secret, so a change to sspi.secret can break warpgate_common.config, while a change to warpgate_common.config can't break sspi.secret.
Position
Below the diagonal: warpgate_common.config uses a module listed above it, which is the healthy direction.
warpgate_common.config uses warpgate_common.config.target, so a change to warpgate_common.config.target can break warpgate_common.config, while a change to warpgate_common.config can't break warpgate_common.config.target.
Position
Below the diagonal: warpgate_common.config uses a module listed above it, which is the healthy direction.
ironrdp_pdu.rdp.server_license uses warpgate_database_protocols.io.decode, so a change to warpgate_database_protocols.io.decode can break ironrdp_pdu.rdp.server_license, while a change to ironrdp_pdu.rdp.server_license can't break warpgate_database_protocols.io.decode.
Position
Below the diagonal: ironrdp_pdu.rdp.server_license uses a module listed above it, which is the healthy direction.
ironrdp_pdu.rdp.server_license uses warpgate_database_protocols.io.encode, so a change to warpgate_database_protocols.io.encode can break ironrdp_pdu.rdp.server_license, while a change to ironrdp_pdu.rdp.server_license can't break warpgate_database_protocols.io.encode.
Position
Below the diagonal: ironrdp_pdu.rdp.server_license uses a module listed above it, which is the healthy direction.
ironrdp_pdu.rdp.server_license uses sspi, so a change to sspi can break ironrdp_pdu.rdp.server_license, while a change to ironrdp_pdu.rdp.server_license can't break sspi.
Position
Below the diagonal: ironrdp_pdu.rdp.server_license uses a module listed above it, which is the healthy direction.
sspi.kerberos uses ironrdp_pdu.basic_output.fast_path, so a change to ironrdp_pdu.basic_output.fast_path can break sspi.kerberos, while a change to sspi.kerberos can't break ironrdp_pdu.basic_output.fast_path.
Position
Below the diagonal: sspi.kerberos uses a module listed above it, which is the healthy direction.
sspi.kerberos uses sspi.auth_identity, so a change to sspi.auth_identity can break sspi.kerberos, while a change to sspi.kerberos can't break sspi.auth_identity.
Position
Below the diagonal: sspi.kerberos uses a module listed above it, which is the healthy direction.
sspi.ntlm uses ironrdp_pdu.basic_output.fast_path, so a change to ironrdp_pdu.basic_output.fast_path can break sspi.ntlm, while a change to sspi.ntlm can't break ironrdp_pdu.basic_output.fast_path.
Position
Below the diagonal: sspi.ntlm uses a module listed above it, which is the healthy direction.
warpgate_common.auth.state uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_common.auth.state, while a change to warpgate_common.auth.state can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_common.auth.state uses a module listed above it, which is the healthy direction.
warpgate_common.auth.state uses warpgate_common.auth.cred, so a change to warpgate_common.auth.cred can break warpgate_common.auth.state, while a change to warpgate_common.auth.state can't break warpgate_common.auth.cred.
Position
Below the diagonal: warpgate_common.auth.state uses a module listed above it, which is the healthy direction.
warpgate_common.auth.state uses warpgate_common.config, so a change to warpgate_common.config can break warpgate_common.auth.state, while a change to warpgate_common.auth.state can't break warpgate_common.config.
Position
Below the diagonal: warpgate_common.auth.state uses a module listed above it, which is the healthy direction.
ironrdp_server.server uses ironrdp_dvc, so a change to ironrdp_dvc can break ironrdp_server.server, while a change to ironrdp_server.server can't break ironrdp_dvc.
Position
Below the diagonal: ironrdp_server.server uses a module listed above it, which is the healthy direction.
ironrdp_server.server uses ironrdp_connector, so a change to ironrdp_connector can break ironrdp_server.server, while a change to ironrdp_server.server can't break ironrdp_connector.
Position
Below the diagonal: ironrdp_server.server uses a module listed above it, which is the healthy direction.
warpgate_core.config_providers uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_core.config_providers, while a change to warpgate_core.config_providers can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_core.config_providers uses a module listed above it, which is the healthy direction.
warpgate_core.config_providers uses warpgate_common.auth.cred, so a change to warpgate_common.auth.cred can break warpgate_core.config_providers, while a change to warpgate_core.config_providers can't break warpgate_common.auth.cred.
Position
Below the diagonal: warpgate_core.config_providers uses a module listed above it, which is the healthy direction.
warpgate_core.config_providers uses sspi.secret, so a change to sspi.secret can break warpgate_core.config_providers, while a change to warpgate_core.config_providers can't break sspi.secret.
Position
Below the diagonal: warpgate_core.config_providers uses a module listed above it, which is the healthy direction.
warpgate_core.config_providers uses warpgate_common.config.target, so a change to warpgate_common.config.target can break warpgate_core.config_providers, while a change to warpgate_core.config_providers can't break warpgate_common.config.target.
Position
Below the diagonal: warpgate_core.config_providers uses a module listed above it, which is the healthy direction.
warpgate_core.config_providers uses warpgate_common.auth.state, so a change to warpgate_common.auth.state can break warpgate_core.config_providers, while a change to warpgate_core.config_providers can't break warpgate_common.auth.state.
Position
Below the diagonal: warpgate_core.config_providers uses a module listed above it, which is the healthy direction.
warpgate_protocol_rdp.client uses warpgate_core.protocols.desktop, so a change to warpgate_core.protocols.desktop can break warpgate_protocol_rdp.client, while a change to warpgate_protocol_rdp.client can't break warpgate_core.protocols.desktop.
Position
Below the diagonal: warpgate_protocol_rdp.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_rdp.client uses ironrdp_pdu.geometry, so a change to ironrdp_pdu.geometry can break warpgate_protocol_rdp.client, while a change to warpgate_protocol_rdp.client can't break ironrdp_pdu.geometry.
Position
Below the diagonal: warpgate_protocol_rdp.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_rdp.client uses ironrdp_egfx.pdu.cmd, so a change to ironrdp_egfx.pdu.cmd can break warpgate_protocol_rdp.client, while a change to warpgate_protocol_rdp.client can't break ironrdp_egfx.pdu.cmd.
Position
Below the diagonal: warpgate_protocol_rdp.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_rdp.client uses ironrdp_egfx.client, so a change to ironrdp_egfx.client can break warpgate_protocol_rdp.client, while a change to warpgate_protocol_rdp.client can't break ironrdp_egfx.client.
Position
Below the diagonal: warpgate_protocol_rdp.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_rdp.client uses warpgate_common.config.target, so a change to warpgate_common.config.target can break warpgate_protocol_rdp.client, while a change to warpgate_protocol_rdp.client can't break warpgate_common.config.target.
Position
Below the diagonal: warpgate_protocol_rdp.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_rdp.client uses ironrdp_connector, so a change to ironrdp_connector can break warpgate_protocol_rdp.client, while a change to warpgate_protocol_rdp.client can't break ironrdp_connector.
Position
Below the diagonal: warpgate_protocol_rdp.client uses a module listed above it, which is the healthy direction.
warpgate_core.protocols.handle uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_core.protocols.handle, while a change to warpgate_core.protocols.handle can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_core.protocols.handle uses a module listed above it, which is the healthy direction.
warpgate_core.protocols.handle uses warpgate_common.config.target, so a change to warpgate_common.config.target can break warpgate_core.protocols.handle, while a change to warpgate_core.protocols.handle can't break warpgate_common.config.target.
Position
Below the diagonal: warpgate_core.protocols.handle uses a module listed above it, which is the healthy direction.
warpgate_core.protocols.handle uses ironrdp_connector, so a change to ironrdp_connector can break warpgate_core.protocols.handle, while a change to warpgate_core.protocols.handle can't break ironrdp_connector.
Position
Below the diagonal: warpgate_core.protocols.handle uses a module listed above it, which is the healthy direction.
warpgate_core.protocols.handle uses warpgate_common.auth.state, so a change to warpgate_common.auth.state can break warpgate_core.protocols.handle, while a change to warpgate_core.protocols.handle can't break warpgate_common.auth.state.
Position
Below the diagonal: warpgate_core.protocols.handle uses a module listed above it, which is the healthy direction.
warpgate_core.protocols.handle uses warpgate_core.config_providers, so a change to warpgate_core.config_providers can break warpgate_core.protocols.handle, while a change to warpgate_core.protocols.handle can't break warpgate_core.config_providers.
Position
Below the diagonal: warpgate_core.protocols.handle uses a module listed above it, which is the healthy direction.
warpgate_core.services uses warpgate_common.state, so a change to warpgate_common.state can break warpgate_core.services, while a change to warpgate_core.services can't break warpgate_common.state.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_core.services uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_core.services, while a change to warpgate_core.services can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_core.services uses warpgate_db_entities.AdminRole, so a change to warpgate_db_entities.AdminRole can break warpgate_core.services, while a change to warpgate_core.services can't break warpgate_db_entities.AdminRole.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_core.services uses warpgate_core.recordings, so a change to warpgate_core.recordings can break warpgate_core.services, while a change to warpgate_core.services can't break warpgate_core.recordings.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_core.services uses sspi.secret, so a change to sspi.secret can break warpgate_core.services, while a change to warpgate_core.services can't break sspi.secret.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_core.services uses warpgate_common.config, so a change to warpgate_common.config can break warpgate_core.services, while a change to warpgate_core.services can't break warpgate_common.config.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_core.services uses ironrdp_connector, so a change to ironrdp_connector can break warpgate_core.services, while a change to warpgate_core.services can't break ironrdp_connector.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_core.services uses warpgate_common.auth.state, so a change to warpgate_common.auth.state can break warpgate_core.services, while a change to warpgate_core.services can't break warpgate_common.auth.state.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_core.services uses warpgate_core.config_providers, so a change to warpgate_core.config_providers can break warpgate_core.services, while a change to warpgate_core.services can't break warpgate_core.config_providers.
Position
Below the diagonal: warpgate_core.services uses a module listed above it, which is the healthy direction.
warpgate_common_http.auth uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_common_http.auth, while a change to warpgate_common_http.auth can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_common_http.auth uses a module listed above it, which is the healthy direction.
warpgate_common_http.auth uses warpgate_common.config.target, so a change to warpgate_common.config.target can break warpgate_common_http.auth, while a change to warpgate_common_http.auth can't break warpgate_common.config.target.
Position
Below the diagonal: warpgate_common_http.auth uses a module listed above it, which is the healthy direction.
warpgate_common_http.auth uses warpgate_common.auth.state, so a change to warpgate_common.auth.state can break warpgate_common_http.auth, while a change to warpgate_common_http.auth can't break warpgate_common.auth.state.
Position
Below the diagonal: warpgate_common_http.auth uses a module listed above it, which is the healthy direction.
warpgate_common_http.auth uses warpgate_core.config_providers, so a change to warpgate_core.config_providers can break warpgate_common_http.auth, while a change to warpgate_common_http.auth can't break warpgate_core.config_providers.
Position
Below the diagonal: warpgate_common_http.auth uses a module listed above it, which is the healthy direction.
warpgate_common_http.auth uses warpgate_core.services, so a change to warpgate_core.services can break warpgate_common_http.auth, while a change to warpgate_common_http.auth can't break warpgate_core.services.
Position
Below the diagonal: warpgate_common_http.auth uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.client uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_protocol_ssh.client, while a change to warpgate_protocol_ssh.client can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_protocol_ssh.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.client uses warpgate_common.config.target, so a change to warpgate_common.config.target can break warpgate_protocol_ssh.client, while a change to warpgate_protocol_ssh.client can't break warpgate_common.config.target.
Position
Below the diagonal: warpgate_protocol_ssh.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.client uses ironrdp_connector, so a change to ironrdp_connector can break warpgate_protocol_ssh.client, while a change to warpgate_protocol_ssh.client can't break ironrdp_connector.
Position
Below the diagonal: warpgate_protocol_ssh.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.client uses warpgate_common.auth.state, so a change to warpgate_common.auth.state can break warpgate_protocol_ssh.client, while a change to warpgate_protocol_ssh.client can't break warpgate_common.auth.state.
Position
Below the diagonal: warpgate_protocol_ssh.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.client uses warpgate_core.protocols.handle, so a change to warpgate_core.protocols.handle can break warpgate_protocol_ssh.client, while a change to warpgate_protocol_ssh.client can't break warpgate_core.protocols.handle.
Position
Below the diagonal: warpgate_protocol_ssh.client uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.client uses warpgate_core.services, so a change to warpgate_core.services can break warpgate_protocol_ssh.client, while a change to warpgate_protocol_ssh.client can't break warpgate_core.services.
Position
Below the diagonal: warpgate_protocol_ssh.client uses a module listed above it, which is the healthy direction.
warpgate_admin.api.admin_scheme uses warpgate_common.config.target, so a change to warpgate_common.config.target can break warpgate_admin.api.admin_scheme, while a change to warpgate_admin.api.admin_scheme can't break warpgate_common.config.target.
Position
Below the diagonal: warpgate_admin.api.admin_scheme uses a module listed above it, which is the healthy direction.
warpgate_admin.api.admin_scheme uses warpgate_common.config, so a change to warpgate_common.config can break warpgate_admin.api.admin_scheme, while a change to warpgate_admin.api.admin_scheme can't break warpgate_common.config.
Position
Below the diagonal: warpgate_admin.api.admin_scheme uses a module listed above it, which is the healthy direction.
warpgate_admin.api.admin_scheme uses warpgate_common_http.auth, so a change to warpgate_common_http.auth can break warpgate_admin.api.admin_scheme, while a change to warpgate_admin.api.admin_scheme can't break warpgate_common_http.auth.
Position
Below the diagonal: warpgate_admin.api.admin_scheme uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses warpgate_common.types.aliases, so a change to warpgate_common.types.aliases can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break warpgate_common.types.aliases.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses picky.key, so a change to picky.key can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break picky.key.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses warpgate_common.auth.cred, so a change to warpgate_common.auth.cred can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break warpgate_common.auth.cred.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses sspi.secret, so a change to sspi.secret can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break sspi.secret.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses sspi, so a change to sspi can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break sspi.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses warpgate_common.auth.state, so a change to warpgate_common.auth.state can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break warpgate_common.auth.state.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses warpgate_core.config_providers, so a change to warpgate_core.config_providers can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break warpgate_core.config_providers.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses warpgate_core.protocols.handle, so a change to warpgate_core.protocols.handle can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break warpgate_core.protocols.handle.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses warpgate_core.services, so a change to warpgate_core.services can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break warpgate_core.services.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
warpgate_protocol_ssh.server.session uses warpgate_protocol_ssh.client, so a change to warpgate_protocol_ssh.client can break warpgate_protocol_ssh.server.session, while a change to warpgate_protocol_ssh.server.session can't break warpgate_protocol_ssh.client.
Position
Below the diagonal: warpgate_protocol_ssh.server.session uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 49% · Weak · gated by R7 ·
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
23
High / Critical
A02:2025 — Security Misconfiguration
23
High / Critical
A05:2025 — Injection
15
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
First, remove the extensive dead code to eliminate maintenance overhead and reduce build times. Next, implement structured logging to replace interpolated messages and fix swallowed exceptions to ensure proper error visibility. Finally, address the missing architectural decision record and resolve the identified dead code warnings in CryptoUtils to complete the cleanup.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
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 `?`).
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 31
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 — 358
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 — 109
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
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. 88 of 88 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 — 88 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, 430 of 498 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. No coverage collector was found in your CI either, so there is no existing report to hand us. You can widen what we reach: optional: add a coverage collector to your test run and commit (or publish) its Cobertura/OpenCover/lcov output anywhere in the repo, or make the suite runnable in-image, and real coverage will be measured.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 4 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 85 test source file(s) (.py, .rs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
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 SCORED: this repository's production source spans .rs, and the rust executor ran against the .rs half and never executed — so reliability was not measured for the repository as a whole. The .NET suite did build and re-run, and came back with 0 flaky across 1 measured tier(s) (unit: measured (0 flaky)) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Cargo manifest, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 0 deducted marker(s) and the 0.2/KLoC density on this row were taken over this repository's .NET projects ALONE: .rs (82,475 lines, 97% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 12 task marker(s) (TODO/FIXME/HACK/XXX) across 10 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D23 Boundary Type-Coupling — 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. 4 bounded context(s) were resolved, but of the 2113 public type(s) this run scanned, none could be attributed to any of them — so no cross-boundary leak was reachable and an empty result was guaranteed regardless of the code. This happens when the scored code model is a non-.NET (sidecar) primary while the contexts were resolved from .NET project directories, which key on assembly name. Not scored: this is a gap in the analyzer, not a verdict about this repository. You can widen what we reach: declare this codebase's bounded contexts by module-path or namespace prefix so they resolve against the languages actually scanned. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — 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. `warpgate-web/src/common/desktopCanvas.ts` 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.
D41 Kernel & Syscall Confinement — 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. Helm/warpgate/templates/deployment.yaml:9, REDACTED:43 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
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 DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container docker-warpgate-1 exited (1); runtime evidence skipped.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
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.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
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. 111 further occurrence(s) are not listed individually; the score already reflects all 151.
X4 Structured logging — 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. 144 further occurrence(s) are not listed individually; the score already reflects all 184.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
22 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ServerSession::handle_remote_event at 47. A further 14 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 Collation::from_str at 225 — they are counted neither in the figure above nor in this dimension's score. 8 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: warpgate-database-protocols/src/mysql/collation.rs (Collation::from_str at 225), warpgate-protocol-rdp/src/client/input.rs (warpgate_protocol_rdp::client::input::keysym_to_scancode at 71), warpgate-database-protocols/src/mysql/protocol/text/column.rs (ColumnType::name at 38), warpgate-common/src/audit.rs (AuditEvent::emit at 23), warpgate-common/src/error.rs (WarpgateError::user_facing_reason at 22), and 3 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ServerSession::handle_remote_event (cyclomatic 47), warpgate_protocol_rdp::server::control_loop (cyclomatic 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.0 to about 7.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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.
+ 23 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with warpgate_protocol_rdp::server::control_loop (cognitive 78), ServerSession::handle_remote_event (cognitive 61). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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 Classes8.4 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
TooManyFields: Model · ×4warpgate-db-entities/src/Parameters.rs:207
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 MethodTooLong finding(s) in God Classes — start with session.rs (2), client.rs (2), audit.rs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 FunctionTooLong finding(s) in God Classes — start with mod.rs (3), handlers.rs (2), run.rs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 10 FileTooLong finding(s) in God Classes — start with mod.rs (3), session.rs, db.rs. — One of this dimension's main actionable groups (10 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
82 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 29 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with session.rs (2), m00058_analytics.rs (2), credentials.rs (2). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 8 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with session.rs (2), otp_credentials.rs, client.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with users.rs (3), ldap_servers.rs, stream.rs. — One of this dimension's main actionable groups (7 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling6.3 / 10Adequate✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
30 production modules (Cargo+npm+Python), 0 dependency cycle(s), 4 unstable depended-on module(s). Read from the build's own module declarations; 11 module(s) off the main sequence, with abstractness counted on 28 of the 30 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: warpgate-ca · ×9
Unstable project warpgate-admin (Cargo)
Unstable project warpgate-protocol-kubernetes
Unstable project warpgate-web-desktop
Unstable project warpgate-web-ssh
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 1 Unstable project warpgate-admin (Cargo) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project warpgate-protocol-kubernetes finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
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.
870 test methods: 854 unit, 16 integration, 0 BDD, 0 e2e. The Rust suite contributes 580 `#[test]` function(s) across 119 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 286 test function(s) across 74 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ 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.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4 tests. Measured on the C# suite only — at least 85 test source file(s) (.py, .rs) went unread, so its test quality is unmeasured and is not in these counts.
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.
38 outdated, 0 yanked direct Cargo dependencies. 140 of 144 direct crates were graded against crates.io (0 not published there, 4 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: aes · ×38
What to do
Improve Dependency Hygiene — currently 8.1/10. — 38 outdated, 0 yanked direct Cargo dependencies. 140 of 144 direct crates were graded against crates.io (0 not published there, 4 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
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.
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 154 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 6 direct `PackageReference`(s), and 148 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Cargo manifest, package.json and a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: warpgate-protocol-ssh/src/server/session.rs (29×47=1363); warpgate-protocol-rdp/src/client/mod.rs (23×24=552); warpgate-protocol-kubernetes/src/server/handlers.rs (13×25=325) Repeated repair below the complexity floor: warpgate-web/src/gateway/WebDesktop.svelte (5 of 9 changes were fixes); warpgate-core/src/recordings/desktop.rs (4 of 7 changes were fixes); warpgate-web-desktop/src/protocol.rs (3 of 5 changes were fixes)
Resolve the 21 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (3), client.rs (2), bridge.rs (2). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with WebDesktop.svelte, desktop.rs, protocol.rs. — One of this dimension's main actionable groups (3 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.0 / 10Strong✓ 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.
28 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is warpgate-tls/src/rustls_helpers.rs. Counted over 284 of the 519 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted debt markers + 2 dead symbols across 977 LoC in the .NET projects (0.2/KLoC) → score 9.7. Measured on the .NET source only: .rs (97% of production source) was not read, and carries at least 12 uncounted task marker(s) in 10 file(s).
Dead code: RsaToPkcs8String · ×2vendor/sspi/tools/aadjoin/AADJoin/Utils/CryptoUtils.cs:45
What to do
Resolve the 2 Dead code finding(s) in Explicit Debt — start with CryptoUtils.cs (2). — One of this dimension's main actionable groups (2 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. 5 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
15 finding(s): 0 critical, 12 high, 3 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 13 file(s) — `helm/warpgate/templates/configmap.yaml`, `REDACTED`, `helm/warpgate/templates/extra-manifests.yaml`, `helm/warpgate/templates/httproute.yaml`, `helm/warpgate/templates/ingress.yaml`, … (+8 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 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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.
Resolve the 6 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 10 Low IaC finding(s) in IaC & Container Security — start with REDACTED (10). — One of this dimension's main actionable groups (10 recommendation-level).
Resolve the 8 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 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.
7 of 284 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is warpgate-db-migrations/src/m00044_ticket_requests.rs. Counted over 284 of the 519 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 6 Boundary-crossing change coupling finding(s) in Change Coupling — start with parameters.rs, lib.rs, session.rs. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 2 Change coupling finding(s) in Change Coupling — start with handler.rs (2). — One of this dimension's main actionable groups (2 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.
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with UnitTests.csproj. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. 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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether an aggregate references another aggregate by identity rather than embedding it by object reference.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Other · Domain Modelling — Whether domain identifiers are strongly typed (a newtype wrapper) rather than raw primitives — consistency once an idiom exists.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model7.9 / 10Strong✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`QoeMetrics` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside. — vendor/ironrdp-egfx/src/server.rs:261
What to do
Move the domain logic onto the entity (invariant-enforcing `&mut self` commands) instead of a foreign service.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
What to do
Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) — even for a small library, every public type is a stability contract.
Do you agree with this assessment?
P2 · Observability8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether 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.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
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.
Do you agree with this assessment?
R1 · Type Safety10.0 / 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.
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.
warpgate-web/src/gateway/WebDesktop.svelte:449 · warpgate-web/src/gateway/WebSsh.svelte:270 — 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. — warpgate-web/src/gateway/WebDesktop.svelte:449
warpgate-web/src/admin/config/AccessRoles.svelte:12 · warpgate-web/src/admin/config/users/Users.svelte:21 — 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. — warpgate-web/src/admin/config/AccessRoles.svelte:12
warpgate-web/src/admin/config/Parameters.svelte:82 · warpgate-web/src/admin/config/Policies.svelte:16 — the two spans are one implementation copied and then locally edited — 93 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. — warpgate-web/src/admin/config/Parameters.svelte:82
warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:140 · warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte:202 — 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. — warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:140
warpgate-web/src/admin/config/ldap/CreateLdapServer.svelte:48 · warpgate-web/src/admin/config/ldap/LdapServer.svelte:88 — 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. — warpgate-web/src/admin/config/ldap/CreateLdapServer.svelte:48
warpgate-web/src/admin/config/AccessRole.svelte:27 · warpgate-web/src/admin/config/AccessRole.svelte:43 — 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. — warpgate-web/src/admin/config/AccessRole.svelte:27
warpgate-web/src/admin/config/AccessRole.svelte:62 · warpgate-web/src/admin/config/AdminRole.svelte:127 · warpgate-web/src/admin/config/targets/Target.svelte:81 — 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. — warpgate-web/src/admin/config/AccessRole.svelte:62
warpgate-web/src/admin/config/AccessRoles.svelte:21 · warpgate-web/src/admin/config/target-groups/TargetGroups.svelte:24 · warpgate-web/src/admin/config/users/Users.svelte:30 — the 3 copies are spread across 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — warpgate-web/src/admin/config/AccessRoles.svelte:21
warpgate-web/src/gateway/WebDesktop.svelte:76 · warpgate-web/src/gateway/WebSsh.svelte:111 — 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. — warpgate-web/src/gateway/WebDesktop.svelte:76
REDACTED:203 · REDACTED:224 — 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. — REDACTED:203
warpgate-web/src/gateway/lib/certificateStore.ts:24 · warpgate-web/src/gateway/lib/certificateStore.ts:48 — 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. — warpgate-web/src/gateway/lib/certificateStore.ts:24
warpgate-web/src/admin/lib/api.ts:8 · warpgate-web/src/gateway/lib/api.ts:4 — 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. — warpgate-web/src/admin/lib/api.ts:8
warpgate-web/src/admin/status/Session.svelte:64 · warpgate-web/src/admin/status/Session.svelte:78 — 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. — warpgate-web/src/admin/status/Session.svelte:64
REDACTED:100 · REDACTED:126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:100
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 · 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.
onMessage has cyclomatic complexity 16 and cognitive complexity 11; 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. — warpgate-web/src/gateway/WebSsh.svelte:152
mfaEnforcedFactor has cyclomatic complexity 14 and cognitive complexity 14; 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. — warpgate-web/src/admin/config/users/AuthPolicyEditor.svelte:113
parseHumantimeDuration has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — warpgate-web/src/common/duration.ts:35
getEffectivePossibleCredentials has cyclomatic complexity 12 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:333
save has cyclomatic complexity 12 and cognitive complexity 11; 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. — warpgate-web/src/admin/config/Parameters.svelte:116
(anonymous) has cyclomatic complexity 12 and cognitive complexity 11; 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. — warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:121
updateActiveSectionFromScroll has cyclomatic complexity 11 and cognitive complexity 18; 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. — warpgate-web/src/admin/lib/SectionedForm.svelte:23
onWsMessage has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — warpgate-web/src/gateway/WebDesktop.svelte:138
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files7.3 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
warpgate-web/src/admin/config/Parameters.svelte has 1278 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/admin/config/Parameters.svelte:1
warpgate-web/src/admin/log-viewer/LogViewer.svelte has 1092 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/admin/log-viewer/LogViewer.svelte:1
warpgate-web/src/admin/config/targets/Target.svelte has 693 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/admin/config/targets/Target.svelte:1
warpgate-web/src/admin/config/users/User.svelte has 587 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/admin/config/users/User.svelte:1
warpgate-web/src/gateway/WebDesktop.svelte has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/gateway/WebDesktop.svelte:1
warpgate-web/src/gateway/WebSsh.svelte has 523 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/gateway/WebSsh.svelte:1
warpgate-web/src/common/ConnectionInstructions.svelte has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/common/ConnectionInstructions.svelte:1
warpgate-web/src/admin/config/users/CredentialEditor.svelte has 490 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/admin/config/users/CredentialEditor.svelte:1
warpgate-web/src/gateway/TicketRequests.svelte has 419 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/gateway/TicketRequests.svelte:1
warpgate-web/src/gateway/Login.svelte has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/gateway/Login.svelte:1
warpgate-web/src/gateway/TargetList.svelte has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — warpgate-web/src/gateway/TargetList.svelte:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
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.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code0.0 / 10Critical✓ 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.
Unreachable from the 2 application, 4 tooling and 1 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/Log.svelte, warpgate-web/src/admin/status/Session.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/log-viewer/LogViewer.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/Root.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — warpgate-web/src/gateway/WebDesktop.svelte, warpgate-web/src/gateway/WebSsh.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (warpgate-web/src/admin/config/users/AuthPolicyEditor.svelte, warpgate-web/src/admin/config/users/CredentialEditor.svelte, warpgate-web/src/admin/status/Session.svelte and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/WebSsh.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/gateway/WebSshTab.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte, warpgate-web/src/gateway/WebDesktop.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — warpgate-web/src/common/desktopInput.ts, warpgate-web/src/common/desktopCanvas.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/status/Recording.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte, warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/Config.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×6) — warpgate-web/src/admin/config/users/User.svelte, warpgate-web/src/admin/config/Parameters.svelte, warpgate-web/src/admin/config/ldap/LdapServer.svelte, …
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/config/users/AuthPolicyEditor.svelte, warpgate-web/src/admin/config/users/User.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/config/users/CredentialEditor.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte, warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/player/playbackController.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (warpgate-web/src/admin/config/ClientKeyModal.svelte, warpgate-web/src/admin/config/SSHKeys.svelte, warpgate-web/src/admin/config/secret-backends/SecretBackends.svelte and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/common/SecretRefInput.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/config/Policies.svelte, warpgate-web/src/admin/config/users/CredentialEditor.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/config/users/AuthPolicyEditor.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (warpgate-web/src/admin/config/CreateTicket.svelte, warpgate-web/src/admin/config/targets/Target.svelte, warpgate-web/src/gateway/TargetList.svelte and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/common/ConnectionInstructions.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/App.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — warpgate-web/src/gateway/TicketRequests.svelte, warpgate-web/src/gateway/TargetList.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 13 in-repo import(s) from 13 other file(s) do name it (warpgate-web/src/admin/config/AccessRole.svelte, warpgate-web/src/admin/config/AccessRoles.svelte, warpgate-web/src/admin/config/AdminRole.svelte and 10 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/common/ItemList.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/targets/ProtocolDocs.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/config/targets/protocolInfo.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/status/Status.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/status/Requests.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/status/Session.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/common/recordings.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/config/users/CredentialEditor.svelte, warpgate-web/src/common/ConnectionInstructions.svelte, warpgate-web/src/gateway/CredentialManager.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/CertificateCredentialModal.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/targets/ssh/Options.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/config/targets/ssh/KeyChecker.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 29 in-repo import(s) from 29 other file(s) do name it (warpgate-web/src/admin/App.svelte, warpgate-web/src/admin/config/AccessRole.svelte, warpgate-web/src/admin/config/AccessRoles.svelte and 26 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/lib/store.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/WebDesktop.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/common/desktopClipboard.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (warpgate-web/src/admin/config/Tickets.svelte, warpgate-web/src/admin/status/Requests.svelte, warpgate-web/src/common/DurationInput.svelte and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/common/duration.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/Root.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/gateway/App.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/config/Parameters.svelte, warpgate-web/src/admin/config/targets/Target.svelte, warpgate-web/src/admin/config/users/User.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — warpgate-web/src/admin/lib/SectionedForm.svelte, warpgate-web/src/common/RateLimitInput.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/ProfileCredentials.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/gateway/CredentialManager.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/player/playbackController.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/common/liveRecordingStream.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/config/users/CredentialEditor.svelte, warpgate-web/src/gateway/CredentialManager.svelte, warpgate-web/src/gateway/MfaSetup.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/CreateOtpModal.svelte
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte, warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte, warpgate-web/src/admin/player/playbackController.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/player/rangeStream.ts
no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — warpgate-web/src/admin/App.svelte
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.
Declared in warpgate-web/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.5 / 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.
`theme` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — warpgate-web/src/theme/index.ts:34
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?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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. (×8) — warpgate-web/src/gateway/App.svelte:114, warpgate-web/src/gateway/WebDesktop.svelte:413, warpgate-web/src/gateway/WebSshTab.svelte:89, …
`.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. (×3) — warpgate-web/src/common/desktopClipboard.ts:70, warpgate-web/src/common/SecretRefInput.svelte:163, warpgate-web/src/admin/player/rangeStream.ts:24
`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. (×2) — warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:147, warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte:209
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 log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`debug!` at line 193 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-web-ssh/src/manager.rs:193
`debug!` at line 52 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-sso/src/google_groups.rs:52
`debug!` at line 58 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — warpgate-sso/src/google_groups.rs:58, warpgate-sso/src/request.rs:58
`debug!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-sso/src/request.rs:59
`error!` at line 106 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-sso/src/request.rs:106
`warn!` at line 143 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-sso/src/request.rs:143
`warn!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-sso/src/request.rs:159
`debug!` at line 371 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-sso/src/sso.rs:371
`warn!` at line 381 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-sso/src/sso.rs:381
`error!` at line 129 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-secrets-vault/src/lib.rs:129
`debug!` at line 363 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-secrets-vault/src/lib.rs:363
`error!` at line 143 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-vnc/src/client.rs:143
`info!` at line 52 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/keys.rs:52
`info!` at line 58 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/keys.rs:58
`info!` at line 189 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/keys.rs:189
`info!` at line 204 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/keys.rs:204
`warn!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/keys.rs:241
`debug!` at line 606 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:606
`warn!` at line 799 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:799
`error!` at line 858 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:858
`error!` at line 878 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:878
`error!` at line 885 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:885
`info!` at line 1587 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:1587
`info!` at line 1619 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:1619
`info!` at line 1753 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:1753
`info!` at line 1912 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:1912
`info!` at line 2048 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:2048
`info!` at line 2097 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:2097
`info!` at line 2151 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:2151
`info!` at line 2189 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:2189
`warn!` at line 2484 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:2484
`info!` at line 2510 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/server/session.rs:2510
`debug!` at line 111 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/client/channel_session.rs:111
`warn!` at line 149 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/client/channel_session.rs:149
`debug!` at line 562 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/client/mod.rs:562
`info!` at line 568 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/client/mod.rs:568
`info!` at line 573 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/client/mod.rs:573
`info!` at line 586 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/client/mod.rs:586
`info!` at line 709 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — warpgate-protocol-ssh/src/client/mod.rs:709
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 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~0.9 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 3258 source line(s) of the 38 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: warpgate-web/src/admin/index.ts (1), warpgate-web/src/gateway/index.ts (1), warpgate-web/src/gateway/login.ts (1). 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?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 47 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container docker-warpgate-1 exited (1); runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
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; Python, Rust, TypeScript not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — Cross-context type coupling was not assessed: no type reached this dimension's context map.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 1 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.
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — SeaORM, sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 1 test file(s) reach none of 163 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
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 applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: parameters.rs ↔ lib.rs warpgate-admin/src/api/parameters.rs:1— `warpgate-admin/src/api/parameters.rs` (context warpgate-admin) and `warpgate-db-migrations/src/lib.rs` (context warpgate-db-migrations) sit in DIFFERENT parts of the tree yet change together 86% of the time (19 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) — 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 19 shared commits counted here, the most recent 3 are `b3cf6477` custom logo option (#2696); `aec66b7a` fixed #2556 - default auth policy (#2557); `3f36f133` fixed #2536 - do not record keypresses during interactive RDP logon, … — run `git show` on any of them.
Boundary-crossing change coupling: lib.rs ↔ lib.rs warpgate-protocol-mysql/src/lib.rs:1— `warpgate-protocol-mysql/src/lib.rs` (context warpgate-protocol-mysql) and `warpgate-protocol-postgres/src/lib.rs` (context warpgate-protocol-postgres) sit in DIFFERENT parts of the tree yet change together 77% of the time (10 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 10 shared commits counted here, the most recent 3 are `1b848915` Stop Kubernetes listener from becoming unavailable on incomplete TCP …; `bfcf2023` fixed #2379 - do not log LB health checks as failed sessions (#2390); `13478db2` Support TCP Proxy Protocol (#2174) — run `git show` on any of them.
Boundary-crossing change coupling: session.rs ↔ session.rs warpgate-protocol-mysql/src/session.rs:1— `warpgate-protocol-mysql/src/session.rs` (context warpgate-protocol-mysql) and `warpgate-protocol-ssh/src/server/session.rs` (context warpgate-protocol-ssh) sit in DIFFERENT parts of the tree yet change together 55% of the time (11 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) — 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 11 shared commits counted here, the most recent 3 are `0daf97d9` fixed #1981 - option to cache web approvals (#2175); `9ca14d10` record invalid usernames as login failures; `a037b92d` perf: find target by name using a query instead of doing it in memory… — run `git show` on any of them.
Boundary-crossing change coupling: auth_state_store.rs ↔ session.rs warpgate-core/src/auth_state_store.rs:1— `warpgate-core/src/auth_state_store.rs` (context warpgate-core) and `warpgate-protocol-ssh/src/server/session.rs` (context warpgate-protocol-ssh) sit in DIFFERENT parts of the tree yet change together 55% of the time (11 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) — 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 11 shared commits counted here, the most recent 3 are `0daf97d9` fixed #1981 - option to cache web approvals (#2175); `9ca14d10` record invalid usernames as login failures; `82041787` fixed #2027 - case-insensitive username comparison for web approval (… — run `git show` on any of them.
Boundary-crossing change coupling: client.rs ↔ session.rs warpgate-protocol-mysql/src/client.rs:1— `warpgate-protocol-mysql/src/client.rs` (context warpgate-protocol-mysql) and `warpgate-protocol-ssh/src/server/session.rs` (context warpgate-protocol-ssh) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `3a2a7229` error types cleanup (#2732); `4afa979d` bump rust some more; `bcba6763` cargo fmt — run `git show` on any of them.
Boundary-crossing change coupling: mod.rs ↔ main.rs warpgate-core/src/db/mod.rs:1— `warpgate-core/src/db/mod.rs` (context warpgate-core) and `warpgate/src/main.rs` (context warpgate) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `cd43586a` migrations already create the parameters instance (#2571); `e79e66c6` introduce warpgate copy-database command (#2475); `f66dee30` #1828 - option to disable host key checks (#2284) — run `git show` on any of them.
DM4 · Rich vs anemic domain model· Anemic domain model · ×1
Anemic domain model: QoeMetrics vendor/ironrdp-egfx/src/server.rs:261— `QoeMetrics` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside.
Hotspot: warpgate-protocol-ssh/src/server/session.rs warpgate-protocol-ssh/src/server/session.rs:1261— warpgate-protocol-ssh/src/server/session.rs changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in ServerSession::handle_remote_event at line 1261. 13 of those changes were fix/bug commits, and the other 16 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-ssh/src/server/session.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-rdp/src/client/mod.rs warpgate-protocol-rdp/src/client/mod.rs:153— warpgate-protocol-rdp/src/client/mod.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in warpgate_protocol_rdp::client::active_loop at line 153. 8 of those changes were fix/bug commits, and the other 15 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-rdp/src/client/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-kubernetes/src/server/handlers.rs warpgate-protocol-kubernetes/src/server/handlers.rs:294— warpgate-protocol-kubernetes/src/server/handlers.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner at line 294. 1 of those changes was a fix/bug commit, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-kubernetes/src/server/handlers.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-rdp/src/server/mod.rs warpgate-protocol-rdp/src/server/mod.rs:209— warpgate-protocol-rdp/src/server/mod.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in warpgate_protocol_rdp::server::control_loop at line 209. 5 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-rdp/src/server/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-ssh/src/client/mod.rs warpgate-protocol-ssh/src/client/mod.rs:1016— warpgate-protocol-ssh/src/client/mod.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Connector::authenticate_session at line 1016. 5 of those changes were fix/bug commits, and the other 13 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-ssh/src/client/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-http/src/common.rs warpgate-protocol-http/src/common.rs:521— warpgate-protocol-http/src/common.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in warpgate_protocol_http::common::inject_request_authorization at line 521. 3 of those changes were fix/bug commits, and the other 13 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-http/src/common.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-common/src/error.rs warpgate-common/src/error.rs:114— warpgate-common/src/error.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in WarpgateError::user_facing_reason at line 114. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-common/src/error.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-http/src/api/info.rs warpgate-protocol-http/src/api/info.rs:168— warpgate-protocol-http/src/api/info.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Api::api_get_info at line 168. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-http/src/api/info.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-web-ssh/src/manager.rs warpgate-web-ssh/src/manager.rs:141— warpgate-web-ssh/src/manager.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in warpgate_web_ssh::manager::relay_events at line 141. 4 of those changes were fix/bug commits, and the other 5 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-web-ssh/src/manager.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate/src/commands/run.rs warpgate/src/commands/run.rs:62— warpgate/src/commands/run.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in warpgate::commands::run::command 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate/src/commands/run.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-core/src/ticket_requests.rs warpgate-core/src/ticket_requests.rs:55— warpgate-core/src/ticket_requests.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in warpgate_core::ticket_requests::create_ticket_request at line 55. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-core/src/ticket_requests.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-mysql/src/client.rs warpgate-protocol-mysql/src/client.rs:41— warpgate-protocol-mysql/src/client.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in MySqlClient::connect at line 41. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-mysql/src/client.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-rdp/src/server/rdp.rs warpgate-protocol-rdp/src/server/rdp.rs:186— warpgate-protocol-rdp/src/server/rdp.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in warpgate_protocol_rdp::server::rdp::route_input at line 186. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-rdp/src/server/rdp.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-common/src/audit.rs warpgate-common/src/audit.rs:223— warpgate-common/src/audit.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in AuditEvent::emit at line 223. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-common/src/audit.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-rdp/src/server/bridge.rs warpgate-protocol-rdp/src/server/bridge.rs:26— warpgate-protocol-rdp/src/server/bridge.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in warpgate_protocol_rdp::server::bridge::frame_bridge at line 26. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-rdp/src/server/bridge.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-postgres/src/client.rs warpgate-protocol-postgres/src/client.rs:59— warpgate-protocol-postgres/src/client.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PostgresClient::connect at line 59. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-postgres/src/client.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-web/src/gateway/WebSsh.svelte warpgate-web/src/gateway/WebSsh.svelte:152— warpgate-web/src/gateway/WebSsh.svelte changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in onMessage at line 152. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-web/src/gateway/WebSsh.svelte`: 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: warpgate/src/main.rs warpgate/src/main.rs:191— warpgate/src/main.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in warpgate::_main at line 191. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate/src/main.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-core/src/db_auth.rs warpgate-core/src/db_auth.rs:189— warpgate-core/src/db_auth.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in warpgate_core::db_auth::authorize_user 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-core/src/db_auth.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-vnc/src/server/bridge.rs warpgate-protocol-vnc/src/server/bridge.rs:108— warpgate-protocol-vnc/src/server/bridge.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in warpgate_protocol_vnc::server::bridge::run_proxy_session at line 108. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-vnc/src/server/bridge.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: warpgate-protocol-http/src/catchall.rs warpgate-protocol-http/src/catchall.rs:128— warpgate-protocol-http/src/catchall.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in warpgate_protocol_http::catchall::get_target_for_request at line 128. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-protocol-http/src/catchall.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (10 lines × 2) warpgate-common/src/eventhub.rs:56— warpgate-common/src/eventhub.rs:56-65 | warpgate-common/src/eventhub.rs:72-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) warpgate-core/src/config_providers/db.rs:823— warpgate-core/src/config_providers/db.rs:823-832 | warpgate-core/src/config_providers/db.rs:884-893 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) warpgate-db-migrations/src/m00037_database_target_auth.rs:105— warpgate-db-migrations/src/m00037_database_target_auth.rs:105-114 | warpgate-db-migrations/src/m00038_fix_target_auth_tags.rs:106-115 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) warpgate-protocol-http/src/api/auth.rs:456— warpgate-protocol-http/src/api/auth.rs:456-465 | warpgate-protocol-http/src/api/auth.rs:608-617 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) warpgate-protocol-ssh/src/server/session.rs:1446— warpgate-protocol-ssh/src/server/session.rs:1446-1455 | warpgate-protocol-ssh/src/server/session.rs:1477-1486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) warpgate-db-migrations/src/m00058_analytics.rs:10— warpgate-db-migrations/src/m00058_analytics.rs:10-19 | warpgate-db-migrations/src/m00063_recordings_storage.rs:13-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) warpgate-db-migrations/src/m00058_analytics.rs:21— warpgate-db-migrations/src/m00058_analytics.rs:21-30 | warpgate-db-migrations/src/m00063_recordings_storage.rs:24-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) warpgate-db-migrations/src/m00080_user_and_target_sessions.rs:166— warpgate-db-migrations/src/m00080_user_and_target_sessions.rs:166-178 | warpgate-db-migrations/src/m00082_target_session_columns.rs:112-121 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) warpgate-protocol-http/src/api/credentials.rs:413— warpgate-protocol-http/src/api/credentials.rs:413-422 | warpgate-protocol-http/src/api/credentials.rs:637-646 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) warpgate-protocol-http/src/api/credentials.rs:467— warpgate-protocol-http/src/api/credentials.rs:467-476 | warpgate-protocol-http/src/api/credentials.rs:588-597 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) warpgate-aws/src/region.rs:14— warpgate-aws/src/region.rs:14-23 | warpgate-aws/src/region.rs:34-43 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) warpgate-admin/src/api/certificate_credentials.rs:146— warpgate-admin/src/api/certificate_credentials.rs:146-155 | warpgate-admin/src/api/public_key_credentials.rs:164-173 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) warpgate-protocol-ssh/src/server/session.rs:2046— warpgate-protocol-ssh/src/server/session.rs:2046-2055 | warpgate-protocol-ssh/src/server/session.rs:2095-2104 — 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.
MethodTooLong: AuditEvent.emit warpgate-common/src/audit.rs:223— MethodTooLong — emit runs 413 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 313 over it, 4.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.
MethodTooLong: Api.api_get_info warpgate-protocol-http/src/api/info.rs:168— MethodTooLong — api_get_info runs 195 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HTTPProtocolServer.bind warpgate-protocol-http/src/lib.rs:89— MethodTooLong — bind runs 176 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ServerSession.handle_remote_event warpgate-protocol-ssh/src/server/session.rs:1261— MethodTooLong — handle_remote_event runs 172 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: Migration.up warpgate-db-migrations/src/m00044_ticket_requests.rs:87— MethodTooLong — up runs 143 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Connector.authenticate_session warpgate-protocol-ssh/src/client/mod.rs:1016— MethodTooLong — authenticate_session runs 138 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 38 over it, 1.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.
MethodTooLong: MySqlClient.connect warpgate-protocol-mysql/src/client.rs:41— MethodTooLong — connect runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: ServerSession.handle_server_handler_event warpgate-protocol-ssh/src/server/session.rs:1051— MethodTooLong — handle_server_handler_event runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.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.
MethodTooLong: Api.api_return_to_sso_get_common warpgate-protocol-http/src/api/sso_provider_list.rs:243— MethodTooLong — api_return_to_sso_get_common runs 118 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: Migration.up warpgate-db-migrations/src/m00035_ticket_user_target_id.rs:86— MethodTooLong — up runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PostgresClient.connect warpgate-protocol-postgres/src/client.rs:59— MethodTooLong — connect runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Api.api_update_parameters warpgate-admin/src/api/parameters.rs:316— MethodTooLong — api_update_parameters runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: warpgate_protocol_rdp::server::control_loop warpgate-protocol-rdp/src/server/mod.rs:209— FunctionTooLong — warpgate_protocol_rdp::server::control_loop runs 174 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: warpgate::commands::run::command warpgate/src/commands/run.rs:62— FunctionTooLong — warpgate::commands::run::command runs 164 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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: warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner warpgate-protocol-kubernetes/src/server/handlers.rs:294— FunctionTooLong — warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.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: warpgate_core::db_auth::authorize_user warpgate-core/src/db_auth.rs:189— FunctionTooLong — warpgate_core::db_auth::authorize_user runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: warpgate_core::ticket_requests::create_ticket_request warpgate-core/src/ticket_requests.rs:55— FunctionTooLong — warpgate_core::ticket_requests::create_ticket_request runs 121 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: warpgate_protocol_vnc::server::negotiate_and_authorize warpgate-protocol-vnc/src/server/mod.rs:163— FunctionTooLong — warpgate_protocol_vnc::server::negotiate_and_authorize runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: warpgate_protocol_rdp::client::active_loop warpgate-protocol-rdp/src/client/mod.rs:153— FunctionTooLong — warpgate_protocol_rdp::client::active_loop runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: warpgate_protocol_vnc::server::protocol::read_client_messages warpgate-protocol-vnc/src/server/protocol.rs:276— FunctionTooLong — warpgate_protocol_vnc::server::protocol::read_client_messages runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: warpgate_desktop_auth::authenticate warpgate-desktop-auth/src/lib.rs:72— FunctionTooLong — warpgate_desktop_auth::authenticate runs 102 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: warpgate_protocol_http::proxy::proxy_ws_inner warpgate-protocol-http/src/proxy.rs:541— FunctionTooLong — warpgate_protocol_http::proxy::proxy_ws_inner runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: warpgate_protocol_kubernetes::server::handlers::_handle_websocket_request_inner warpgate-protocol-kubernetes/src/server/handlers.rs:577— FunctionTooLong — warpgate_protocol_kubernetes::server::handlers::_handle_websocket_request_inner runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Swallowed exception (empty catch) warpgate-web/src/gateway/App.svelte:114— 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) warpgate-web/src/gateway/WebDesktop.svelte:413— 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) warpgate-web/src/gateway/WebSshTab.svelte:89— 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) warpgate-web/src/gateway/WebSshTab.svelte:100— 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) warpgate-web/src/gateway/WebSshTab.svelte:142— 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) warpgate-web/src/gateway/WebSshTab.svelte:155— 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) warpgate-web/src/common/desktopClipboard.ts:70— `.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) warpgate-web/src/common/desktopInput.ts:73— 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) warpgate-web/src/common/RequestsButton.svelte:37— 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) warpgate-web/src/common/SecretRefInput.svelte:163— `.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) warpgate-web/src/admin/player/rangeStream.ts:24— `.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.
FileTooLong: server/session.rs warpgate-protocol-ssh/src/server/session.rs— FileTooLong — 1805 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: ServerSession (4 blocks, 134-2738). The bar is 500 significant lines; this is 1305 over it, 3.61× 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: client/mod.rs warpgate-protocol-ssh/src/client/mod.rs— FileTooLong — 998 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 498 over it, 2.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: config_providers/db.rs warpgate-core/src/config_providers/db.rs— FileTooLong — 720 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: DatabaseConfigProvider (3 blocks, 28-1021). The bar is 500 significant lines; this is 220 over it, 1.44× 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: api/users.rs warpgate-admin/src/api/users.rs— FileTooLong — 629 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 129 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: config/mod.rs warpgate-common/src/config/mod.rs— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 115 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.
FileTooLong: client/mod.rs warpgate-protocol-rdp/src/client/mod.rs— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 102 over it, 1.20× 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: api/auth.rs warpgate-protocol-http/src/api/auth.rs— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 74 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/audit.rs warpgate-common/src/audit.rs— FileTooLong — 573 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 96% of them inside a single declaration: AuditEvent (2 blocks, 35-687). The bar is 500 significant lines; this is 73 over it, 1.15× 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: server/handlers.rs warpgate-protocol-kubernetes/src/server/handlers.rs— FileTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 72 over it, 1.14× 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: api/credentials.rs warpgate-protocol-http/src/api/credentials.rs— FileTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 66% of them inside a single declaration: Api (248-714). The bar is 500 significant lines; this is 24 over it, 1.05× 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.
Off the main sequence: warpgate-ca — warpgate-ca: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Off the main sequence: warpgate-aws — warpgate-aws: abstractness 0.00, instability 0.10, distance 0.90 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Off the main sequence: warpgate-web — warpgate-web: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: warpgate-ldap — warpgate-ldap: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: warpgate-sso — warpgate-sso: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: warpgate-db-entities — warpgate-db-entities: abstractness 0.00, instability 0.22, distance 0.78 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
Off the main sequence: warpgate-tls — warpgate-tls: abstractness 0.17, instability 0.07, distance 0.77 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
Off the main sequence: warpgate-database-protocols — warpgate-database-protocols: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: warpgate-desktop-ui — warpgate-desktop-ui: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Duplicated block (13 lines × 2) warpgate-admin/src/api/otp_credentials.rs:151— warpgate-admin/src/api/otp_credentials.rs:151-163 | warpgate-admin/src/api/password_credentials.rs:159-171 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) warpgate-protocol-mysql/src/client.rs:98— warpgate-protocol-mysql/src/client.rs:98-110 | warpgate-protocol-postgres/src/client.rs:130-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) warpgate-protocol-ssh/src/server/session.rs:806— warpgate-protocol-ssh/src/server/session.rs:806-818 | warpgate-protocol-ssh/src/server/session.rs:2549-2562 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) warpgate-protocol-ssh/src/server/session.rs:2131— warpgate-protocol-ssh/src/server/session.rs:2131-2143 | warpgate-protocol-ssh/src/server/session.rs:2169-2181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:116— warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:116-130 | warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:203-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) warpgate-db-migrations/src/m00027_ca.rs:40— warpgate-db-migrations/src/m00027_ca.rs:40-52 | warpgate-db-migrations/src/m00027_ca.rs:53-65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) warpgate-db-migrations/src/m00057_password_login_mode.rs:35— warpgate-db-migrations/src/m00057_password_login_mode.rs:35-47 | warpgate-db-migrations/src/m00057_password_login_mode.rs:71-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) warpgate-web-desktop/src/manager.rs:78— warpgate-web-desktop/src/manager.rs:78-90 | warpgate-web-ssh/src/manager.rs:89-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) warpgate-admin/src/api/ldap_servers.rs:348— warpgate-admin/src/api/ldap_servers.rs:348-355 | warpgate-admin/src/api/ldap_servers.rs:414-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) warpgate-admin/src/api/users.rs:674— warpgate-admin/src/api/users.rs:674-681 | warpgate-admin/src/api/users.rs:728-735 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) warpgate-admin/src/api/users.rs:710— warpgate-admin/src/api/users.rs:710-717 | warpgate-admin/src/api/users.rs:764-771 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) warpgate-admin/src/api/users.rs:857— warpgate-admin/src/api/users.rs:857-864 | warpgate-admin/src/api/users.rs:907-914 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) warpgate-protocol-mysql/src/stream.rs:95— warpgate-protocol-mysql/src/stream.rs:95-103 | warpgate-protocol-postgres/src/stream.rs:158-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) warpgate-db-migrations/src/m00010_parameters.rs:32— warpgate-db-migrations/src/m00010_parameters.rs:32-39 | warpgate-db-migrations/src/m00020_ldap_server.rs:45-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) warpgate-protocol-rdp/src/lib.rs:123— warpgate-protocol-rdp/src/lib.rs:123-130 | warpgate-protocol-vnc/src/client.rs:143-153 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×6
Duplicated block (7 lines × 2) warpgate-core/src/ticket_requests.rs:171— warpgate-core/src/ticket_requests.rs:171-177 | warpgate-core/src/ticket_requests.rs:206-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) warpgate-db-migrations/src/m00075_hash_ticket_and_api_token_secrets.rs:36— warpgate-db-migrations/src/m00075_hash_ticket_and_api_token_secrets.rs:36-42 | warpgate-db-migrations/src/m00081_http_session_user_session_id.rs:104-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) warpgate-protocol-vnc/src/server/protocol.rs:385— warpgate-protocol-vnc/src/server/protocol.rs:385-391 | warpgate-protocol-vnc/src/server/protocol.rs:400-407 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) warpgate-common/src/helpers/serde_base64.rs:13— warpgate-common/src/helpers/serde_base64.rs:13-19 | warpgate-db-migrations/src/m00009_credential_models.rs:174-180 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) warpgate-admin/src/api/admin_scheme.rs:172— warpgate-admin/src/api/admin_scheme.rs:172-178 | warpgate-protocol-http/src/api/auth_scheme.rs:56-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) warpgate-protocol-ssh/src/server/session.rs:1087— warpgate-protocol-ssh/src/server/session.rs:1087-1093 | warpgate-protocol-ssh/src/server/session.rs:1698-1704 — 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.
ServerSession::handle_remote_event (cognitive 61) warpgate-protocol-ssh/src/server/session.rs:1261— ServerSession::handle_remote_event has cognitive complexity 61 (threshold 15). Drivers by points: if/else 20 (51 pts), match/switch 4 (7 pts), boolean chains 3 (nesting depth added 34). 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.
ServerSession::start (cognitive 35) warpgate-protocol-ssh/src/server/session.rs:258— ServerSession::start has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (24 pts), match/switch 3 (6 pts), loops 5 (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.
ServerSession::handle_event (cognitive 31) warpgate-protocol-ssh/src/server/session.rs:831— ServerSession::handle_event has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (23 pts), match/switch 3 (6 pts), boolean chains 2 (nesting depth added 14). 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.
ServerSession::try_auth_eager (cognitive 27) warpgate-protocol-ssh/src/server/session.rs:2385— ServerSession::try_auth_eager has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (22 pts), match/switch 3 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ServerSession::_auth_keyboard_interactive (cognitive 21) warpgate-protocol-ssh/src/server/session.rs:2183— ServerSession::_auth_keyboard_interactive has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassTooLong: ServerSession warpgate-protocol-ssh/src/server/session.rs:134— ClassTooLong — 1677 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 68 methods, 4 blocks, lines 134-2738. The bar is 400 significant lines; this is 1277 over it, 4.19× 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: DatabaseConfigProvider warpgate-core/src/config_providers/db.rs:28— ClassTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 3 methods, 3 blocks, lines 28-1021. The bar is 400 significant lines; this is 233 over it, 1.58× 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: AuditEvent warpgate-common/src/audit.rs:35— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 2 blocks, lines 35-687. The bar is 400 significant lines; this is 152 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ServerHandler warpgate-protocol-ssh/src/server/russh_handler.rs:103— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 5 blocks, lines 103-623. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LoginProtectionService warpgate-core/src/login_protection/service.rs:90— ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 16 methods, 2 blocks, lines 90-653. The bar is 400 significant lines; this is 4 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (14 lines × 2) warpgate-protocol-rdp/src/server/mod.rs:140— warpgate-protocol-rdp/src/server/mod.rs:140-154 | warpgate-protocol-vnc/src/server/mod.rs:100-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) warpgate-db-migrations/src/m00025_ssh_client_auth.rs:66— warpgate-db-migrations/src/m00025_ssh_client_auth.rs:66-79 | warpgate-db-migrations/src/m00086_jit_session_approval.rs:162-177 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:21— warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:21-34 | warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:35-48 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) warpgate-common/src/audit.rs:401— warpgate-common/src/audit.rs:401-414 | warpgate-common/src/audit.rs:420-433 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) warpgate-db-migrations/src/m00017_descriptions.rs:96— warpgate-db-migrations/src/m00017_descriptions.rs:96-109 | warpgate-db-migrations/src/m00019_rate_limits.rs:64-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) warpgate-common/src/audit.rs:542— warpgate-common/src/audit.rs:542-550 | warpgate-common/src/audit.rs:567-575 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) warpgate-common/src/audit.rs:611— warpgate-common/src/audit.rs:611-619 | warpgate-common/src/audit.rs:638-646 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) warpgate-protocol-http/src/api/credentials.rs:444— warpgate-protocol-http/src/api/credentials.rs:444-452 | warpgate-protocol-http/src/api/credentials.rs:549-557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:70— warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:70-78 | warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:79-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) warpgate-db-migrations/src/m00036_user_role_expiry_history.rs:13— warpgate-db-migrations/src/m00036_user_role_expiry_history.rs:13-21 | warpgate-db-migrations/src/m00036_user_role_expiry_history.rs:22-30 — 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.
warpgate_protocol_rdp::server::control_loop (cognitive 78) warpgate-protocol-rdp/src/server/mod.rs:209— warpgate_protocol_rdp::server::control_loop has cognitive complexity 78 (threshold 15). Drivers by points: if/else 19 (56 pts), match/switch 5 (18 pts), boolean chains 3, loops 1 (nesting depth added 50). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_rdp::client::active_loop (cognitive 49) warpgate-protocol-rdp/src/client/mod.rs:153— warpgate_protocol_rdp::client::active_loop has cognitive complexity 49 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 4 (9 pts), match/switch 3 (8 pts), boolean chains 2 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_rdp::server::rdp::route_input (cognitive 22) warpgate-protocol-rdp/src/server/rdp.rs:186— warpgate_protocol_rdp::server::rdp::route_input has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_rdp::client::input::translate (cognitive 18) warpgate-protocol-rdp/src/client/input.rs:11— warpgate_protocol_rdp::client::input::translate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner (cognitive 36) warpgate-protocol-kubernetes/src/server/handlers.rs:294— warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 6, loops 3 (4 pts), match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_kubernetes::correlator::correlated_authorization (cognitive 29) warpgate-protocol-kubernetes/src/correlator.rs:100— warpgate_protocol_kubernetes::correlator::correlated_authorization has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 6 (13 pts), boolean chains 1, loops 1 (nesting depth added 16). 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.
warpgate_protocol_kubernetes::server::auth::authenticate (cognitive 22) warpgate-protocol-kubernetes/src/server/auth.rs:295— warpgate_protocol_kubernetes::server::auth::authenticate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_kubernetes::server::handlers::_handle_websocket_request_inner (cognitive 16) warpgate-protocol-kubernetes/src/server/handlers.rs:577— warpgate_protocol_kubernetes::server::handlers::_handle_websocket_request_inner has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 7 (9 pts), if/else 6 (7 pts) (nesting depth added 3). 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.
TooManyFields: Model warpgate-db-entities/src/Parameters.rs:207— TooManyFields — 61 stored fields beside 10 methods. The bar is 30 stored fields; this is 31 over it, 2.03× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: ParameterValues warpgate-admin/src/api/parameters.rs:61— TooManyFields — 47 stored fields. The bar is 30 stored fields; this is 17 over it, 1.57× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: ParameterUpdate warpgate-admin/src/api/parameters.rs:113— TooManyFields — 47 stored fields. The bar is 30 stored fields; this is 17 over it, 1.57× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Info warpgate-protocol-http/src/api/info.rs:115— TooManyFields — 32 stored fields. The bar is 30 stored fields; this is 2 over it, 1.07× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×4
Duplicated block (15 lines × 2) warpgate-web-desktop/src/api.rs:26— warpgate-web-desktop/src/api.rs:26-40 | warpgate-web-ssh/src/api.rs:31-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) warpgate-db-migrations/src/m00025_ssh_client_auth.rs:28— warpgate-db-migrations/src/m00025_ssh_client_auth.rs:28-42 | warpgate-db-migrations/src/m00044_ticket_requests.rs:135-151 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) warpgate-db-migrations/src/m00019_rate_limits.rs:38— warpgate-db-migrations/src/m00019_rate_limits.rs:38-52 | warpgate-db-migrations/src/m00044_ticket_requests.rs:201-216 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) warpgate-db-migrations/src/m00031_minimize_password_login.rs:16— warpgate-db-migrations/src/m00031_minimize_password_login.rs:16-30 | warpgate-db-migrations/src/m00050_password_policy.rs:67-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
ServerSession::handle_remote_event (cyclomatic 47) warpgate-protocol-ssh/src/server/session.rs:1261— ServerSession::handle_remote_event has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: warpgate-protocol-ssh/src/server/session.rs holds 3 of the 22 functions over the threshold — including the worst — and 48 of the 142 points over it (34%), 2.5× the next-largest file (warpgate-protocol-rdp/src/server/mod.rs at 19). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ServerSession::handle_event (cyclomatic 25) warpgate-protocol-ssh/src/server/session.rs:831— ServerSession::handle_event 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. This is NOT this file's highest cyclomatic complexity: ServerSession::handle_server_handler_event (cyclomatic 30) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: warpgate-protocol-ssh/src/server/session.rs holds 3 of the 22 functions over the threshold — including the worst — and 48 of the 142 points over it (34%), 2.5× the next-largest file (warpgate-protocol-rdp/src/server/mod.rs at 19). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ServerSession::start (cyclomatic 21) warpgate-protocol-ssh/src/server/session.rs:258— ServerSession::start 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. This is NOT this file's highest cyclomatic complexity: ServerSession::handle_server_handler_event (cyclomatic 30) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: warpgate-protocol-ssh/src/server/session.rs holds 3 of the 22 functions over the threshold — including the worst — and 48 of the 142 points over it (34%), 2.5× the next-largest file (warpgate-protocol-rdp/src/server/mod.rs at 19). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Repeated repair: warpgate-web/src/gateway/WebDesktop.svelte warpgate-web/src/gateway/WebDesktop.svelte:138— warpgate-web/src/gateway/WebDesktop.svelte changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is onWsMessage at line 138), 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: “fixed #2522 - do not show empty admin page for non-admin users, allow ctrl-clicking ssh and desktop targets (#2523)”; “fixed #2487 - RDP - handle unstable bitmap parse order in Chromium (#2491)”; “fixed #2411 - support RDP clipboard redirection (#2447)”; “fixed #2349 - keyboard layouts in RDP (#2364)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-web/src/gateway/WebDesktop.svelte`: 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: warpgate-core/src/recordings/desktop.rs warpgate-core/src/recordings/desktop.rs:315— warpgate-core/src/recordings/desktop.rs changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is DesktopRecorder::write_event at line 315), 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: “fixed #2536 - do not record keypresses during interactive RDP logon, add disable keyboard recording option (#2537)”; “fixed #2487 - RDP - handle unstable bitmap parse order in Chromium (#2491)”; “fixed #2349 - keyboard layouts in RDP (#2364)”; “fixed #2326 - dynamic resolution in RDP web client (#2329)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-core/src/recordings/desktop.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: warpgate-web-desktop/src/protocol.rs warpgate-web-desktop/src/protocol.rs:219— warpgate-web-desktop/src/protocol.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is ServerMessage::from_event at line 219), 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: “fixed #2411 - support RDP clipboard redirection (#2447)”; “fixed #2349 - keyboard layouts in RDP (#2364)”; “fixed #2326 - dynamic resolution in RDP web client (#2329)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 05:58:54 +01:00' --until='2026-10-27 05:58:54 +01:00' --full-history --no-merges -- warpgate-web-desktop/src/protocol.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
warpgate_core::db_auth::authorize_user (cognitive 40) warpgate-core/src/db_auth.rs:189— warpgate_core::db_auth::authorize_user has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (34 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_core::config_providers::sso_user::resolve_and_map_sso_user (cognitive 22) warpgate-core/src/config_providers/sso_user.rs:11— warpgate_core::config_providers::sso_user::resolve_and_map_sso_user has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_core::ticket_requests::create_ticket_request (cognitive 18) warpgate-core/src/ticket_requests.rs:55— warpgate_core::ticket_requests::create_ticket_request has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 4, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
warpgate_protocol_vnc::client::run (cognitive 34) warpgate-protocol-vnc/src/client.rs:164— warpgate_protocol_vnc::client::run has cognitive complexity 34 (threshold 15). Drivers by points: if/else 4 (19 pts), match/switch 4 (9 pts), loops 3 (6 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_vnc::server::bridge::run_proxy_session (cognitive 32) warpgate-protocol-vnc/src/server/bridge.rs:108— warpgate_protocol_vnc::server::bridge::run_proxy_session has cognitive complexity 32 (threshold 15). Drivers by points: if/else 5 (18 pts), match/switch 4 (12 pts), boolean chains 1, loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_vnc::server::protocol::read_client_messages (cognitive 24) warpgate-protocol-vnc/src/server/protocol.rs:276— warpgate_protocol_vnc::server::protocol::read_client_messages has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 3 (9 pts), loops 2 (4 pts) (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Duplicated block (11 lines × 2) warpgate-core/src/config_providers/db.rs:407— warpgate-core/src/config_providers/db.rs:407-417 | warpgate-core/src/config_providers/db.rs:581-591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) warpgate-protocol-http/src/api/ticket_requests.rs:252— warpgate-protocol-http/src/api/ticket_requests.rs:252-262 | warpgate-protocol-http/src/api/ticket_requests.rs:383-393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) warpgate-admin/src/api/certificate_credentials.rs:253— warpgate-admin/src/api/certificate_credentials.rs:253-263 | warpgate-admin/src/api/public_key_credentials.rs:282-292 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) warpgate-core/src/recordings/traffic.rs:186— warpgate-core/src/recordings/traffic.rs:186-190 | warpgate-core/src/recordings/traffic.rs:198-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:284— warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:284-288 | warpgate-db-migrations/src/m00093_log_session_id_nullable.rs:142-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) warpgate-admin/src/api/recordings_detail.rs:106— warpgate-admin/src/api/recordings_detail.rs:106-110 | warpgate-admin/src/api/recordings_detail.rs:123-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) warpgate-db-migrations/src/m00044_ticket_requests.rs:219— warpgate-db-migrations/src/m00044_ticket_requests.rs:219-234 | warpgate-db-migrations/src/m00086_jit_session_approval.rs:66-81 — before extracting anything, compare `warpgate-db-migrations/src/m00044_ticket_requests.rs` and `warpgate-db-migrations/src/m00086_jit_session_approval.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) warpgate-db-migrations/src/m00044_ticket_requests.rs:106— warpgate-db-migrations/src/m00044_ticket_requests.rs:106-121 | warpgate-db-migrations/src/m00086_jit_session_approval.rs:100-115 — before extracting anything, compare `warpgate-db-migrations/src/m00044_ticket_requests.rs` and `warpgate-db-migrations/src/m00086_jit_session_approval.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) warpgate-common/src/audit.rs:226— warpgate-common/src/audit.rs:226-241 | warpgate-common/src/audit.rs:259-274 — 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.
warpgate_protocol_rdp::server::control_loop (cyclomatic 34) warpgate-protocol-rdp/src/server/mod.rs:209— warpgate_protocol_rdp::server::control_loop has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
warpgate_protocol_rdp::client::active_loop (cyclomatic 24) warpgate-protocol-rdp/src/client/mod.rs:153— warpgate_protocol_rdp::client::active_loop has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner (cyclomatic 25) warpgate-protocol-kubernetes/src/server/handlers.rs:294— warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner 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.
warpgate_protocol_kubernetes::server::handlers::_handle_websocket_request_inner (cyclomatic 17) warpgate-protocol-kubernetes/src/server/handlers.rs:577— warpgate_protocol_kubernetes::server::handlers::_handle_websocket_request_inner 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.
warpgate::commands::run::command (cyclomatic 23) warpgate/src/commands/run.rs:62— warpgate::commands::run::command has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
warpgate::_main (cyclomatic 16) warpgate/src/main.rs:191— warpgate::_main has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
warpgate_protocol_vnc::server::bridge::run_proxy_session (cyclomatic 20) warpgate-protocol-vnc/src/server/bridge.rs:108— warpgate_protocol_vnc::server::bridge::run_proxy_session 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.
warpgate_protocol_vnc::server::protocol::read_client_messages (cyclomatic 20) warpgate-protocol-vnc/src/server/protocol.rs:276— warpgate_protocol_vnc::server::protocol::read_client_messages has cyclomatic complexity 20 (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.
warpgate_core::db_auth::authorize_user (cyclomatic 19) warpgate-core/src/db_auth.rs:189— warpgate_core::db_auth::authorize_user has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
warpgate_core::ticket_requests::create_ticket_request (cyclomatic 17) warpgate-core/src/ticket_requests.rs:55— warpgate_core::ticket_requests::create_ticket_request 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.
Dead code: RsaToPkcs8String vendor/sspi/tools/aadjoin/AADJoin/Utils/CryptoUtils.cs:45— Method RsaToPkcs8String — Roslyn's SymbolFinder walked every project the solution loads, including AADJoin, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Pkcs8ToRsa vendor/sspi/tools/aadjoin/AADJoin/Utils/CryptoUtils.cs:87— Method Pkcs8ToRsa — Roslyn's SymbolFinder walked every project the solution loads, including AADJoin, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
warpgate::commands::run::command (cognitive 28) warpgate/src/commands/run.rs:62— warpgate::commands::run::command has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 6 (12 pts), if/else 7 (9 pts), loops 5 (7 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.
warpgate::config::check_and_migrate_config (cognitive 24) warpgate/src/config.rs:74— warpgate::config::check_and_migrate_config has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 1 (4 pts), loops 1 (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.
warpgate_desktop_auth::hold_screen::run_hold_screen (cognitive 28) warpgate-desktop-auth/src/hold_screen.rs:145— warpgate_desktop_auth::hold_screen::run_hold_screen has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 4 (15 pts), if/else 3 (9 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 18). 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.
warpgate_desktop_auth::authenticate (cognitive 19) warpgate-desktop-auth/src/lib.rs:72— warpgate_desktop_auth::authenticate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 3 (5 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Connector::authenticate_session (cognitive 27) warpgate-protocol-ssh/src/client/mod.rs:1016— Connector::authenticate_session has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Connector::_handle_auth_result (cognitive 19) warpgate-protocol-ssh/src/client/mod.rs:1214— Connector::_handle_auth_result has cognitive complexity 19 (threshold 15). Drivers by points: loops 3 (11 pts), match/switch 2 (5 pts), if/else 1 (3 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
warpgate_admin::api::recordings_detail::serve_live_stream (cognitive 26) warpgate-admin/src/api/recordings_detail.rs:270— warpgate_admin::api::recordings_detail::serve_live_stream has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 4 (10 pts), boolean chains 1, loops 1 (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
warpgate_admin::api::recordings_detail::replay_scratch_span_awaiting (cognitive 16) warpgate-admin/src/api/recordings_detail.rs:213— warpgate_admin::api::recordings_detail::replay_scratch_span_awaiting has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_http::catchall::get_target_for_request (cognitive 23) warpgate-protocol-http/src/catchall.rs:128— warpgate_protocol_http::catchall::get_target_for_request has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_protocol_http::common::inject_request_authorization (cognitive 20) warpgate-protocol-http/src/common.rs:521— warpgate_protocol_http::common::inject_request_authorization has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Migration::up (cognitive 21) warpgate-db-migrations/src/m00038_fix_target_auth_tags.rs:50— Migration::up has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Migration::up (cognitive 16) warpgate-db-migrations/src/m00087_drop_null_target_options.rs:78— Migration::up has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 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.
Change coupling: handler.rs ↔ russh_handler.rs warpgate-protocol-ssh/src/client/handler.rs:1— `warpgate-protocol-ssh/src/client/handler.rs` and `warpgate-protocol-ssh/src/server/russh_handler.rs` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 `6c231ba6` fixed #1459 - concurrent agent channel requests causing deadlock (#2135); `9453879e` fmt; `e2036886` Implement Agent Forwarding (#1249) — run `git show` on any of them.
Change coupling: handler.rs ↔ session.rs warpgate-protocol-ssh/src/client/handler.rs:1— `warpgate-protocol-ssh/src/client/handler.rs` and `warpgate-protocol-ssh/src/server/session.rs` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `3a2a7229` error types cleanup (#2732); `f66dee30` #1828 - option to disable host key checks (#2284); `6c231ba6` fixed #1459 - concurrent agent channel requests causing deadlock (#2135) — run `git show` on any of them.
Duplicated block (6 lines × 3) warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:53— warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:53-58 | warpgate-db-migrations/src/m00080_user_and_target_sessions.rs:64-69 | warpgate-db-migrations/src/m00087_drop_null_target_options.rs:100-105 — before extracting anything, compare `warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs` and `warpgate-db-migrations/src/m00087_drop_null_target_options.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:62— warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:62-67 | warpgate-db-migrations/src/m00080_user_and_target_sessions.rs:74-79 | warpgate-db-migrations/src/m00087_drop_null_target_options.rs:109-114 — before extracting anything, compare `warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs` and `warpgate-db-migrations/src/m00087_drop_null_target_options.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) warpgate-core/src/recordings/desktop.rs:238— warpgate-core/src/recordings/desktop.rs:238-243 | warpgate-core/src/recordings/terminal.rs:99-104 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) warpgate-db-migrations/src/m00010_parameters.rs:41— warpgate-db-migrations/src/m00010_parameters.rs:41-46 | warpgate-db-migrations/src/m00020_ldap_server.rs:54-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:47— warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:47-74 | warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:153-169 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) warpgate-db-migrations/src/m00034_add_log_related_fields.rs:25— warpgate-db-migrations/src/m00034_add_log_related_fields.rs:25-41 | warpgate-db-migrations/src/m00034_add_log_related_fields.rs:48-64 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2 locations) REDACTED:203— REDACTED:203 · REDACTED:224 — 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 (11 lines × 2 locations) warpgate-web/src/gateway/lib/certificateStore.ts:24— warpgate-web/src/gateway/lib/certificateStore.ts:24 · warpgate-web/src/gateway/lib/certificateStore.ts:48 — 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.
Dead file (~158 LoC) warpgate-web/src/admin/CertificateCredentialModal.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/config/users/CredentialEditor.svelte, warpgate-web/src/common/ConnectionInstructions.svelte, warpgate-web/src/gateway/CredentialManager.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~158 LoC) warpgate-web/src/admin/config/targets/ssh/KeyChecker.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/targets/ssh/Options.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Swallowed exception (caught, then discarded) warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:147— `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) warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte:209— `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.
SessionChannel::run (cyclomatic 26) warpgate-protocol-ssh/src/client/channel_session.rs:40— SessionChannel::run has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Api::api_get_info (cyclomatic 19) warpgate-protocol-http/src/api/info.rs:168— Api::api_get_info 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.
MySqlClient::connect (cyclomatic 19) warpgate-protocol-mysql/src/client.rs:41— MySqlClient::connect has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PostgresClient::connect (cyclomatic 18) warpgate-protocol-postgres/src/client.rs:59— PostgresClient::connect has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TargetMenu::handle_input (cyclomatic 17) warpgate-protocol-ssh/src/server/target_menu.rs:193— TargetMenu::handle_input 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.
PlaybackController.doSeek (cyclomatic 17) warpgate-web/src/admin/player/playbackController.ts:173— PlaybackController.doSeek 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.
warpgate_desktop_auth::hold_screen::run_hold_screen (cyclomatic 16) warpgate-desktop-auth/src/hold_screen.rs:145— warpgate_desktop_auth::hold_screen::run_hold_screen has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Connector::authenticate_session (cyclomatic 16) warpgate-protocol-ssh/src/client/mod.rs:1016— Connector::authenticate_session 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.
warpgate_web_ssh::manager::relay_events (cyclomatic 16) warpgate-web-ssh/src/manager.rs:141— warpgate_web_ssh::manager::relay_events has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Api::api_get_info (cognitive 37) warpgate-protocol-http/src/api/info.rs:168— Api::api_get_info has cognitive complexity 37 (threshold 15). Drivers by points: if/else 24 (31 pts), boolean chains 3, match/switch 3 (nesting depth added 7). 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.
DirtyTracker::take_settled (cognitive 27) warpgate-web-desktop/src/dirty.rs:71— DirtyTracker::take_settled has cognitive complexity 27 (threshold 15). Drivers by points: loops 6 (16 pts), if/else 3 (11 pts) (nesting depth added 18). 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.
warpgate_web_desktop::manager::relay_events (cognitive 26) warpgate-web-desktop/src/manager.rs:251— warpgate_web_desktop::manager::relay_events has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 3 (7 pts), loops 2 (4 pts), boolean chains 2 (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.
warpgate_protocol_ssh::server::target_menu::run_target_menu_loop (cognitive 24) warpgate-protocol-ssh/src/server/target_menu.rs:496— warpgate_protocol_ssh::server::target_menu::run_target_menu_loop has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (17 pts), match/switch 2 (5 pts), boolean chains 1, loops 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.
PostgresClient::connect (cognitive 22) warpgate-protocol-postgres/src/client.rs:59— PostgresClient::connect has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 4 (8 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TlsCertificateBundle::sni_names (cognitive 22) warpgate-tls/src/cert.rs:82— TlsCertificateBundle::sni_names has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MySqlClient::connect (cognitive 20) warpgate-protocol-mysql/src/client.rs:41— MySqlClient::connect has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
warpgate_web_clients_common::run_stream_loop (cognitive 20) warpgate-web-clients-common/src/lib.rs:460— warpgate_web_clients_common::run_stream_loop has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ListenerSupervisor::run (cognitive 19) warpgate/src/listener_supervisor.rs:115— ListenerSupervisor::run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
helpers.toClassName (cognitive 19) warpgate-web/src/common/helpers.ts:55— helpers.toClassName has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 1 (3 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.
HandshakeResponse::encode_with (cognitive 18) warpgate-database-protocols/src/mysql/protocol/connect/handshake_response.rs:36— HandshakeResponse::encode_with has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (18 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, 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.
protocols.getEffectivePossibleCredentials (cognitive 18) REDACTED:333— protocols.getEffectivePossibleCredentials has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Services::new (cognitive 17) warpgate-core/src/services.rs:156— Services::new has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 6 (7 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.
ResponseRelay::next (cognitive 17) warpgate-protocol-mysql/src/relay.rs:64— ResponseRelay::next has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PostgresSession::run_authorized_inner (cognitive 17) warpgate-protocol-postgres/src/session.rs:352— PostgresSession::run_authorized_inner has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 1 (3 pts), loops 1 (nesting depth added 8). 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.
TargetMenu::handle_input (cognitive 17) warpgate-protocol-ssh/src/server/target_menu.rs:193— TargetMenu::handle_input has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CookieHostMiddlewareEndpoint::call (cognitive 16) warpgate-protocol-http/src/middleware/cookie_host.rs:89— CookieHostMiddlewareEndpoint::call has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyMethods: ServerSession warpgate-protocol-ssh/src/server/session.rs:134— TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.27× 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.
Near-duplicate member pair (50 shared lines) warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:24— warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:24-134 | warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:136-240 — These two members are variants of one another: 50 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) warpgate-common/src/auth/state.rs:463— warpgate-common/src/auth/state.rs:463-476 | warpgate-core/src/approvals/subject.rs:61-74 | warpgate-core/src/approvals/subject.rs:76-89 | warpgate-core/src/approvals/subject.rs:91-104 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (27 lines × 2) warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:48— warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:48-74 | warpgate-db-migrations/src/m00087_drop_null_target_options.rs:95-121 — before extracting anything, compare `warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs` and `warpgate-db-migrations/src/m00087_drop_null_target_options.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–20 lines × 2) warpgate-core/src/logging/json_console.rs:37— warpgate-core/src/logging/json_console.rs:37-56 | warpgate-core/src/logging/layer.rs:50-67 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9–13 lines × 2) warpgate-db-migrations/src/m00072_session_node_id_not_null.rs:19— warpgate-db-migrations/src/m00072_session_node_id_not_null.rs:19-31 | warpgate-db-migrations/src/m00080_user_and_target_sessions.rs:232-240 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) warpgate-admin/src/api/certificate_credentials.rs:142— warpgate-admin/src/api/certificate_credentials.rs:142-153 | warpgate-protocol-http/src/api/credentials.rs:633-644 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8–12 lines × 2) warpgate-protocol-mysql/src/lib.rs:49— warpgate-protocol-mysql/src/lib.rs:49-56 | warpgate-protocol-postgres/src/lib.rs:50-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8–9 lines × 2) warpgate-admin/src/api/certificate_credentials.rs:194— warpgate-admin/src/api/certificate_credentials.rs:194-201 | warpgate-admin/src/api/certificate_credentials.rs:226-234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 6) warpgate-common/src/audit.rs:541— warpgate-common/src/audit.rs:541-548 | warpgate-common/src/audit.rs:566-573 | warpgate-common/src/audit.rs:588-595 | warpgate-common/src/audit.rs:610-617 | warpgate-common/src/audit.rs:637-644 | warpgate-common/src/audit.rs:668-675 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) warpgate-protocol-mysql/src/lib.rs:49— warpgate-protocol-mysql/src/lib.rs:49-56 | warpgate-protocol-postgres/src/lib.rs:50-57 | warpgate-protocol-vnc/src/server/mod.rs:49-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 4) warpgate-common/src/auth/state.rs:467— warpgate-common/src/auth/state.rs:467-473 | warpgate-core/src/approvals/subject.rs:65-71 | warpgate-core/src/approvals/subject.rs:80-86 | warpgate-core/src/approvals/subject.rs:95-101 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (23 lines × 2) warpgate-db-migrations/src/m00066_cluster_token.rs:8— warpgate-db-migrations/src/m00066_cluster_token.rs:8-30 | warpgate-db-migrations/src/m00091_drop_cluster_token.rs:8-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 4) warpgate-protocol-mysql/src/session_handle.rs:9— warpgate-protocol-mysql/src/session_handle.rs:9-18 | warpgate-protocol-postgres/src/session_handle.rs:9-18 | warpgate-protocol-rdp/src/session_handle.rs:9-18 | warpgate-protocol-vnc/src/server/session_handle.rs:9-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (9 lines × 8) warpgate-db-entities/src/ApiToken.rs:25— warpgate-db-entities/src/ApiToken.rs:25-33 | warpgate-db-entities/src/CertificateCredential.rs:28-36 | warpgate-db-entities/src/OtpCredential.rs:23-31 | warpgate-db-entities/src/PasswordCredential.rs:23-31 | warpgate-db-entities/src/PublicKeyCredential.rs:28-36 | warpgate-db-entities/src/SsoCredential.rs:24-32 | warpgate-db-migrations/src/m00014_api_tokens.rs:31-39 | warpgate-db-migrations/src/m00028_certificate_credentials.rs:33-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times.
Duplicated block (20 lines × 2) warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:88— warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:88-108 | warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:179-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 4) warpgate-db-migrations/src/m00044_ticket_requests.rs:121— warpgate-db-migrations/src/m00044_ticket_requests.rs:121-137 | warpgate-db-migrations/src/m00044_ticket_requests.rs:176-192 | warpgate-db-migrations/src/m00050_password_policy.rs:23-39 | warpgate-db-migrations/src/m00050_password_policy.rs:51-67 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (15 lines × 4) warpgate-db-migrations/src/m00025_ssh_client_auth.rs:42— warpgate-db-migrations/src/m00025_ssh_client_auth.rs:42-56 | warpgate-db-migrations/src/m00037_show_session_menu.rs:16-30 | warpgate-db-migrations/src/m00047_record_scp.rs:11-25 | warpgate-db-migrations/src/m00083_record_desktop_keyboard_input.rs:11-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (14 lines × 5) warpgate-db-migrations/src/m00044_ticket_requests.rs:120— warpgate-db-migrations/src/m00044_ticket_requests.rs:120-134 | warpgate-db-migrations/src/m00044_ticket_requests.rs:175-189 | warpgate-db-migrations/src/m00050_password_policy.rs:22-36 | warpgate-db-migrations/src/m00050_password_policy.rs:50-64 | warpgate-db-migrations/src/m00084_mfa_enforcement.rs:22-35 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (14 lines × 4) warpgate-common/src/audit.rs:321— warpgate-common/src/audit.rs:321-334 | warpgate-common/src/audit.rs:341-354 | warpgate-common/src/audit.rs:361-374 | warpgate-common/src/audit.rs:381-394 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) warpgate-db-migrations/src/m00044_ticket_requests.rs:221— warpgate-db-migrations/src/m00044_ticket_requests.rs:221-234 | warpgate-db-migrations/src/m00044_ticket_requests.rs:235-248 | warpgate-db-migrations/src/m00086_jit_session_approval.rs:68-81 — before extracting anything, compare `warpgate-db-migrations/src/m00044_ticket_requests.rs` and `warpgate-db-migrations/src/m00086_jit_session_approval.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) warpgate-db-migrations/src/m00025_ssh_client_auth.rs:60— warpgate-db-migrations/src/m00025_ssh_client_auth.rs:60-71 | warpgate-db-migrations/src/m00027_ca.rs:97-109 | warpgate-db-migrations/src/m00084_mfa_enforcement.rs:40-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
End-of-life runtime: .NET net6.0 vendor/sspi/tools/aadjoin/UnitTests/UnitTests.csproj:4— vendor/sspi/tools/aadjoin/UnitTests/UnitTests.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Unstable project warpgate-web-ssh — warpgate-web-ssh has instability 0.86 with 1 dependents.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Duplicated block (28 lines × 2 locations) warpgate-web/src/gateway/WebDesktop.svelte:449— warpgate-web/src/gateway/WebDesktop.svelte:449 · warpgate-web/src/gateway/WebSsh.svelte:270 — 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 (23 lines × 2 locations) warpgate-web/src/admin/config/AccessRoles.svelte:12— warpgate-web/src/admin/config/AccessRoles.svelte:12 · warpgate-web/src/admin/config/users/Users.svelte:21 — 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 (19 matched lines × 2 locations) · ×1
Duplicated block with local edits (19 matched lines × 2 locations) warpgate-web/src/admin/config/Parameters.svelte:82— warpgate-web/src/admin/config/Parameters.svelte:82 · warpgate-web/src/admin/config/Policies.svelte:16 — the two spans are one implementation copied and then locally edited — 93 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 (17 lines × 2 locations) warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:140— warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:140 · warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte:202 — 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 (16 lines × 2 locations) warpgate-web/src/admin/config/ldap/CreateLdapServer.svelte:48— warpgate-web/src/admin/config/ldap/CreateLdapServer.svelte:48 · warpgate-web/src/admin/config/ldap/LdapServer.svelte:88 — 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 (15 lines × 2 locations) warpgate-web/src/admin/config/AccessRole.svelte:27— warpgate-web/src/admin/config/AccessRole.svelte:27 · warpgate-web/src/admin/config/AccessRole.svelte:43 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 3 locations) warpgate-web/src/admin/config/AccessRole.svelte:62— warpgate-web/src/admin/config/AccessRole.svelte:62 · warpgate-web/src/admin/config/AdminRole.svelte:127 · warpgate-web/src/admin/config/targets/Target.svelte:81 — 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 (14 lines × 3 locations) warpgate-web/src/admin/config/AccessRoles.svelte:21— warpgate-web/src/admin/config/AccessRoles.svelte:21 · warpgate-web/src/admin/config/target-groups/TargetGroups.svelte:24 · warpgate-web/src/admin/config/users/Users.svelte:30 — the 3 copies are spread across 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (12 lines × 2 locations) warpgate-web/src/gateway/WebDesktop.svelte:76— warpgate-web/src/gateway/WebDesktop.svelte:76 · warpgate-web/src/gateway/WebSsh.svelte:111 — 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 (9 lines × 2 locations) warpgate-web/src/admin/lib/api.ts:8— warpgate-web/src/admin/lib/api.ts:8 · warpgate-web/src/gateway/lib/api.ts:4 — 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.
Duplicated block (7 lines × 2 locations) warpgate-web/src/admin/status/Session.svelte:64— warpgate-web/src/admin/status/Session.svelte:64 · warpgate-web/src/admin/status/Session.svelte:78 — 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 (5 lines × 2 locations) REDACTED:100— REDACTED:100 · REDACTED:126 — 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.
Complex function onMessage (cyclomatic 16, cognitive 11) warpgate-web/src/gateway/WebSsh.svelte:152— onMessage has cyclomatic complexity 16 and cognitive complexity 11; 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 mfaEnforcedFactor (cyclomatic 14, cognitive 14) warpgate-web/src/admin/config/users/AuthPolicyEditor.svelte:113— mfaEnforcedFactor has cyclomatic complexity 14 and cognitive complexity 14; 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 parseHumantimeDuration (cyclomatic 13, cognitive 12) warpgate-web/src/common/duration.ts:35— parseHumantimeDuration has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getEffectivePossibleCredentials (cyclomatic 12, cognitive 18) REDACTED:333— getEffectivePossibleCredentials has cyclomatic complexity 12 and cognitive complexity 18; 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 save (cyclomatic 12, cognitive 11) · ×1
Complex function save (cyclomatic 12, cognitive 11) warpgate-web/src/admin/config/Parameters.svelte:116— save has cyclomatic complexity 12 and cognitive complexity 11; 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 12, cognitive 11) warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:121— (anonymous) has cyclomatic complexity 12 and cognitive complexity 11; 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 updateActiveSectionFromScroll (cyclomatic 11, cognitive 18) warpgate-web/src/admin/lib/SectionedForm.svelte:23— updateActiveSectionFromScroll has cyclomatic complexity 11 and cognitive complexity 18; 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 onWsMessage (cyclomatic 11, cognitive 12) warpgate-web/src/gateway/WebDesktop.svelte:138— onWsMessage has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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· warpgate-web/src/admin/config/Parameters.svelte · ×1
warpgate-web/src/admin/config/Parameters.svelte: 1278 lines of code warpgate-web/src/admin/config/Parameters.svelte:1— warpgate-web/src/admin/config/Parameters.svelte has 1278 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· warpgate-web/src/admin/log-viewer/LogViewer.svelte · ×1
warpgate-web/src/admin/log-viewer/LogViewer.svelte: 1092 lines of code warpgate-web/src/admin/log-viewer/LogViewer.svelte:1— warpgate-web/src/admin/log-viewer/LogViewer.svelte has 1092 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· warpgate-web/src/admin/config/targets/Target.svelte · ×1
warpgate-web/src/admin/config/targets/Target.svelte: 693 lines of code warpgate-web/src/admin/config/targets/Target.svelte:1— warpgate-web/src/admin/config/targets/Target.svelte has 693 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· warpgate-web/src/admin/config/users/User.svelte · ×1
warpgate-web/src/admin/config/users/User.svelte: 587 lines of code warpgate-web/src/admin/config/users/User.svelte:1— warpgate-web/src/admin/config/users/User.svelte has 587 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· warpgate-web/src/gateway/WebDesktop.svelte · ×1
warpgate-web/src/gateway/WebDesktop.svelte: 547 lines of code warpgate-web/src/gateway/WebDesktop.svelte:1— warpgate-web/src/gateway/WebDesktop.svelte has 547 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· warpgate-web/src/gateway/WebSsh.svelte · ×1
warpgate-web/src/gateway/WebSsh.svelte: 523 lines of code warpgate-web/src/gateway/WebSsh.svelte:1— warpgate-web/src/gateway/WebSsh.svelte has 523 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· warpgate-web/src/common/ConnectionInstructions.svelte · ×1
warpgate-web/src/common/ConnectionInstructions.svelte: 505 lines of code warpgate-web/src/common/ConnectionInstructions.svelte:1— warpgate-web/src/common/ConnectionInstructions.svelte has 505 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· warpgate-web/src/admin/config/users/CredentialEditor.svelte · ×1
warpgate-web/src/admin/config/users/CredentialEditor.svelte: 490 lines of code warpgate-web/src/admin/config/users/CredentialEditor.svelte:1— warpgate-web/src/admin/config/users/CredentialEditor.svelte has 490 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· warpgate-web/src/gateway/TicketRequests.svelte · ×1
warpgate-web/src/gateway/TicketRequests.svelte: 419 lines of code warpgate-web/src/gateway/TicketRequests.svelte:1— warpgate-web/src/gateway/TicketRequests.svelte has 419 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· warpgate-web/src/gateway/Login.svelte · ×1
warpgate-web/src/gateway/Login.svelte: 406 lines of code warpgate-web/src/gateway/Login.svelte:1— warpgate-web/src/gateway/Login.svelte has 406 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· warpgate-web/src/gateway/TargetList.svelte · ×1
warpgate-web/src/gateway/TargetList.svelte: 406 lines of code warpgate-web/src/gateway/TargetList.svelte:1— warpgate-web/src/gateway/TargetList.svelte has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~500 LoC) warpgate-web/src/admin/log-viewer/LogViewer.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/Log.svelte, warpgate-web/src/admin/status/Session.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~494 LoC) warpgate-web/src/gateway/WebDesktop.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/Root.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~374 LoC) REDACTED— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (warpgate-web/src/admin/config/users/AuthPolicyEditor.svelte, warpgate-web/src/admin/config/users/CredentialEditor.svelte, warpgate-web/src/admin/status/Session.svelte and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~331 LoC) warpgate-web/src/gateway/WebSshTab.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/WebSsh.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~324 LoC) warpgate-web/src/common/desktopInput.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte, warpgate-web/src/gateway/WebDesktop.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~322 LoC) warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/status/Recording.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~316 LoC) warpgate-web/src/gateway/WebSsh.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/Root.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~314 LoC) warpgate-web/src/admin/config/users/User.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/Config.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~308 LoC) warpgate-web/src/admin/config/users/CredentialEditor.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/config/users/AuthPolicyEditor.svelte, warpgate-web/src/admin/config/users/User.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~297 LoC) warpgate-web/src/admin/player/playbackController.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte, warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~242 LoC) warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/status/Recording.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~233 LoC) warpgate-web/src/common/desktopCanvas.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte, warpgate-web/src/gateway/WebDesktop.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~221 LoC) warpgate-web/src/common/SecretRefInput.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (warpgate-web/src/admin/config/ClientKeyModal.svelte, warpgate-web/src/admin/config/SSHKeys.svelte, warpgate-web/src/admin/config/secret-backends/SecretBackends.svelte and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~213 LoC) warpgate-web/src/admin/config/users/AuthPolicyEditor.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (warpgate-web/src/admin/config/Policies.svelte, warpgate-web/src/admin/config/users/CredentialEditor.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~206 LoC) warpgate-web/src/common/ConnectionInstructions.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (warpgate-web/src/admin/config/CreateTicket.svelte, warpgate-web/src/admin/config/targets/Target.svelte, warpgate-web/src/gateway/TargetList.svelte and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~198 LoC) warpgate-web/src/gateway/TicketRequests.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/App.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~193 LoC) warpgate-web/src/common/ItemList.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 13 in-repo import(s) from 13 other file(s) do name it (warpgate-web/src/admin/config/AccessRole.svelte, warpgate-web/src/admin/config/AccessRoles.svelte, warpgate-web/src/admin/config/AdminRole.svelte and 10 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~184 LoC) warpgate-web/src/admin/config/targets/protocolInfo.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/targets/ProtocolDocs.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~183 LoC) warpgate-web/src/admin/status/Requests.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/status/Status.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~172 LoC) warpgate-web/src/admin/config/Parameters.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/Config.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~160 LoC) warpgate-web/src/common/recordings.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/status/Session.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~159 LoC) warpgate-web/src/gateway/TargetList.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/App.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~148 LoC) warpgate-web/src/admin/config/ldap/LdapServer.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/Config.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~147 LoC) warpgate-web/src/admin/lib/store.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 29 in-repo import(s) from 29 other file(s) do name it (warpgate-web/src/admin/App.svelte, warpgate-web/src/admin/config/AccessRole.svelte, warpgate-web/src/admin/config/AccessRoles.svelte and 26 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~143 LoC) warpgate-web/src/common/desktopClipboard.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/WebDesktop.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~142 LoC) warpgate-web/src/admin/config/AdminRole.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/Config.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~140 LoC) warpgate-web/src/admin/config/targets/CreateTarget.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/Config.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~135 LoC) warpgate-web/src/common/duration.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (warpgate-web/src/admin/config/Tickets.svelte, warpgate-web/src/admin/status/Requests.svelte, warpgate-web/src/common/DurationInput.svelte and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~133 LoC) warpgate-web/src/gateway/App.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/Root.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~126 LoC) warpgate-web/src/admin/config/targets/Target.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/config/Config.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~123 LoC) warpgate-web/src/admin/lib/SectionedForm.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/config/Parameters.svelte, warpgate-web/src/admin/config/targets/Target.svelte, warpgate-web/src/admin/config/users/User.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~119 LoC) warpgate-web/src/gateway/CredentialManager.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/gateway/ProfileCredentials.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~115 LoC) warpgate-web/src/common/RateLimitInput.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/config/Parameters.svelte, warpgate-web/src/admin/config/targets/Target.svelte, warpgate-web/src/admin/config/users/User.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~114 LoC) warpgate-web/src/common/liveRecordingStream.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/player/playbackController.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~111 LoC) warpgate-web/src/admin/CreateOtpModal.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/config/users/CredentialEditor.svelte, warpgate-web/src/gateway/CredentialManager.svelte, warpgate-web/src/gateway/MfaSetup.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~109 LoC) warpgate-web/src/admin/player/rangeStream.ts— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte, warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte, warpgate-web/src/admin/player/playbackController.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~105 LoC) warpgate-web/src/admin/App.svelte— no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (warpgate-web/src/admin/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Unused dependency '@otplib/plugin-base32-enc-dec' — Declared in warpgate-web/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 '@otplib/plugin-crypto-js' — Declared in warpgate-web/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 '@otplib/preset-browser' — Declared in warpgate-web/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.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×1
Untrusted text written into markup unescaped warpgate-web/src/theme/index.ts:34— `theme` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Interpolated log message defeats structured logging warpgate-web-ssh/src/manager.rs:193— `debug!` at line 193 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/google_groups.rs:52— `debug!` at line 52 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/google_groups.rs:58— `debug!` at line 58 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/request.rs:58— `debug!` at line 58 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/request.rs:59— `debug!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/request.rs:106— `error!` at line 106 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/request.rs:143— `warn!` at line 143 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/request.rs:159— `warn!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/sso.rs:371— `debug!` at line 371 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-sso/src/sso.rs:381— `warn!` at line 381 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-secrets-vault/src/lib.rs:129— `error!` at line 129 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-secrets-vault/src/lib.rs:363— `debug!` at line 363 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-vnc/src/client.rs:143— `error!` at line 143 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/keys.rs:52— `info!` at line 52 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/keys.rs:58— `info!` at line 58 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/keys.rs:189— `info!` at line 189 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/keys.rs:204— `info!` at line 204 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/keys.rs:241— `warn!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/server/session.rs:606— `debug!` at line 606 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/server/session.rs:799— `warn!` at line 799 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/server/session.rs:858— `error!` at line 858 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/server/session.rs:878— `error!` at line 878 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/server/session.rs:885— `error!` at line 885 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/server/session.rs:1587— `info!` at line 1587 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging warpgate-protocol-ssh/src/server/session.rs:1619— `info!` at line 1619 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Orphaned file warpgate-db-migrations/src/m00044_ticket_requests.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file warpgate-db-migrations/src/m00053_login_protection.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file warpgate-sso/src/google_groups.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file warpgate-db-migrations/src/m00054_login_protection_params.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file warpgate-db-migrations/src/m00050_password_policy.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file warpgate-db-migrations/src/m00020_target_groups.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file warpgate-db-migrations/src/m00025_ssh_client_auth.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 24 significant file(s) lose their only recent owner: warpgate-tls/src/rustls_helpers.rs, warpgate-db-entities/src/SessionApprovalRequest.rs, warpgate-protocol-ssh/src/command_detector.rs, warpgate-protocol-rdp/src/clipboard.rs, warpgate-core/src/approvals/gate.rs, warpgate-protocol-mysql/src/client.rs, warpgate-core/src/approvals/wait.rs, warpgate-tls/src/maybe_tls_stream.rs (+16 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: warpgate-database-protocols/src/mysql/protocol/text/column.rs, warpgate-database-protocols/src/error.rs, warpgate-database-protocols/src/mysql/protocol/mod.rs, warpgate-database-protocols/src/mysql/protocol/response/err.rs. Pair on, review, or document these before any departure.
Silent fallback default on Err vendor/sspi/src/kdc.rs:28— `detect_kdc_hosts_from_system` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err warpgate-protocol-kubernetes/src/audit.rs:399— `json_array` turns every `Err` into `"[]".to_owned()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
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/`.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 7 of 284 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; 284 of the 519 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: warpgate-db-migrations/src/m00044_ticket_requests.rs, warpgate-db-migrations/src/m00053_login_protection.rs, warpgate-sso/src/google_groups.rs, warpgate-db-migrations/src/m00054_login_protection_params.rs, warpgate-db-migrations/src/m00050_password_policy.rs, warpgate-db-migrations/src/m00020_target_groups.rs, warpgate-db-migrations/src/m00025_ssh_client_auth.rs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
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.
Duplicated predicate warpgate-core/src/recordings/desktop.rs:477— `st.bytes_since_keyframe >= MAX_GOP_BYTES || (time - st.last_keyframe_time) >= MAX_GOP_SECONDS` appears character-identically in 2 files — warpgate-core/src/recordings/desktop.rs, warpgate-core/src/recordings/terminal.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 1/2 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~0.9 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 3258 source line(s) of the 38 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: warpgate-web/src/admin/index.ts (1), warpgate-web/src/gateway/index.ts (1), warpgate-web/src/gateway/login.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated: aes — `aes` is locked at 0.9.2 but 0.9.3 is the current stable release on crates.io, and it already satisfies the `"0.9"` requirement declared in warpgate-protocol-vnc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aes` and commit the updated REDACTED.
Outdated: aes-gcm — `aes-gcm` is locked at 0.11.0 but 0.11.1 is the current stable release on crates.io, and it already satisfies the `"0.11"` requirement declared in warpgate-common/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aes-gcm` and commit the updated REDACTED.
Outdated: aws-config — `aws-config` is locked at 1.12.0 but 1.13.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-config` and commit the updated REDACTED.
Outdated: aws-credential-types — `aws-credential-types` is locked at 1.3.0 but 1.3.1 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-credential-types` and commit the updated REDACTED.
Outdated: aws-sdk-ec2 — `aws-sdk-ec2` is locked at 1.267.0 but 1.271.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-ec2` and commit the updated REDACTED.
Outdated: aws-sdk-ec2instanceconnect — `aws-sdk-ec2instanceconnect` is locked at 1.115.0 but 1.118.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-ec2instanceconnect` and commit the updated REDACTED.
Outdated: aws-sdk-eks — `aws-sdk-eks` is locked at 1.154.0 but 1.158.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-eks` and commit the updated REDACTED.
Outdated: aws-sdk-rds — `aws-sdk-rds` is locked at 1.154.0 but 1.157.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-rds` and commit the updated REDACTED.
Outdated: aws-sdk-s3 — `aws-sdk-s3` is locked at 1.152.0 but 1.155.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-s3` and commit the updated REDACTED.
Outdated: aws-sdk-sts — `aws-sdk-sts` is locked at 1.119.0 but 1.122.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-sts` and commit the updated REDACTED.
Outdated: aws-sigv4 — `aws-sigv4` is locked at 1.6.0 but 1.6.3 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sigv4` and commit the updated REDACTED.
Outdated: aws-smithy-runtime-api — `aws-smithy-runtime-api` is locked at 1.19.0 but 1.19.1 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-smithy-runtime-api` and commit the updated REDACTED.
Outdated: aws-smithy-types — `aws-smithy-types` is locked at 1.8.1 but 1.9.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-aws/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-smithy-types` and commit the updated REDACTED.
Outdated: bitflags — `bitflags` is locked at 2.13.1 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in warpgate-database-protocols/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.6 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.0"` requirement declared in warpgate-common/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: config — `config` is locked at 0.15.25 but 0.15.27 is the current stable release on crates.io, and it already satisfies the `"0.15"` requirement declared in warpgate/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p config` and commit the updated REDACTED.
Outdated: console — `console` is locked at 0.16.4 but 0.16.6 is the current stable release on crates.io, and it already satisfies the `"0.16"` requirement declared in warpgate/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p console` and commit the updated REDACTED.
Outdated: ecb — `ecb` is locked at 0.2.0 but 0.2.1 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in warpgate-protocol-vnc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ecb` and commit the updated REDACTED.
Outdated: flate2 — `flate2` is locked at 1.1.9 but 1.1.10 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-protocol-mysql/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
Outdated: h2 — `h2` is locked at 0.4.16 but 0.4.20 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in warpgate-protocol-kubernetes/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p h2` and commit the updated REDACTED.
Outdated: ipnet — `ipnet` is locked at 2.12.1 but 2.12.2 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in warpgate-admin/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ipnet` and commit the updated REDACTED.
Outdated: libz-sys — `libz-sys` is locked at 1.1.29 but 1.1.30 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-protocol-rdp/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libz-sys` and commit the updated REDACTED.
Outdated: notify — `notify` is locked at 8.2.0 but 8.2.1 is the current stable release on crates.io, and it already satisfies the `"8.0"` requirement declared in warpgate/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: rand — `rand` is locked at 0.10.2 but 0.10.3 is the current stable release on crates.io, and it already satisfies the `"0.10"` requirement declared in warpgate-common/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rand` and commit the updated REDACTED.
Outdated: rcgen — `rcgen` is locked at 0.14.9 but 0.14.10 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in warpgate-admin/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rcgen` and commit the updated REDACTED.
Off the main sequence: warpgate-common-cache — warpgate-common-cache: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: warpgate-common — warpgate-common: abstractness 0.08, instability 0.21, distance 0.71 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
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 1 file(s) — `warpgate-web/src/common/desktopCanvas.ts` — 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 — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a17cfb-51c2-7915-863a-1c184ed3bc54 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 31 · Warnings: 358 · Recommendations: 69 · Info: 40 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 27-10-2026 @ 10:50 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.