Public report of warp-tech/warpgate, published 14 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 14 November 2026, 17:09 UTC · Survey ID cd_dd961a8bc1064b18b6ed86a9d6b37f29

warp-tech/warpgate

Measured 14 November 2026, 17:09 UTC, at code version 5aca27f

CAI score 57out of 100 At risk Down 3 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: 87,558 lines of product code in 30 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Code Health, 51

Findings by how serious they are

132 critical 455 serious 127 minor

18 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 17:09 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

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. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

78of 78 dimensions measured by tools.
640of 714 findings point to an exact file and line, so you can open each one in the code. The other 74 concern the repository as a whole, such as missing documentation.
78dimensions across 9 lenses, read from 87,558 lines of product code in 30 projects.
Chapters

Executive summary

warp-tech/warpgate is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 57 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.

Code Health, at 51, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is removing the unused code, worth about 3 points. Recording design decisions comes next, worth about 2 points.

Fifty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven pipeline steps install packages that can change without warning, and thirty-nine form fields can't be read by a screen reader. Pinning each tool to an exact version, pinning what the pipeline installs and labelling the form fields would close these risks. Limiting each secret to its own step would fix the seven secrets exposed to more of the pipeline than needed, and updating the vulnerable packages would deal with the six packages with a known security hole. The five sets of files in separate parts that keep changing together need that dependency made explicit.

The product code is 87,558 lines, about €110,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The 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.
Code Health 51 · counts for 45%Security and Compliance 54 · counts for 25%Accessibility 54 · counts for 14%Maturity 67 · counts for 8%Production Readiness 79 · counts for 4%Architecture 92 · counts for 2%Domain Modelling 100 · counts for 1%Event Sourcing 100 · counts for 1%Performance 100 · counts for 0%

The weakest lenses score close to each other, so improving any of them moves the score.

Code composition: what the lines of code are
Product code 83%Tests 17%
New since the last survey: 278 findings

These 278 critical or serious findings weren't in the previous survey, on 27 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · warpgate_protocol_http::common::inject_request_authorization (cyclomatic 16) warpgate-protocol-http/src/common.rs
  • Cognitive Complexity · CommandDetector::extract (cognitive 16) warpgate-protocol-ssh/src/command_detector.rs
  • God Classes · FileTooLong: src/correlator.rs warpgate-protocol-kubernetes/src/correlator.rs
  • Code Duplication · Edited copies of one member (3 members, 47+ corresponding lines) warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs
  • Code Duplication · Edited copy of a member (55 corresponding lines) warpgate-core/src/config_providers/db.rs
  • Code Duplication · Edited copy of a member (66 corresponding lines) warpgate-protocol-mysql/src/lib.rs
  • Code Duplication · Edited copy of a member (47 corresponding lines) warpgate-admin/src/api/certificate_credentials.rs
  • Code Duplication · Edited copy of a member (39 corresponding lines) warpgate-admin/src/api/users.rs
  • Code Duplication · Edited copy of a member (47 corresponding lines) warpgate-web-desktop/src/manager.rs
  • Code Duplication · Edited copy of a member (40 corresponding lines) warpgate-protocol-http/src/api/ticket_requests.rs
  • Code Duplication · Edited copy of a member (41 corresponding lines) warpgate-admin/src/api/public_key_credentials.rs
  • Code Duplication · Edited copy of a member (34 corresponding lines) warpgate-protocol-http/src/api/credentials.rs
  • Code Duplication · Edited copy of a member (31 corresponding lines) warpgate-admin/src/api/otp_credentials.rs
  • Code Duplication · Edited copy of a member (35 corresponding lines) warpgate-db-migrations/src/m00057_password_login_mode.rs
  • Code Duplication · Edited copies of one member (4 members, 31+ corresponding lines) warpgate-admin/src/api/otp_credentials.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) warpgate-core/src/ticket_requests.rs
  • Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) warpgate-db-migrations/src/m00036_user_role_expiry_history.rs
  • Code Duplication · Edited copy of a member (40 corresponding lines) warpgate-db-migrations/src/m00019_rate_limits.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) warpgate-core/src/recordings/traffic.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) warpgate-protocol-http/src/api/ticket_requests.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) warpgate-db-migrations/src/m00049_text_columns.rs
  • Code Duplication · Edited copy of a member (16 corresponding lines) warpgate-admin/src/api/roles.rs
  • Code Duplication · Edited copy of a member (26 corresponding lines) warpgate-db-migrations/src/m00074_encryption_key_rotation.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) warpgate-db-migrations/src/m00072_session_node_id_not_null.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) warpgate-db-migrations/src/m00017_descriptions.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) warpgate-admin/src/api/ticket_requests_detail.rs
  • Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) warpgate-admin/src/api/roles.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) warpgate-core/src/recordings/traffic.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) warpgate-protocol-mysql/src/common.rs
  • Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) warpgate-admin/src/api/admin_roles.rs
  • Code Duplication · Edited copy of a member (16 corresponding lines) warpgate-admin/src/api/roles.rs
  • Code Duplication · Edited copy of a member (17 corresponding lines) warpgate-core/src/resources/roles.rs
  • Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) warpgate-db-migrations/src/m00013_add_openssh_public_key_dates.rs
  • Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) warpgate-admin/src/api/admin_roles.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) warpgate-protocol-mysql/src/session.rs
  • Code Duplication · Edited copy of a member (21 corresponding lines) warpgate-db-migrations/src/m00081_http_session_user_session_id.rs
  • Code Duplication · Edited copy of a member (16 corresponding lines) warpgate-admin/src/api/secret_backends.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) warpgate-aws/src/region.rs
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) warpgate-admin/src/api/recordings_detail.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) warpgate-common/src/eventhub.rs
  • Code Duplication · Edited copies of one member (5 members, 14+ corresponding lines) warpgate-admin/src/api/certificate_credentials.rs
  • Code Duplication · Edited copy of a member (17 corresponding lines) warpgate-protocol-rdp/src/client/tls.rs
  • Code Duplication · Edited copy of a member (17 corresponding lines) warpgate-db-migrations/src/m00020_target_groups.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) warpgate-db-migrations/src/m00052_log_text_column.rs
  • Code Duplication · Edited copy of a member (9 corresponding lines) warpgate-protocol-vnc/src/server/protocol.rs
  • Code Duplication · Edited copy of a member (9 corresponding lines) warpgate-core/src/rate_limiting/registry.rs
  • Code Duplication · Edited copy of a member (8 corresponding lines) warpgate-core/src/recordings/traffic.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) warpgate-protocol-ssh/src/server/session.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) warpgate-core/src/rate_limiting/stream.rs
  • Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) warpgate-db-entities/src/TargetRoleAssignment.rs
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) warpgate-core/src/resources/roles.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) warpgate-db-entities/src/UserAdminRoleAssignment.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) warpgate-db-migrations/src/m00016_fix_public_key_length.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) warpgate-db-migrations/src/m00081_http_session_user_session_id.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) warpgate-db-migrations/src/m00027_ca.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) warpgate-core/src/config_providers/db.rs
  • Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) warpgate-db-migrations/src/m00029_certificate_revocation.rs
  • Code Duplication · Edited copy of a member (10 corresponding lines) warpgate-core/src/logging/json_console.rs
  • Code Duplication · Edited copy of a member (6 corresponding lines) warpgate-core/src/protocols/framebuffer.rs
  • Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs
  • Code Duplication · Edited copy of a member (10 corresponding lines) warpgate-admin/src/main.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs
  • Code Duplication · Edited copy of a member (8 corresponding lines) warpgate-admin/src/api/admin_roles.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) warpgate-admin/src/api/ldap_servers.rs
  • Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) warpgate-admin/src/api/roles.rs
  • Code Duplication · Edited copies of one member (5 members, 12+ corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) warpgate-protocol-http/src/api/common.rs
  • Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) warpgate-db-migrations/src/m00018_ticket_description.rs
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) warpgate-protocol-mysql/src/session.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) warpgate-db-migrations/src/m00072_session_node_id_not_null.rs
  • Code Duplication · Edited copy of a member (9 corresponding lines) warpgate-core/src/resources/roles.rs
  • Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) warpgate-db-migrations/src/m00007_targets_and_roles.rs
  • Code Duplication · Edited copy of a member (7 corresponding lines) warpgate-protocol-rdp/src/client/tls.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) warpgate-protocol-ssh/src/server/session.rs
  • Code Duplication · Edited copy of a member (7 corresponding lines) warpgate-tls/src/maybe_tls_stream.rs
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs
  • Code Duplication · Edited copy of a member (8 corresponding lines) warpgate-admin/src/api/session_approvals.rs
  • Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) warpgate-db-migrations/src/m00037_show_session_menu.rs
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) warpgate-db-migrations/src/m00023_ldap_username_attribute.rs
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) warpgate-admin/src/api/secret_backends.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) warpgate-aws/src/s3.rs
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) warpgate-db-migrations/src/m00031_minimize_password_login.rs
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) warpgate-protocol-ssh/src/server/target_menu.rs
  • Code Duplication · Edited copy of a member (10 corresponding lines) warpgate-protocol-http/src/api/web_desktop.rs
  • Code Duplication · Edited copy of a member (6 corresponding lines) warpgate-protocol-mysql/src/stream.rs
  • Code Duplication · Edited copy of a member (4 corresponding lines) warpgate-core/src/recordings/writer.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) warpgate-common/src/auth/state.rs
  • Code Duplication · Edited copy of a member (10 corresponding lines) warpgate-db-migrations/src/m00061_rename_web_ssh_enabled.rs
  • Code Duplication · Edited copy of a member (10 corresponding lines) warpgate-db-migrations/src/m00061_rename_web_ssh_enabled.rs
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) warpgate-db-migrations/src/m00023_ldap_username_attribute.rs
  • Code Duplication · Edited copy of a member (6 corresponding lines) warpgate-core/src/protocols/terminal_screen.rs
  • Code Duplication · Edited copy of a member (7 corresponding lines) warpgate-protocol-mysql/src/stream.rs
  • Code Duplication · Duplicated block (13 lines × 2) warpgate-protocol-rdp/src/server/mod.rs
  • Code Duplication · Duplicated block (8–12 lines × 2) warpgate-protocol-mysql/src/lib.rs
  • Code Duplication · Duplicated block (11 lines × 2) warpgate-core/src/config_providers/db.rs
  • Code Duplication · Duplicated block (11 lines × 2) warpgate-protocol-mysql/src/lib.rs
  • Code Duplication · Duplicated block (10 lines × 2) warpgate-core/src/config_providers/db.rs
  • Code Duplication · Duplicated block (10 lines × 2) warpgate-protocol-http/src/api/auth.rs
  • Code Duplication · Duplicated block (8–9 lines × 2) warpgate-admin/src/api/certificate_credentials.rs

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 171 findings

These 171 critical or serious findings were in the previous survey, on 27 October 2026, and are gone from this one. The first 100 are listed here.

  • Code Duplication · Duplicated block (8–12 lines × 2) warpgate-protocol-mysql/src/lib.rs
  • Code Duplication · Duplicated block (11 lines × 2) warpgate-core/src/config_providers/db.rs
  • Code Duplication · Duplicated block (10 lines × 2) warpgate-core/src/config_providers/db.rs
  • Code Duplication · Duplicated block (10 lines × 2) warpgate-protocol-http/src/api/auth.rs
  • Code Duplication · Duplicated block (8–9 lines × 2) warpgate-admin/src/api/certificate_credentials.rs
  • Code Duplication · Duplicated block (9 lines × 2) warpgate-common/src/audit.rs
  • Code Duplication · Duplicated block (9 lines × 2) warpgate-common/src/audit.rs
  • Code Duplication · Duplicated block (9 lines × 2) warpgate-protocol-http/src/api/credentials.rs
  • Code Duplication · Duplicated block (8 lines × 6) warpgate-common/src/audit.rs
  • Code Duplication · Duplicated block (8 lines × 3) warpgate-protocol-mysql/src/lib.rs
  • Code Duplication · Duplicated block (8 lines × 2) warpgate-admin/src/api/users.rs
  • Code Duplication · Duplicated block (8 lines × 2) warpgate-admin/src/api/users.rs
  • Code Duplication · Duplicated block (7 lines × 2) warpgate-db-migrations/src/m00075_hash_ticket_and_api_token_secrets.rs
  • Code Duplication · Duplicated block (6 lines × 3) warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs
  • Code Duplication · Duplicated block (11 lines × 2) warpgate-admin/src/api/certificate_credentials.rs
  • Code Duplication · Duplicated block (8 lines × 2) warpgate-protocol-rdp/src/lib.rs
  • Secret Scanning · Leaked secret: hardcoded-credential helm/e2e.sh
  • Secret Scanning · Leaked secret: hardcoded-credential helm/warpgate/values.yaml
  • Churn × Complexity Hotspots · Hotspot: warpgate-common/src/error.rs warpgate-common/src/error.rs
  • Churn × Complexity Hotspots · Hotspot: warpgate-protocol-rdp/src/server/rdp.rs warpgate-protocol-rdp/src/server/rdp.rs
  • Churn × Complexity Hotspots · Hotspot: warpgate-common/src/audit.rs warpgate-common/src/audit.rs
  • Churn × Complexity Hotspots · Hotspot: warpgate-protocol-rdp/src/server/bridge.rs warpgate-protocol-rdp/src/server/bridge.rs
  • Churn × Complexity Hotspots · Hotspot: warpgate-protocol-vnc/src/server/bridge.rs warpgate-protocol-vnc/src/server/bridge.rs
  • Churn × Complexity Hotspots · Hotspot: warpgate-protocol-http/src/catchall.rs warpgate-protocol-http/src/catchall.rs
  • Churn × Complexity Hotspots · Repeated repair: warpgate-core/src/recordings/desktop.rs warpgate-core/src/recordings/desktop.rs
  • Churn × Complexity Hotspots · Repeated repair: warpgate-web-desktop/src/protocol.rs warpgate-web-desktop/src/protocol.rs
  • Explicit Debt · Dead code: RsaToPkcs8String vendor/sspi/tools/aadjoin/AADJoin/Utils/CryptoUtils.cs
  • Explicit Debt · Dead code: Pkcs8ToRsa vendor/sspi/tools/aadjoin/AADJoin/Utils/CryptoUtils.cs
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0387 REDACTED
  • Change Coupling · Boundary-crossing change coupling: client.rs ↔ session.rs warpgate-protocol-mysql/src/client.rs
  • Platform End-of-Life · End-of-life runtime: .NET net6.0 vendor/sspi/tools/aadjoin/UnitTests/UnitTests.csproj
  • Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) warpgate-web/src/admin/config/Parameters.svelte
  • Code Duplication · Duplicated block (7 lines × 2 locations) warpgate-web/src/admin/status/Session.svelte
  • Cyclomatic Complexity · Complex function save (cyclomatic 12, cognitive 11) warpgate-web/src/admin/config/Parameters.svelte
  • 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/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/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
  • Dead Code · Dead file (~314 LoC) warpgate-web/src/admin/config/users/User.svelte
  • Dead Code · Dead file (~198 LoC) warpgate-web/src/gateway/TicketRequests.svelte
  • Dead Code · Dead file (~193 LoC) warpgate-web/src/common/ItemList.svelte
  • Dead Code · Dead file (~172 LoC) warpgate-web/src/admin/config/Parameters.svelte
  • Dead Code · Dead file (~159 LoC) warpgate-web/src/gateway/TargetList.svelte
  • Dead Code · Dead file (~148 LoC) warpgate-web/src/admin/config/ldap/LdapServer.svelte
  • Dead Code · Dead file (~142 LoC) warpgate-web/src/admin/config/AdminRole.svelte
  • Dead Code · Dead file (~140 LoC) warpgate-web/src/admin/config/targets/CreateTarget.svelte
  • Dead Code · Dead file (~126 LoC) warpgate-web/src/admin/config/targets/Target.svelte
  • Dead Code · Dead file (~105 LoC) warpgate-web/src/admin/App.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 (~92 LoC) warpgate-web/src/admin/config/secret-backends/SecretBackendModal.svelte
  • Dead Code · Dead file (~91 LoC) warpgate-web/src/admin/config/targets/ssh/Options.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/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 (~79 LoC) warpgate-web/src/admin/config/targets/Targets.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/CreateApiTokenModal.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 (~67 LoC) warpgate-web/src/common/groups.ts
  • 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 (~52 LoC) warpgate-web/src/gateway/ApiTokenManager.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 (~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 (~41 LoC) warpgate-web/src/admin/config/targets/ChooseTargetKind.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/target-groups/TargetGroups.svelte
Rebuild cost: about €110,000 · Estimate
Cost to rebuild€36,000 to €180,000, for 601 to 1,905 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problemStandard, 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 57. 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.
SizeMedium: 87,558 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
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 3 points · Medium effort · Dead Code
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 2 points · Low effort · ADR Quality
3
Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off.
This repository constructs a TLS client that accepts any certificate at 3 sites, not one: `warpgate-protocol-rdp/src/client/tls.rs:129` (a rustls `ServerCertVerifier` that accepts every certificate (`NoCertificateVerification`)), `warpgate-protocol-rdp/src/client/tls.rs:264` (`set_verify(SslVerifyMode::NONE`), `warpgate/src/commands/healthcheck.rs:16` (`.danger_accept_invalid_certs(true)`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Raises the score by about 3 points · Medium effort · Web-Security Posture

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Code Health, at 51 (Adequate). 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 3 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

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.

arch warpgate warpgate warpgate-admin (Cargo) warpgate-admin (Cargo) warpgate->warpgate-admin (Cargo) warpgate-ca warpgate-ca warpgate->warpgate-ca warpgate-common warpgate-common warpgate->warpgate-common warpgate-core warpgate-core warpgate->warpgate-core warpgate-db-entities warpgate-db-entities warpgate->warpgate-db-entities warpgate-protocol-http warpgate-protocol-http warpgate->warpgate-protocol-http warpgate-protocol-kubernetes warpgate-protocol-kubernetes warpgate->warpgate-protocol-kubernetes warpgate-protocol-mysql warpgate-protocol-mysql warpgate->warpgate-protocol-mysql warpgate-protocol-postgres warpgate-protocol-postgres warpgate->warpgate-protocol-postgres warpgate-protocol-rdp warpgate-protocol-rdp warpgate->warpgate-protocol-rdp warpgate-protocol-ssh warpgate-protocol-ssh warpgate->warpgate-protocol-ssh warpgate-protocol-vnc warpgate-protocol-vnc warpgate->warpgate-protocol-vnc warpgate-tls warpgate-tls warpgate->warpgate-tls warpgate-aws warpgate-aws warpgate-admin (Cargo)->warpgate-aws warpgate-admin (Cargo)->warpgate-ca warpgate-admin (Cargo)->warpgate-common warpgate-common-http warpgate-common-http warpgate-admin (Cargo)->warpgate-common-http warpgate-admin (Cargo)->warpgate-core warpgate-admin (Cargo)->warpgate-db-entities warpgate-admin (Cargo)->warpgate-protocol-kubernetes warpgate-admin (Cargo)->warpgate-protocol-ssh warpgate-admin (Cargo)->warpgate-tls warpgate-common->warpgate-aws warpgate-common->warpgate-ca warpgate-common->warpgate-tls warpgate-common-http->warpgate-ca warpgate-common-http->warpgate-common warpgate-common-http->warpgate-core warpgate-common-http->warpgate-db-entities warpgate-common-http->warpgate-tls warpgate-core->warpgate-aws warpgate-core->warpgate-ca warpgate-core->warpgate-common warpgate-core->warpgate-db-entities warpgate-core->warpgate-tls warpgate-db-entities->warpgate-aws warpgate-db-entities->warpgate-common warpgate-db-entities->warpgate-tls warpgate-desktop-auth warpgate-desktop-auth warpgate-desktop-auth->warpgate-common warpgate-desktop-auth->warpgate-common-http warpgate-desktop-auth->warpgate-core warpgate-protocol-http->warpgate-admin (Cargo) warpgate-protocol-http->warpgate-aws warpgate-protocol-http->warpgate-ca warpgate-protocol-http->warpgate-common warpgate-protocol-http->warpgate-common-http warpgate-protocol-http->warpgate-core warpgate-protocol-http->warpgate-db-entities warpgate-protocol-http->warpgate-tls warpgate-web-clients-common warpgate-web-clients-common warpgate-protocol-http->warpgate-web-clients-common warpgate-web-desktop warpgate-web-desktop warpgate-protocol-http->warpgate-web-desktop warpgate-web-ssh warpgate-web-ssh warpgate-protocol-http->warpgate-web-ssh warpgate-protocol-kubernetes->warpgate-aws warpgate-protocol-kubernetes->warpgate-ca warpgate-protocol-kubernetes->warpgate-common warpgate-protocol-kubernetes->warpgate-common-http warpgate-protocol-kubernetes->warpgate-core warpgate-protocol-kubernetes->warpgate-db-entities warpgate-protocol-kubernetes->warpgate-tls warpgate-protocol-mysql->warpgate-aws warpgate-protocol-mysql->warpgate-common warpgate-protocol-mysql->warpgate-common-http warpgate-protocol-mysql->warpgate-core warpgate-protocol-mysql->warpgate-tls warpgate-protocol-postgres->warpgate-aws warpgate-protocol-postgres->warpgate-common warpgate-protocol-postgres->warpgate-common-http warpgate-protocol-postgres->warpgate-core warpgate-protocol-postgres->warpgate-db-entities warpgate-protocol-postgres->warpgate-tls warpgate-protocol-rdp->warpgate-common warpgate-protocol-rdp->warpgate-core warpgate-protocol-rdp->warpgate-db-entities warpgate-protocol-rdp->warpgate-desktop-auth warpgate-protocol-rdp->warpgate-tls warpgate-protocol-ssh->warpgate-aws warpgate-protocol-ssh->warpgate-common warpgate-protocol-ssh->warpgate-common-http warpgate-protocol-ssh->warpgate-core warpgate-protocol-ssh->warpgate-db-entities warpgate-protocol-ssh->warpgate-tls warpgate-protocol-vnc->warpgate-common warpgate-protocol-vnc->warpgate-common-http warpgate-protocol-vnc->warpgate-core warpgate-protocol-vnc->warpgate-db-entities warpgate-protocol-vnc->warpgate-desktop-auth warpgate-protocol-vnc->warpgate-tls warpgate-tls->warpgate-ca warpgate-web-clients-common->warpgate-common warpgate-web-clients-common->warpgate-common-http warpgate-web-clients-common->warpgate-core warpgate-web-clients-common->warpgate-db-entities warpgate-web-desktop->warpgate-common warpgate-web-desktop->warpgate-common-http warpgate-web-desktop->warpgate-core warpgate-web-desktop->warpgate-db-entities warpgate-web-desktop->warpgate-protocol-rdp warpgate-web-desktop->warpgate-protocol-vnc warpgate-web-desktop->warpgate-web-clients-common warpgate-web-ssh->warpgate-common warpgate-web-ssh->warpgate-common-http warpgate-web-ssh->warpgate-core warpgate-web-ssh->warpgate-db-entities warpgate-web-ssh->warpgate-protocol-ssh warpgate-web-ssh->warpgate-web-clients-common __more__ +10 more projects

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.

566 modules, with 781 dependencies between them. 10 loops run through 21 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 526 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.
uses →1 ironrdp_connector2 warpgate_common.secrets3 warpgate_common.state4 warpgate_common.types.aliases5 warpgate_common.types.listen_endpoint6 warpgate_common.types.secret7 warpgate_core.protocols.desktop8 warpgate_database_protocols.io.encode9 warpgate_database_protocols.mysql.protocol.capabilities10 warpgate_db_entities.AdminRole11 warpgate_sso.config12 warpgate_tls.cert13 ironrdp_server.display14 warpgate_common.auth.cred15 warpgate_common.config.target16 warpgate_core.protocols17 warpgate_core.recordings18 warpgate_protocol_ssh.server.channel_registry19 ironrdp_server.server20 warpgate_common.config21 warpgate_core.recordings.desktop22 warpgate_db_entities.Target23 warpgate_common.auth.state24 warpgate_core.config_providers25 warpgate_core.auth_state_store26 warpgate_core.protocols.handle27 warpgate_core.state28 warpgate_core.services29 warpgate_common_http.auth30 warpgate_desktop_auth31 warpgate_protocol_mysql.session32 warpgate_protocol_ssh.client33 warpgate_protocol_vnc.server34 warpgate_admin.api.admin_scheme35 warpgate_protocol_http.api.auth_scheme36 warpgate_protocol_ssh.server.session37 warpgate_web_clients_common38 warpgate_protocol_http.api.auth39 warpgate_web_desktop.session40 warpgate_web_ssh.session
1 ironrdp_connector
2 warpgate_common.secrets
3 warpgate_common.state
4 warpgate_common.types.aliases
5 warpgate_common.types.listen_endpoint
6 warpgate_common.types.secret
7 warpgate_core.protocols.desktop
8 warpgate_database_protocols.io.encode
9 warpgate_database_protocols.mysql.protocol.capabilities
10 warpgate_db_entities.AdminRole
11 warpgate_sso.config
12 warpgate_tls.cert
13 ironrdp_server.display1
14 warpgate_common.auth.cred1
15 warpgate_common.config.target1911
16 warpgate_core.protocols11
17 warpgate_core.recordings212
18 warpgate_protocol_ssh.server.channel_registry2
19 ironrdp_server.server144
20 warpgate_common.config1741231
21 warpgate_core.recordings.desktop52
22 warpgate_db_entities.Target1
23 warpgate_common.auth.state461
24 warpgate_core.config_providers3111514
25 warpgate_core.auth_state_store3231
26 warpgate_core.protocols.handle42132
27 warpgate_core.state4111
28 warpgate_core.services1211111212
29 warpgate_common_http.auth11111
30 warpgate_desktop_auth211211
31 warpgate_protocol_mysql.session111121
32 warpgate_protocol_ssh.client231113
33 warpgate_protocol_vnc.server111111
34 warpgate_admin.api.admin_scheme241
35 warpgate_protocol_http.api.auth_scheme15
36 warpgate_protocol_ssh.server.session3221122213
37 warpgate_web_clients_common411211
38 warpgate_protocol_http.api.auth1122121
39 warpgate_web_desktop.session1311112
40 warpgate_web_ssh.session2211112
Uses a module listed above itPart of a loopThe module itself
1 ironrdp_connector2 warpgate_common.secrets3 warpgate_common.state4 warpgate_common.types.aliases5 warpgate_common.types.listen_endpoint6 warpgate_common.types.secret7 warpgate_core.protocols.desktop8 warpgate_database_protocols.io.encode9 warpgate_database_protocols.mysql.protocol.capabilities10 warpgate_db_entities.AdminRole11 warpgate_sso.config12 warpgate_tls.cert13 ironrdp_server.display14 warpgate_common.auth.cred15 warpgate_common.config.target16 warpgate_core.protocols17 warpgate_core.recordings18 warpgate_protocol_ssh.server.channel_registry19 ironrdp_server.server20 warpgate_common.config21 warpgate_core.recordings.desktop22 warpgate_db_entities.Target23 warpgate_common.auth.state24 warpgate_core.config_providers25 warpgate_core.auth_state_store26 warpgate_core.protocols.handle27 warpgate_core.state28 warpgate_core.services29 warpgate_common_http.auth30 warpgate_desktop_auth31 warpgate_protocol_mysql.session32 warpgate_protocol_ssh.client33 warpgate_protocol_vnc.server34 warpgate_admin.api.admin_scheme35 warpgate_protocol_http.api.auth_scheme36 warpgate_protocol_ssh.server.session37 warpgate_web_clients_common38 warpgate_protocol_http.api.auth39 warpgate_web_desktop.session40 warpgate_web_ssh.sessionironrdp_connector1warpgate_common.secrets2warpgate_common.state3warpgate_common.types.aliases4warpgate_common.types.listen_endpoint5warpgate_common.types.secret6warpgate_core.protocols.desktop7warpgate_database_protocols.io.encode8warpgate_database_protocols.mysql.protocol.capabilities9warpgate_db_entities.AdminRole10warpgate_sso.config11warpgate_tls.cert12ironrdp_server.display13warpgate_common.auth.cred14warpgate_common.config.target15warpgate_core.protocols16warpgate_core.recordings17warpgate_protocol_ssh.server.channel_registry18ironrdp_server.server19warpgate_common.config20warpgate_core.recordings.desktop21warpgate_db_entities.Target22warpgate_common.auth.state23warpgate_core.config_providers24warpgate_core.auth_state_store25warpgate_core.protocols.handle26warpgate_core.state27warpgate_core.services28warpgate_common_http.auth29warpgate_desktop_auth30warpgate_protocol_mysql.session31warpgate_protocol_ssh.client32warpgate_protocol_vnc.server33warpgate_admin.api.admin_scheme34warpgate_protocol_http.api.auth_scheme35warpgate_protocol_ssh.server.session36warpgate_web_clients_common37warpgate_protocol_http.api.auth38warpgate_web_desktop.session39warpgate_web_ssh.session40111911112122144174123152146131115143231421324111121111121211111211211111121231113111111241153221122213411211112212113111122211112+526 more modules (most-connected shown)

At a glance — Code Health · 51% · Adequate · gated by R7 ·

At a glance — Architecture · 92% · Exemplary ·

At a glance — Maturity · 67% · Adequate · gated by M2 ·

At a glance — Readiness · 79% · Strong ·

At a glance — Security · 54% · Adequate · gated by D29, S1 ·

At a glance — Domain Modelling · 100% · Exemplary ·

At a glance — Event Sourcing · 100% · Exemplary ·

At a glance — Accessibility · 54% · Adequate ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection75High / Critical
A03:2025 — Software Supply Chain Failures29High / Critical
A02:2025 — Security Misconfiguration23High / Critical

Roadmap

Top priorities: Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 3 sites, not one: `warpgate-protocol-rdp/src/client/tls.rs:129` (a rustls `ServerCertVerifier` that accepts every certificate (`NoCertificateVerification`)), `warpgate-protocol-rdp/src/client/tls.rs:264` (`set_verify(SslVerifyMode::NONE`), `warpgate/src/commands/healthcheck.rs:16` (`.danger_accept_invalid_certs(true)`). Each is a separate decision — fixing only the line this row cites leaves the others in place; Interpolated log message defeats structured logging.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.+3.4 ptsMediumDead Code
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.+1.6 ptsLowADR Quality
Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 3 sites, not one: `warpgate-protocol-rdp/src/client/tls.rs:129` (a rustls `ServerCertVerifier` that accepts every certificate (`NoCertificateVerification`)), `warpgate-protocol-rdp/src/client/tls.rs:264` (`set_verify(SslVerifyMode::NONE`), `warpgate/src/commands/healthcheck.rs:16` (`.danger_accept_invalid_certs(true)`). Each is a separate decision — fixing only the line this row cites leaves the others in place.+2.6 ptsMediumWeb-Security Posture
Interpolated log message defeats structured logging+1.9 ptsMediumStructured logging
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 `?`).+1.6 ptsMediumNullable reference types
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.+1.4 ptsMediumArchitecture documentation
Resolve the 1 No network policy finding(s) in Network Egress Confinement.+0.6 ptsLowNetwork Egress Confinement
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+1.2 ptsMediumForms & labels

File quality

Per-file score 0–10 — a quality signature. Of 167 files carrying findings, judged against the Preview bar: 2% slop · 12% mixed · 86% near-clean.

FileScoreBandWorst signal
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED0.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedDependency Vulnerabilities: Medium advisory (unmaintained): REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
warpgate-protocol-mysql/src/lib.rs5.2MixedChange Coupling: Boundary-crossing change coupling: lib.rs ↔ lib.rs
warpgate-admin/src/api/parameters.rs5.4MixedChange Coupling: Boundary-crossing change coupling: parameters.rs ↔ lib.rs
REDACTED5.7MixedStatic Analysis (SAST): High: REDACTED
warpgate-protocol-mysql/src/session.rs5.8MixedChange Coupling: Boundary-crossing change coupling: session.rs ↔ session.rs
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
warpgate-protocol-ssh/src/server/session.rs6.0MixedExplicit Debt: HackComment

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 132

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 — 455

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 — 127

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 18

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 78 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 78 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D16D17D19D20D23D24D26D28D29D30D31D34D35D36D37D40D41D43AC1AC2AC3AC4AC5AC6AX10AX3AX4AX8AX9C1C4DM1DM2DM4DM6ES1ES2M1M2M3M4P1P10P2P3P4P5P6PF3R1R10R2R3R5R6R7R8R9S1X1X14X15X2X21X29X30X4X5

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
  1. 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, 640 of 714 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1db08-ab23-7996-a022-83fd24677f53.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py, .rs) and this repository declares a Python test suite (tests, 77 test files), but it was not re-run: its dependency install could not be served by 172.31.7.1 (pip: No matching distribution found for openapi-client (unavailable)), so its suite was not run against dependencies it does not declare. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
  • AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 116 further occurrence(s) are not listed individually; the score already reflects all 156.
  • AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • C1 Data Protection — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • C4 Data Retention — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust, Svelte components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust, Svelte components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 122 further occurrence(s) are not listed individually; the score already reflects all 162.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 145 further occurrence(s) are not listed individually; the score already reflects all 185.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • 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.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • 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.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • 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.

Dimensions

D1 · Cyclomatic Complexity7.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Prevented

23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ServerSession::handle_remote_event at 47. A further 13 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. 7 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 2 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.

ServerSession::handle_remote_event (cyclomatic 47) · ×3warpgate-protocol-ssh/src/server/session.rs:1261
warpgate_protocol_rdp::server::control_loop (cyclomatic 34) · ×2warpgate-protocol-rdp/src/server/mod.rs:209
warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner (cyclomatic 25) · ×2warpgate-protocol-kubernetes/src/server/handlers.rs:294
warpgate::commands::run::command (cyclomatic 23) · ×2warpgate/src/commands/run.rs:62
warpgate_protocol_vnc::server::bridge::run_proxy_session (cyclomatic 20) · ×2warpgate-protocol-vnc/src/server/bridge.rs:108

+ 11 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity6.3 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.3 / 10 · rule-coverage 100% · ceiling Prevented

49 method(s) exceeded the cognitive complexity threshold of 15; the worst was warpgate_protocol_rdp::server::control_loop at 78.

ServerSession::handle_remote_event (cognitive 61) · ×5warpgate-protocol-ssh/src/server/session.rs:1261
warpgate_protocol_rdp::server::control_loop (cognitive 78) · ×4warpgate-protocol-rdp/src/server/mod.rs:209
warpgate_protocol_kubernetes::server::handlers::_handle_normal_request_inner (cognitive 36) · ×4warpgate-protocol-kubernetes/src/server/handlers.rs:294
warpgate_core::db_auth::authorize_user (cognitive 40) · ×3warpgate-core/src/db_auth.rs:189
warpgate_protocol_vnc::client::run (cognitive 34) · ×3warpgate-protocol-vnc/src/client.rs:164

+ 24 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.3 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Prevented

44 god class(es) detected.

MethodTooLong: AuditEvent.emit · ×12warpgate-common/src/audit.rs:223
FileTooLong: server/session.rs · ×11warpgate-protocol-ssh/src/server/session.rs
FunctionTooLong: warpgate_protocol_rdp::server::control_loop · ×11warpgate-protocol-rdp/src/server/mod.rs:209
ClassTooLong: ServerSession · ×5warpgate-protocol-ssh/src/server/session.rs:134
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

  1. 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).
  2. Resolve the 11 FileTooLong finding(s) in God Classes — start with mod.rs (3), session.rs, db.rs. — One of this dimension's main actionable groups (11 warning-level).
  3. 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).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication7.8 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.8 / 10 · rule-coverage 100% · ceiling Verified

85 duplicated block group(s) detected. 5.5 % of the production lines (4,790 of 87,558) are in a reported copy. A further 92 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (10 lines × 2) · ×13warpgate-common/src/eventhub.rs:56
Duplicated block (13 lines × 2) · ×8warpgate-admin/src/api/otp_credentials.rs:153
Duplicated block (8 lines × 2) · ×7warpgate-admin/src/api/ldap_servers.rs:348
Edited copy of a member (14 corresponding lines) · ×5warpgate-core/src/recordings/traffic.rs:147
Edited copy of a member (13 corresponding lines) · ×5warpgate-protocol-mysql/src/common.rs:9

+ 79 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. Resolve the 8 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with otp_credentials.rs, client.rs, mod.rs. — One of this dimension's main actionable groups (8 warning-level).
  3. 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).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 6.3 / 10 · rule-coverage 100% · ceiling Prevented

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

  1. Resolve the 9 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 1 Unstable project warpgate-admin (Cargo) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project warpgate-protocol-kubernetes finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 135 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D12 · Dependency Hygiene8.0 7.8 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 7.8 / 10 · rule-coverage 97% · ceiling Verified

42 outdated, 0 yanked direct Cargo dependencies. 148 of 152 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 · ×42

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets. 2 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 870 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json and 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.8 / 10Stronggated by 16 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: warpgate-protocol-ssh/src/server/session.rs (24×47=1128); warpgate-protocol-rdp/src/client/mod.rs (20×26=520); warpgate-protocol-kubernetes/src/server/handlers.rs (13×25=325) Repeated repair below the complexity floor: warpgate-web/src/gateway/WebDesktop.svelte (3 of 5 changes were fixes)

Hotspot: warpgate-protocol-ssh/src/server/session.rs · ×15warpgate-protocol-ssh/src/server/session.rs:1261
Repeated repair: warpgate-web/src/gateway/WebDesktop.sveltewarpgate-web/src/gateway/WebDesktop.svelte:138

What to do

  1. Resolve the 15 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (3), client.rs (2), session.rs. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with WebDesktop.svelte. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D16 · Bus Factor9.2 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Documented

21 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is warpgate-core/src/recordings/tests.rs. Counted over 286 of the 523 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Stronggated by 12 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

12 deducted task-comment markers across 87558 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×8warpgate-protocol-ssh/src/client/mod.rs:1209
HackComment · ×3warpgate-protocol-ssh/src/server/session.rs:198
FixmeCommentwarpgate-database-protocols/src/mysql/protocol/packet.rs:34

What to do

  1. Resolve the 8 TodoComment finding(s) in Explicit Debt — start with mod.rs, common.rs, err.rs. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 3 HackComment finding(s) in Explicit Debt — start with session.rs (2), common.rs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with packet.rs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 5 document(s) read across 2 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundwarpgate-protocol-http/src/main.rs:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

No domain types leak across context boundaries (3 contexts). Contexts: warpgate-core, warpgate-desktop-auth, warpgate-protocol-ssh.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 96 judged comments only repeat the code they sit on (0.0 %).

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion8.2 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Documented

3 of 29 build units (Cargo, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.5 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 0.5 / 10 · rule-coverage 100% · ceiling Documented

75 finding(s): 0 critical, 72 high, 3 medium, 0 low. 56 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 14 file(s) — `helm/warpgate/templates/configmap.yaml`, `REDACTED`, `helm/warpgate/templates/extra-manifests.yaml`, `helm/warpgate/templates/httproute.yaml`, `helm/warpgate/templates/ingress.yaml`, … (+9 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 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

+ 4 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
  3. No action in Static Analysis (SAST) — all 56 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 (56 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities3.8 / 10Weak✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 3.8 / 10 · rule-coverage 100% · ceiling Documented

24 finding(s): 3 critical, 3 high, 9 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  2. 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).
  3. Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D31 · IaC & Container Security7.3 / 10Adequategated by 5 critical findings✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 7.3 / 10 · rule-coverage 100% · ceiling Documented

23 finding(s): 0 critical, 5 high, 8 medium, 10 low.

REDACTED
REDACTED
REDACTED

What to do

  1. 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).
  2. 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).
  3. 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.

D34 · Knowledge Freshness9.7 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

7 of 286 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 286 of the 523 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×7warpgate-db-migrations/src/m00044_ticket_requests.rs:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling9.8 / 10Adequategated by 5 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: parameters.rs↔lib.rs 86%; lib.rs↔lib.rs 69%; handler.rs↔russh_handler.rs 62%

Boundary-crossing change coupling: parameters.rs ↔ lib.rs · ×5warpgate-admin/src/api/parameters.rs:1
Change coupling: handler.rs ↔ russh_handler.rs · ×2warpgate-protocol-ssh/src/client/handler.rs:1

What to do

  1. Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with parameters.rs, lib.rs, auth_state_store.rs. — One of this dimension's main actionable groups (5 issue-level).
  2. 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.

D36 · Supply-chain Provenance & Signing7.5 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.5 / 10 · rule-coverage 100% · ceiling Documented

3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. 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).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. 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.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D40 · Network Egress Confinement6.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Documented

0/2 network-egress controls present (network policy, egress restriction).

No network policy

What to do

  1. Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d40_recommendation.md · top locations in Appendix A, every location in findings.md.

D41 · Kernel & Syscall Confinement6.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Documented

No workload manifest could be read as a pod spec, so no confinement was judged.

Detailed fixes: d41_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives4.3 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:253, warpgate-web/src/gateway/WebDesktop.svelte:541

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels4.1 / 10Weak✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×32) — warpgate-web/src/admin/CertificateCredentialModal.svelte:174, warpgate-web/src/admin/CreateOtpModal.svelte:162, warpgate-web/src/admin/Log.svelte:53, …
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×7) — warpgate-web/src/admin/CreatePasswordModal.svelte:65, warpgate-web/src/admin/PublicKeyCredentialModal.svelte:95, warpgate-web/src/admin/config/ClientKeyModal.svelte:98, …
  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — warpgate-web/src/admin/config/Policies.svelte:87

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.5 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×9) — warpgate-web/src/admin/config/AccessRole.svelte:145, warpgate-web/src/admin/config/AdminRole.svelte:165, warpgate-web/src/admin/config/Tickets.svelte:102, …
  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — warpgate-web/src/admin/status/KubernetesRecording.svelte:144

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics4.8 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • This <canvas> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its only behaviour is bound to mousedown, mouseup, mousemove and wheel, pointer gestures a keyboard cannot produce, and there is no key handler. The tab stop leads nowhere. Bind the same behaviour to a key handler, or provide an equivalent control elsewhere. Give it a role as well, so assistive tech can announce what it is. — warpgate-web/src/gateway/WebDesktop.svelte:541

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AX10 · Code composition8.3 / 10Strong✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

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.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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.

C1 · Data Protection8.5 / 10Strong✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

What to do

  • Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps.
C4 · Data Retention7.5 / 10Strong✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept.

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

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.

DM2 · Strongly-typed ids10.0 / 10Exemplary✓ Tool-verified

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.

DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ 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.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

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.

ES1 · Fold determinism10.0 / 10Exemplary✓ Tool-verified

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.

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

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.

M1 · Documentation (README)7.5 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

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.

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).
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

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.

R10 · Code Duplication8.5 / 10Strong✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. 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/Policies.svelte:12 · warpgate-web/src/admin/config/parameters/ParametersForm.svelte:39 — 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/config/Policies.svelte:12
  • 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:90 — 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:29 · warpgate-web/src/admin/config/AccessRole.svelte:45 — 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:29
  • warpgate-web/src/admin/config/AccessRole.svelte:64 · warpgate-web/src/admin/config/AdminRole.svelte:129 · warpgate-web/src/admin/config/targets/Target.svelte:83 — 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:64
  • warpgate-web/src/admin/config/AccessRoles.svelte:21 · warpgate-web/src/admin/config/target-groups/TargetGroups.svelte:26 · 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/config/AccessRole.svelte:13 · warpgate-web/src/admin/config/AdminRole.svelte:18 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — warpgate-web/src/admin/config/AccessRole.svelte:13
  • warpgate-web/src/admin/config/ldap/LdapServer.svelte:18 · warpgate-web/src/admin/config/ldap/LdapUserBrowser.svelte:15 — the two spans are one implementation copied and then locally edited — 54 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/ldap/LdapServer.svelte:18
  • 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.
R2 · Cyclomatic Complexity9.0 / 10Exemplary✓ Tool-verified

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
  • (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
  • save has cyclomatic complexity 11 and cognitive complexity 10; 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/ParametersForm.svelte:63
R3 · Large Files7.7 / 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/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 689 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 589 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/TargetList.svelte has 459 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
  • warpgate-web/src/gateway/TicketRequests.svelte has 431 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 404 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

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R5 · Dependency Freshness10.0 / 10Exemplary✓ Tool-verified

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.

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.

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/Manage.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 (×4) — warpgate-web/src/admin/config/users/User.svelte, warpgate-web/src/admin/config/AdminRole.svelte, warpgate-web/src/admin/config/targets/CreateTarget.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 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 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 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/TargetList.svelte, warpgate-web/src/gateway/TicketRequests.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/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 (×2) — warpgate-web/src/admin/status/Requests.svelte, warpgate-web/src/admin/status/Sessions.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 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 — warpgate-web/src/admin/config/ldap/LdapServer.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/ParametersForm.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 — warpgate-web/src/admin/lib/SectionedForm.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/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
  • 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/Network.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 — 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/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

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene7.5 / 10Strong✓ Tool-verified

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. (×5)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

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.

S1 · Web-Security Posture2.0 / 10Critical✓ Tool-verified

Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository builds on an HTTP-server crate (`poem` (Cargo.toml)) but serves no HTTP of its own: its production source starts no server (no `HttpServer::new`, `axum::serve`, `Server::bind`, tonic `Server::builder()…serve`, `rocket::build()`, `warp::serve`, `serve_connection` or the like — its examples and tests are not production source), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • a rustls `ServerCertVerifier` that accepts every certificate (`NoCertificateVerification`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on. (×3) — warpgate-protocol-rdp/src/client/tls.rs:129, warpgate-protocol-rdp/src/client/tls.rs:264, warpgate/src/commands/healthcheck.rs:16
  • `set_min_proto_version(SslVersion::TLS1)` explicitly admits a protocol version that is broken (SSL 3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Remove the pin: reqwest, native-tls and openssl negotiate the highest version both sides support, and rustls implements only TLS 1.2 and 1.3 — so naming no older version is the strongest setting. Where a floor must be named, use `min_tls_version(tls::Version::TLS_1_2)` / `set_min_proto_version(Some(SslVersion::TLS1_2))`. — warpgate-protocol-rdp/src/client/tls.rs:244
  • MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×4) — warpgate-protocol-mysql/src/common.rs:10, warpgate-protocol-mysql/src/common.rs:11, warpgate-protocol-mysql/src/common.rs:13, …

What to do

  • Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 3 sites, not one: `warpgate-protocol-rdp/src/client/tls.rs:129` (a rustls `ServerCertVerifier` that accepts every certificate (`NoCertificateVerification`)), `warpgate-protocol-rdp/src/client/tls.rs:264` (`set_verify(SslVerifyMode::NONE`), `warpgate/src/commands/healthcheck.rs:16` (`.danger_accept_invalid_certs(true)`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
  • Drop SSL 3.0 and TLS 1.0/1.1: remove the `min_tls_version`/`set_min_proto_version` pin naming them, or set TLS 1.2 explicitly — or move the client to rustls, which offers nothing older.
  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 4 sites, not one: `warpgate-protocol-mysql/src/common.rs:10` (`Sha1::digest`), `warpgate-protocol-mysql/src/common.rs:11` (`Sha1::digest`), `warpgate-protocol-mysql/src/common.rs:13` (`Sha1::digest`), `warpgate-protocol-vnc/src/server/rfb.rs:235` (`Md5::digest`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

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.

X2 · Cancellation propagation10.0 / 10Exemplary○ Nothing flagged

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.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

X4 · Structured logging4.6 / 10Weak✓ Tool-verified

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 2089 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:2089
  • `info!` at line 2143 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:2143
  • `info!` at line 2181 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:2181
  • `warn!` at line 2476 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:2476
  • `info!` at line 2502 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:2502
  • `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

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types5.8 / 10Adequate✓ Tool-verified

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 3323 source line(s) of the 40 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. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

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 `?`).

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

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.

LensScoreRatingImpact
Code Health51%Adequate — gated by R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture92%ExemplarySolid.
Maturity67%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness79%StrongSolid.
Security54%Adequate — gated by D29, S1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100%ExemplaryStrongest area.
Event Sourcing100%ExemplarySolid.
Accessibility54%AdequateAcceptable, with room to improve.
Performance100%ExemplarySolid.
Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a struct, Diesel table, SeaORM entity or SQL migration table named for it — a SeaORM ActiveModelBehavior hook or database trigger that records each change, or an event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 53 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — AX6 reached only 21% of this repository's production lines — rust (84,587 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • D10 Test Quality — ~18521 lines of test source are present (.py, .rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .py suite was found but not re-run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
  • 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
  • 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.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — Rust suite
  • 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
  • DM5 Encapsulated state — this Rust crate declares no type implementing a hand-rolled Hash/PartialEq, so DM5's value-identity encapsulation read has no population to be taken over
  • DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — 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.
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
  • 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R4 Test Coverage — 1 test file(s) reach none of 174 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X12 Unreachable branch — X12 reached only 21% of this repository's production lines — rust (84,587 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — X16 reached only 21% of this repository's production lines — rust (84,587 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X17 Uncapped recursion over a caller-supplied document — X17 reached only 21% of this repository's production lines — rust (84,587 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — X24 reached only 21% of this repository's production lines — rust (84,587 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.
  • X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — X3 reached only 21% of this repository's production lines — rust (84,587 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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.

Critical — 132 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 31 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×34
  • <input> without a programmatic label warpgate-web/src/admin/CertificateCredentialModal.svelte:174 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/CreateOtpModal.svelte:162 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/CreatePasswordModal.svelte:65 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label warpgate-web/src/admin/Log.svelte:53 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/PublicKeyCredentialModal.svelte:83 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/PublicKeyCredentialModal.svelte:95 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label warpgate-web/src/admin/SsoCredentialModal.svelte:60 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/SsoCredentialModal.svelte:72 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/TlsConfiguration.svelte:25 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/AccessRole.svelte:93 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/AccessRole.svelte:97 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/AdminRole.svelte:158 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/AdminRole.svelte:162 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/ClientKeyModal.svelte:68 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/ClientKeyModal.svelte:77 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/ClientKeyModal.svelte:98 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label warpgate-web/src/admin/config/ClientKeyModal.svelte:110 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/CreateAdminRole.svelte:39 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/CreateAdminRole.svelte:43 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/CreateRole.svelte:39 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/CreateTicket.svelte:128 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label warpgate-web/src/admin/config/CreateTicket.svelte:137 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/CreateTicket.svelte:145 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/CreateUser.svelte:42 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label warpgate-web/src/admin/config/GenerateClientKeyModal.svelte:57 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • + 9 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×5
  • <select> without a programmatic label warpgate-web/src/admin/TlsConfiguration.svelte:16 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label warpgate-web/src/admin/config/CreateTicket.svelte:105 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label warpgate-web/src/admin/config/CreateTicket.svelte:117 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label warpgate-web/src/admin/config/Tickets.svelte:186 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label warpgate-web/src/admin/config/ldap/LdapConnectionFields.svelte:91 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D31 · IaC & Container Security · High IaC · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×5
  • 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 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) — 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 9 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: 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: 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: 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.
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
S1 · Web-Security Posture · TLS certificate validation disabled · ×3
  • TLS certificate validation disabled warpgate-protocol-rdp/src/client/tls.rs:129 — a rustls `ServerCertVerifier` that accepts every certificate (`NoCertificateVerification`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on.
  • TLS certificate validation disabled warpgate-protocol-rdp/src/client/tls.rs:264 — a rustls `ServerCertVerifier` that accepts every certificate (`NoCertificateVerification`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on.
  • TLS certificate validation disabled warpgate/src/commands/healthcheck.rs:16 — a rustls `ServerCertVerifier` that accepts every certificate (`NoCertificateVerification`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on.
AC2 · Forms & labels · <label> that labels no control · ×1
  • <label> that labels no control warpgate-web/src/admin/config/Policies.svelte:87 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics · Focusable <canvas> isn't keyboard-operable · ×1
  • Focusable <canvas> isn't keyboard-operable warpgate-web/src/gateway/WebDesktop.svelte:541 — This <canvas> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its only behaviour is bound to mousedown, mouseup, mousemove and wheel, pointer gestures a keyboard cannot produce, and there is no key handler. The tab stop leads nowhere. Bind the same behaviour to a key handler, or provide an equivalent control elsewhere. Give it a role as well, so assistive tech can announce what it is.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 455 finding(s)
D15 · Churn × Complexity Hotspots · Hotspot · ×15
  • Hotspot: warpgate-protocol-ssh/src/server/session.rs warpgate-protocol-ssh/src/server/session.rs:1261 — warpgate-protocol-ssh/src/server/session.rs changed 24 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. 10 of those changes were fix/bug commits, and the other 14 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in warpgate_protocol_rdp::client::active_loop at line 153. 8 of those changes were fix/bug commits, 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-ssh/src/client/mod.rs warpgate-protocol-ssh/src/client/mod.rs:1018 — 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 1018. 6 of those changes were fix/bug commits, 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-rdp/src/server/mod.rs warpgate-protocol-rdp/src/server/mod.rs:209 — warpgate-protocol-rdp/src/server/mod.rs changed 8 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. 4 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-http/src/common.rs warpgate-protocol-http/src/common.rs:522 — warpgate-protocol-http/src/common.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in warpgate_protocol_http::common::inject_request_authorization at line 522. 2 of those changes were fix/bug commits, 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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/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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-protocol-http/src/api/info.rs warpgate-protocol-http/src/api/info.rs:168 — warpgate-protocol-http/src/api/info.rs changed 7 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. 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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 8 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. 3 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-protocol-mysql/src/client.rs warpgate-protocol-mysql/src/client.rs:41 — warpgate-protocol-mysql/src/client.rs changed 6 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-core/src/ticket_requests.rs warpgate-core/src/ticket_requests.rs:55 — warpgate-core/src/ticket_requests.rs changed 6 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-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 20 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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 4 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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 2 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×13
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-common/src/eventhub.rs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-core/src/config_providers/db.rs:823` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00037_database_target_auth.rs:105` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-http/src/api/auth.rs:456` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-ssh/src/server/session.rs:1446` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00080_user_and_target_sessions.rs:166` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-http/src/api/credentials.rs:413` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `body` to `Json<NewPublicKeyCredential>` in one and `Json<IssueCertificateCredentialRequest>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-aws/src/region.rs:14` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-http/src/api/credentials.rs:467` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) warpgate-admin/src/api/certificate_credentials.rs:147 — warpgate-admin/src/api/certificate_credentials.rs:147-156 | warpgate-admin/src/api/public_key_credentials.rs:165-174 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/certificate_credentials.rs:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) warpgate-protocol-ssh/src/server/session.rs:2046 — warpgate-protocol-ssh/src/server/session.rs:2046-2055 | warpgate-protocol-ssh/src/server/session.rs:2087-2096 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-ssh/src/server/session.rs:2046` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D3 · God Classes · MethodTooLong · ×12
  • 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:1018 — 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 128 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 28 over it, 1.28× 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: PostgresClient.connect warpgate-protocol-postgres/src/client.rs:59 — MethodTooLong — connect runs 112 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 12 over it, 1.12× 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: 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.
D3 · God Classes · FileTooLong · ×11
  • FileTooLong: server/session.rs warpgate-protocol-ssh/src/server/session.rs — FileTooLong — 1803 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-2730). The bar is 500 significant lines; this is 1303 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 — 1000 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 500 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 — 725 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-1027). The bar is 500 significant lines; this is 225 over it, 1.45× 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-rdp/src/client/mod.rs — FileTooLong — 655 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 155 over it, 1.31× 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/users.rs warpgate-admin/src/api/users.rs — FileTooLong — 644 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 144 over it, 1.29× 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 — 621 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 121 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 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: src/correlator.rs warpgate-protocol-kubernetes/src/correlator.rs — FileTooLong — 540 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 40 over it, 1.08× 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.
D3 · God Classes · FunctionTooLong · ×11
  • 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_protocol_rdp::client::active_loop warpgate-protocol-rdp/src/client/mod.rs:153 — FunctionTooLong — warpgate_protocol_rdp::client::active_loop runs 126 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 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: 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_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.
D5 · Coupling · Off the main sequence · ×9
  • 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-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-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-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.
D17 · Explicit Debt · TodoComment · ×8
  • TodoComment warpgate-protocol-ssh/src/client/mod.rs:1209 — /// TODO: Optionally implement forwarding the challenges to the user — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment warpgate-protocol-http/src/common.rs:257 — // TODO unify both based on the accept header — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment warpgate-database-protocols/src/mysql/protocol/response/err.rs:55 — //TODO: sql_state — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment warpgate-core/src/cluster.rs:129 — // TODO: client pool — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment warpgate-core/src/rate_limiting/registry.rs:33 — // TODO granular refresh — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment warpgate-core/src/approvals/gate.rs:91 — /// `notify_waiting` is called if waiting for an administrator (TODO use a more explicit event sender) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment warpgate-common/src/types/aliases.rs:5 — // TODO reuse for other IDs — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment warpgate-common/src/auth/cred.rs:231 — // TODO check verbosity — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D31 · IaC & Container Security · Medium IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×8
  • Duplicated block (13 lines × 2) warpgate-admin/src/api/otp_credentials.rs:153 — warpgate-admin/src/api/otp_credentials.rs:153-165 | warpgate-admin/src/api/password_credentials.rs:161-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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/otp_credentials.rs:153` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) 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-rdp/src/server/mod.rs:111 — warpgate-protocol-rdp/src/server/mod.rs:111-123 | warpgate-protocol-vnc/src/server/mod.rs:72-84 — 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:2123 — warpgate-protocol-ssh/src/server/session.rs:2123-2135 | warpgate-protocol-ssh/src/server/session.rs:2161-2173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-ssh/src/server/session.rs:2123` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00057_password_login_mode.rs:35` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×7
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/ldap_servers.rs:348` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `body` to `Json<CreateLdapServerRequest>` in one and `Json<TestLdapServerRequest>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) warpgate-admin/src/api/users.rs:687 — warpgate-admin/src/api/users.rs:687-694 | warpgate-admin/src/api/users.rs:742-749 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/users.rs:687` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) warpgate-admin/src/api/users.rs:724 — warpgate-admin/src/api/users.rs:724-731 | warpgate-admin/src/api/users.rs:779-786 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/users.rs:724` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) warpgate-admin/src/api/users.rs:873 — warpgate-admin/src/api/users.rs:873-880 | warpgate-admin/src/api/users.rs:924-931 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/users.rs:873` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-mysql/src/stream.rs:95` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `mut` in one and `crate) async fn upgrade( mut` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (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-kubernetes/src/server/handlers.rs:674 — warpgate-protocol-kubernetes/src/server/handlers.rs:674-682 | warpgate-protocol-kubernetes/src/server/handlers.rs:686-693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-kubernetes/src/server/handlers.rs:674` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D2 · Cognitive Complexity · ServerSession · ×5
  • 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:2377 — 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:2175 — 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.
D3 · God Classes · ClassTooLong · ×5
  • ClassTooLong: ServerSession warpgate-protocol-ssh/src/server/session.rs:134 — ClassTooLong — 1675 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-2730. The bar is 400 significant lines; this is 1275 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 — 638 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-1027. The bar is 400 significant lines; this is 238 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: 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.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×5
  • Edited copy of a member (14 corresponding lines) warpgate-core/src/recordings/traffic.rs:147 — warpgate-core/src/recordings/traffic.rs:147-160 | warpgate-core/src/recordings/traffic.rs:165-178 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) warpgate-protocol-mysql/src/session.rs:237 — warpgate-protocol-mysql/src/session.rs:237-252 | warpgate-protocol-postgres/src/session.rs:280-293 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) warpgate-aws/src/region.rs:8 — warpgate-aws/src/region.rs:8-23 | warpgate-aws/src/region.rs:30-43 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) warpgate-db-migrations/src/m00052_log_text_column.rs:9 — warpgate-db-migrations/src/m00052_log_text_column.rs:9-22 | warpgate-db-migrations/src/m00052_log_text_column.rs:24-37 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) warpgate-db-migrations/src/m00016_fix_public_key_length.rs:17 — warpgate-db-migrations/src/m00016_fix_public_key_length.rs:17-30 | warpgate-db-migrations/src/m00016_fix_public_key_length.rs:32-45 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×5
  • Edited copy of a member (13 corresponding lines) warpgate-protocol-mysql/src/common.rs:9 — warpgate-protocol-mysql/src/common.rs:9-21 | warpgate-protocol-mysql/src/common.rs:25-37 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) warpgate-core/src/rate_limiting/stream.rs:176 — warpgate-core/src/rate_limiting/stream.rs:176-188 | warpgate-core/src/rate_limiting/stream.rs:196-209 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs:437 — warpgate-protocol-ssh/src/server/russh_handler.rs:437-449 | warpgate-protocol-ssh/src/server/russh_handler.rs:500-516 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) warpgate-protocol-http/src/api/common.rs:24 — warpgate-protocol-http/src/api/common.rs:24-37 | warpgate-protocol-kubernetes/src/server/auth.rs:103-115 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) warpgate-db-migrations/src/m00072_session_node_id_not_null.rs:41 — warpgate-db-migrations/src/m00072_session_node_id_not_null.rs:41-53 | warpgate-db-migrations/src/m00077_session_user_target_id.rs:8-21 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×5
  • Edited copy of a member (10 corresponding lines) warpgate-core/src/logging/json_console.rs:97 — warpgate-core/src/logging/json_console.rs:97-107 | warpgate-core/src/logging/layer.rs:34-43 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) warpgate-admin/src/main.rs:7 — warpgate-admin/src/main.rs:7-16 | warpgate-protocol-http/src/main.rs:7-16 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) warpgate-protocol-http/src/api/web_desktop.rs:44 — warpgate-protocol-http/src/api/web_desktop.rs:44-54 | warpgate-protocol-http/src/api/web_ssh.rs:40-49 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) warpgate-db-migrations/src/m00061_rename_web_ssh_enabled.rs:13 — warpgate-db-migrations/src/m00061_rename_web_ssh_enabled.rs:13-25 | warpgate-db-migrations/src/m00068_rename_ssh_banner.rs:13-22 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) warpgate-db-migrations/src/m00061_rename_web_ssh_enabled.rs:27 — warpgate-db-migrations/src/m00061_rename_web_ssh_enabled.rs:27-39 | warpgate-db-migrations/src/m00068_rename_ssh_banner.rs:24-33 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×5
  • 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-http/src/api/ticket_requests.rs:252` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) warpgate-protocol-mysql/src/lib.rs:86 — warpgate-protocol-mysql/src/lib.rs:86-96 | warpgate-protocol-postgres/src/lib.rs:110-121 — before extracting anything, compare `warpgate-protocol-mysql/src/lib.rs` and `warpgate-protocol-postgres/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-mysql/src/lib.rs:86` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 2) warpgate-protocol-rdp/src/lib.rs:116 — warpgate-protocol-rdp/src/lib.rs:116-126 | warpgate-protocol-vnc/src/client.rs:136-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-rdp/src/lib.rs:116` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 2) warpgate-admin/src/api/certificate_credentials.rs:256 — warpgate-admin/src/api/certificate_credentials.rs:256-266 | warpgate-admin/src/api/public_key_credentials.rs:285-295 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/certificate_credentials.rs:256` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×5
  • 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00036_user_role_expiry_history.rs:13` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×5
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-core/src/ticket_requests.rs:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-vnc/src/server/protocol.rs:385` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (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 — before extracting anything, compare `warpgate-common/src/helpers/serde_base64.rs` and `warpgate-db-migrations/src/m00009_credential_models.rs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-common/src/helpers/serde_base64.rs:13` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `warpgate-admin/src/api/admin_scheme.rs:180` calls `pub`, `require`, `access` and `warpgate-protocol-http/src/api/auth_scheme.rs:63` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 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.
AC3 · Page structure · Heading level jumps from h1 to h4 · ×4
  • Heading level jumps from h1 to h4 warpgate-web/src/admin/config/AccessRole.svelte:145 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h4 warpgate-web/src/admin/config/AdminRole.svelte:165 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h4 warpgate-web/src/admin/config/targets/Target.svelte:303 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h4 warpgate-web/src/gateway/TicketRequests.svelte:255 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D2 · Cognitive Complexity · warpgate_protocol_rdp · ×4
  • 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 51) warpgate-protocol-rdp/src/client/mod.rs:153 — warpgate_protocol_rdp::client::active_loop has cognitive complexity 51 (threshold 15). Drivers by points: if/else 11 (29 pts), match/switch 4 (11 pts), loops 4 (9 pts), boolean chains 2 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • warpgate_protocol_rdp::server::rdp::route_input (cognitive 22) warpgate-protocol-rdp/src/server/rdp.rs:189 — 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.
D2 · Cognitive Complexity · warpgate_protocol_kubernetes · ×4
  • 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::server::auth::authenticate (cognitive 22) warpgate-protocol-kubernetes/src/server/auth.rs:355 — 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::correlator::correlated_authorization (cognitive 17) warpgate-protocol-kubernetes/src/correlator.rs:137 — warpgate_protocol_kubernetes::correlator::correlated_authorization has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • 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.
D3 · God Classes · TooManyFields · ×4
  • 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 CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×4
  • Edited copy of a member (18 corresponding lines) warpgate-core/src/recordings/traffic.rs:106 — warpgate-core/src/recordings/traffic.rs:106-123 | warpgate-core/src/recordings/traffic.rs:125-142 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) warpgate-admin/src/api/ticket_requests_detail.rs:53 — warpgate-admin/src/api/ticket_requests_detail.rs:53-70 | warpgate-admin/src/api/ticket_requests_detail.rs:82-99 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) warpgate-db-migrations/src/m00081_http_session_user_session_id.rs:49 — warpgate-db-migrations/src/m00081_http_session_user_session_id.rs:49-66 | warpgate-db-migrations/src/m00092_http_session_sso_identity.rs:43-65 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) warpgate-db-migrations/src/m00027_ca.rs:96 — warpgate-db-migrations/src/m00027_ca.rs:96-115 | warpgate-db-migrations/src/m00084_mfa_enforcement.rs:39-56 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×4
  • Edited copy of a member (11 corresponding lines) warpgate-protocol-ssh/src/server/session.rs:2578 — warpgate-protocol-ssh/src/server/session.rs:2578-2588 | warpgate-protocol-ssh/src/server/session.rs:2594-2608 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) warpgate-admin/src/api/ldap_servers.rs:510 — warpgate-admin/src/api/ldap_servers.rs:510-520 | warpgate-admin/src/api/ldap_servers.rs:597-609 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) warpgate-protocol-ssh/src/server/session.rs:1848 — warpgate-protocol-ssh/src/server/session.rs:1848-1858 | warpgate-protocol-ssh/src/server/session.rs:1910-1920 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) warpgate-aws/src/s3.rs:135 — warpgate-aws/src/s3.rs:135-145 | warpgate-aws/src/s3.rs:148-158 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×4
  • Edited copy of a member (12 corresponding lines) warpgate-db-entities/src/UserAdminRoleAssignment.rs:23 — warpgate-db-entities/src/UserAdminRoleAssignment.rs:23-34 | warpgate-db-migrations/src/m00032_admin_roles.rs:67-78 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) warpgate-core/src/config_providers/db.rs:328 — warpgate-core/src/config_providers/db.rs:328-339 | warpgate-core/src/config_providers/db.rs:341-352 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs:236 — warpgate-protocol-ssh/src/server/russh_handler.rs:236-247 | warpgate-protocol-ssh/src/server/russh_handler.rs:253-265 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) warpgate-common/src/auth/state.rs:351 — warpgate-common/src/auth/state.rs:351-362 | warpgate-core/src/approvals/subject.rs:48-59 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-web-desktop/src/api.rs:26` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `warpgate-web-desktop/src/api.rs:45` calls `Some`, `keyframe`, `push` and `warpgate-web-ssh/src/api.rs:46` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (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 — before extracting anything, compare `warpgate-db-migrations/src/m00025_ssh_client_auth.rs` and `warpgate-db-migrations/src/m00044_ticket_requests.rs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00025_ssh_client_auth.rs:28` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00019_rate_limits.rs:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×4
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00025_ssh_client_auth.rs:66` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:21` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-common/src/audit.rs:401` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (14 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00017_descriptions.rs:96` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
S1 · Web-Security Posture · Weak hash algorithm · ×4
  • Weak hash algorithm warpgate-protocol-mysql/src/common.rs:10 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm warpgate-protocol-mysql/src/common.rs:11 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm warpgate-protocol-mysql/src/common.rs:13 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm warpgate-protocol-vnc/src/server/rfb.rs:235 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
AC3 · Page structure · Heading level jumps from h1 to h5 · ×3
  • Heading level jumps from h1 to h5 warpgate-web/src/admin/config/Tickets.svelte:102 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h5 warpgate-web/src/admin/status/LoginProtection.svelte:133 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h5 warpgate-web/src/admin/status/NetworkStatus.svelte:22 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D1 · Cyclomatic Complexity · ServerSession · ×3
  • 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 23 functions over the threshold — including the worst — and 48 of the 147 points over it (33%), 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 23 functions over the threshold — including the worst — and 48 of the 147 points over it (33%), 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 23 functions over the threshold — including the worst — and 48 of the 147 points over it (33%), 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.
D17 · Explicit Debt · HackComment · ×3
  • HackComment warpgate-protocol-ssh/src/server/session.rs:198 — // HACK russh ChannelId is opaque except via Display — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment warpgate-protocol-ssh/src/server/session.rs:1765 — // HACK russh ChannelId is opaque except via Display — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment warpgate-protocol-http/src/common.rs:185 — // HACK: for getting the session state out of an already serialized session — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · warpgate_core · ×3
  • 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.
D2 · Cognitive Complexity · warpgate_protocol_vnc · ×3
  • 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.
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×3
  • Edited copy of a member (16 corresponding lines) warpgate-admin/src/api/roles.rs:154 — warpgate-admin/src/api/roles.rs:154-169 | warpgate-admin/src/api/target_groups.rs:142-157 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) warpgate-admin/src/api/roles.rs:195 — warpgate-admin/src/api/roles.rs:195-210 | warpgate-admin/src/api/roles.rs:221-236 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) warpgate-admin/src/api/secret_backends.rs:455 — warpgate-admin/src/api/secret_backends.rs:455-470 | warpgate-admin/src/api/ssh_keys.rs:267-283 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 14+ corresponding lines) warpgate-admin/src/api/roles.rs:67 — warpgate-admin/src/api/roles.rs:67-81 | warpgate-admin/src/api/target_groups.rs:64-77 | warpgate-admin/src/api/targets.rs:87-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) warpgate-admin/src/api/admin_roles.rs:106 — warpgate-admin/src/api/admin_roles.rs:106-119 | warpgate-admin/src/api/ldap_servers.rs:297-313 | warpgate-admin/src/api/roles.rs:45-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) warpgate-db-migrations/src/m00007_targets_and_roles.rs:127 — warpgate-db-migrations/src/m00007_targets_and_roles.rs:127-142 | warpgate-db-migrations/src/m00020_target_groups.rs:82-99 | warpgate-db-migrations/src/m00064_cluster.rs:48-61 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×3
  • Edited copy of a member (17 corresponding lines) warpgate-core/src/resources/roles.rs:60 — warpgate-core/src/resources/roles.rs:60-80 | warpgate-core/src/resources/target_groups.rs:58-74 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) warpgate-protocol-rdp/src/client/tls.rs:212 — warpgate-protocol-rdp/src/client/tls.rs:212-228 | warpgate-protocol-rdp/src/client/tls.rs:235-251 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) warpgate-db-migrations/src/m00020_target_groups.rs:58 — warpgate-db-migrations/src/m00020_target_groups.rs:58-80 | warpgate-db-migrations/src/m00064_cluster.rs:30-46 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×3
  • Edited copy of a member (9 corresponding lines) warpgate-protocol-vnc/src/server/protocol.rs:107 — warpgate-protocol-vnc/src/server/protocol.rs:107-115 | warpgate-protocol-vnc/src/server/protocol.rs:122-133 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) warpgate-core/src/rate_limiting/registry.rs:62 — warpgate-core/src/rate_limiting/registry.rs:62-70 | warpgate-core/src/rate_limiting/registry.rs:83-91 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) warpgate-core/src/resources/roles.rs:29 — warpgate-core/src/resources/roles.rs:29-38 | warpgate-core/src/resources/target_groups.rs:29-37 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×3
  • Edited copy of a member (8 corresponding lines) warpgate-core/src/recordings/traffic.rs:183 — warpgate-core/src/recordings/traffic.rs:183-190 | warpgate-core/src/recordings/traffic.rs:195-202 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) warpgate-admin/src/api/admin_roles.rs:178 — warpgate-admin/src/api/admin_roles.rs:178-185 | warpgate-admin/src/api/roles.rs:137-146 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) warpgate-admin/src/api/session_approvals.rs:158 — warpgate-admin/src/api/session_approvals.rs:158-165 | warpgate-admin/src/api/sessions_list.rs:222-229 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×3
  • Edited copy of a member (6 corresponding lines) warpgate-core/src/protocols/framebuffer.rs:50 — warpgate-core/src/protocols/framebuffer.rs:50-55 | warpgate-core/src/protocols/framebuffer.rs:96-104 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) warpgate-protocol-mysql/src/stream.rs:54 — warpgate-protocol-mysql/src/stream.rs:54-60 | warpgate-protocol-postgres/src/stream.rs:131-136 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) warpgate-core/src/protocols/terminal_screen.rs:35 — warpgate-core/src/protocols/terminal_screen.rs:35-40 | warpgate-protocol-ssh/src/command_detector.rs:67-73 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) warpgate-protocol-rdp/src/client/tls.rs:26 — warpgate-protocol-rdp/src/client/tls.rs:26-32 | warpgate-protocol-rdp/src/client/tls.rs:40-46 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) warpgate-tls/src/maybe_tls_stream.rs:143 — warpgate-tls/src/maybe_tls_stream.rs:143-149 | warpgate-tls/src/maybe_tls_stream.rs:161-167 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) warpgate-protocol-mysql/src/stream.rs:34 — warpgate-protocol-mysql/src/stream.rs:34-41 | warpgate-protocol-postgres/src/stream.rs:113-119 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 9+ corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs:267 — warpgate-protocol-ssh/src/server/russh_handler.rs:267-277 | warpgate-protocol-ssh/src/server/russh_handler.rs:310-320 | warpgate-protocol-ssh/src/server/russh_handler.rs:328-336 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) warpgate-admin/src/api/secret_backends.rs:331 — warpgate-admin/src/api/secret_backends.rs:331-342 | warpgate-admin/src/api/secret_backends.rs:352-361 | warpgate-admin/src/api/ssh_keys.rs:141-149 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) warpgate-protocol-ssh/src/server/target_menu.rs:402 — warpgate-protocol-ssh/src/server/target_menu.rs:402-413 | warpgate-protocol-ssh/src/server/target_menu.rs:424-432 | warpgate-protocol-ssh/src/server/target_menu.rs:434-442 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) warpgate-core/src/recordings/traffic.rs:185 — warpgate-core/src/recordings/traffic.rs:185-190 | warpgate-core/src/recordings/traffic.rs:197-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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-core/src/recordings/traffic.rs:185` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-core/src/recordings/desktop.rs:238` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `item` to `&DesktopRecordingItem` in one and `&TerminalRecordingItem` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×3
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00044_ticket_requests.rs:219` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00044_ticket_requests.rs:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-common/src/audit.rs:226` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
AC1 · Text alternatives · <canvas> without a text alternative · ×2
  • <canvas> without a text alternative warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:253 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative warpgate-web/src/gateway/WebDesktop.svelte:541 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
D1 · Cyclomatic Complexity · warpgate_protocol_rdp · ×2
  • 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 26) warpgate-protocol-rdp/src/client/mod.rs:153 — warpgate_protocol_rdp::client::active_loop has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · warpgate_protocol_kubernetes · ×2
  • 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.
D1 · Cyclomatic Complexity · warpgate · ×2
  • 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.
D1 · Cyclomatic Complexity · warpgate_protocol_vnc · ×2
  • 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.
D1 · Cyclomatic Complexity · warpgate_core · ×2
  • 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.
D2 · Cognitive Complexity · warpgate · ×2
  • 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.
D2 · Cognitive Complexity · warpgate_desktop_auth · ×2
  • 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.
D2 · Cognitive Complexity · Connector · ×2
  • Connector::authenticate_session (cognitive 27) warpgate-protocol-ssh/src/client/mod.rs:1018 — 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:1216 — 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.
D2 · Cognitive Complexity · warpgate_admin · ×2
  • 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.
D2 · Cognitive Complexity · warpgate_protocol_http · ×2
  • 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 23) warpgate-protocol-http/src/common.rs:522 — warpgate_protocol_http::common::inject_request_authorization has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 5). 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.
D2 · Cognitive Complexity · Migration · ×2
  • 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.
D35 · Change Coupling · Change coupling · ×2
  • 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 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 `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 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `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.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×2
  • Edited copy of a member (47 corresponding lines) warpgate-admin/src/api/certificate_credentials.rs:122 — warpgate-admin/src/api/certificate_credentials.rs:122-168 | warpgate-protocol-http/src/api/credentials.rs:609-658 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) warpgate-web-desktop/src/manager.rs:49 — warpgate-web-desktop/src/manager.rs:49-95 | warpgate-web-ssh/src/manager.rs:46-106 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×2
  • Edited copy of a member (40 corresponding lines) warpgate-protocol-http/src/api/ticket_requests.rs:237 — warpgate-protocol-http/src/api/ticket_requests.rs:237-280 | warpgate-protocol-http/src/api/ticket_requests.rs:366-405 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) warpgate-db-migrations/src/m00019_rate_limits.rs:17 — warpgate-db-migrations/src/m00019_rate_limits.rs:17-56 | warpgate-db-migrations/src/m00025_ssh_client_auth.rs:15-57 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×2
  • Edited copy of a member (24 corresponding lines) warpgate-protocol-http/src/api/ticket_requests.rs:291 — warpgate-protocol-http/src/api/ticket_requests.rs:291-314 | warpgate-protocol-http/src/api/ticket_requests.rs:416-442 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) warpgate-db-migrations/src/m00072_session_node_id_not_null.rs:14 — warpgate-db-migrations/src/m00072_session_node_id_not_null.rs:14-39 | warpgate-db-migrations/src/m00093_log_session_id_nullable.rs:116-139 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 10+ corresponding lines) warpgate-admin/src/api/recordings_detail.rs:88 — warpgate-admin/src/api/recordings_detail.rs:88-97 | warpgate-admin/src/api/recordings_detail.rs:105-114 | warpgate-admin/src/api/recordings_detail.rs:122-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) warpgate-db-migrations/src/m00023_ldap_username_attribute.rs:32 — warpgate-db-migrations/src/m00023_ldap_username_attribute.rs:32-41 | warpgate-db-migrations/src/m00024_ssh_key_attribute.rs:26-35 | warpgate-db-migrations/src/m00025_ldap_uuid_attribute.rs:26-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 16+ corresponding lines) warpgate-db-migrations/src/m00029_certificate_revocation.rs:32 — warpgate-db-migrations/src/m00029_certificate_revocation.rs:32-49 | warpgate-db-migrations/src/m00070_http_sessions.rs:30-45 | warpgate-db-migrations/src/m00095_kubernetes_sessions.rs:34-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs:154 — warpgate-protocol-ssh/src/server/russh_handler.rs:154-171 | warpgate-protocol-ssh/src/server/russh_handler.rs:215-230 | warpgate-protocol-ssh/src/server/russh_handler.rs:413-429 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 15+ corresponding lines) warpgate-db-migrations/src/m00023_ldap_username_attribute.rs:15 — warpgate-db-migrations/src/m00023_ldap_username_attribute.rs:15-30 | warpgate-db-migrations/src/m00024_ssh_key_attribute.rs:10-24 | warpgate-db-migrations/src/m00025_ldap_uuid_attribute.rs:10-24 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) warpgate-db-migrations/src/m00031_minimize_password_login.rs:15 — warpgate-db-migrations/src/m00031_minimize_password_login.rs:15-31 | warpgate-db-migrations/src/m00045_role_default_flag.rs:8-23 | warpgate-db-migrations/src/m00051_tutorial_dismissed.rs:10-24 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×2
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `warpgate-db-migrations/src/m00080_user_and_target_sessions.rs:70` calls `and_where`, `col`, `clone` and `warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:59` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/recordings_detail.rs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:170` calls `col`, `serial_id_column`, `primary_key` and `warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:75` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00034_add_log_related_fields.rs:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×2
  • 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.
R7 · Dead Code · Dead file (~316 LoC) · ×2
  • Dead file (~316 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/Manage.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
R7 · Dead Code · Dead file (~158 LoC) · ×2
  • 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
R7 · Dead Code · Dead file (~128 LoC) · ×2
  • Dead file (~128 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/Manage.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 (~128 LoC) warpgate-web/src/admin/status/Sessions.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
AC3 · Page structure · Heading level jumps from h1 to h6 · ×1
  • Heading level jumps from h1 to h6 warpgate-web/src/admin/config/ldap/LdapUserBrowser.svelte:149 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Data table has no header cells · ×1
  • Data table has no header cells warpgate-web/src/admin/status/KubernetesRecording.svelte:144 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 warpgate-web/src/admin/status/Session.svelte:253 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D1 · Cyclomatic Complexity · SessionChannel · ×1
  • 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.
D1 · Cyclomatic Complexity · PostgresClient · ×1
  • PostgresClient::connect (cyclomatic 20) warpgate-protocol-postgres/src/client.rs:59 — PostgresClient::connect 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.
D1 · Cyclomatic Complexity · Api · ×1
  • 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.
D1 · Cyclomatic Complexity · MySqlClient · ×1
  • 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.
D1 · Cyclomatic Complexity · TargetMenu · ×1
  • 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.
D1 · Cyclomatic Complexity · PlaybackController.doSeek (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · warpgate_desktop_auth · ×1
  • 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.
D1 · Cyclomatic Complexity · warpgate_protocol_http · ×1
  • warpgate_protocol_http::common::inject_request_authorization (cyclomatic 16) warpgate-protocol-http/src/common.rs:522 — warpgate_protocol_http::common::inject_request_authorization has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Connector · ×1
  • Connector::authenticate_session (cyclomatic 16) warpgate-protocol-ssh/src/client/mod.rs:1018 — 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.
D1 · Cyclomatic Complexity · warpgate_web_ssh · ×1
  • 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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×1
  • Repeated repair: warpgate-web/src/gateway/WebDesktop.svelte warpgate-web/src/gateway/WebDesktop.svelte:138 — warpgate-web/src/gateway/WebDesktop.svelte 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 11 (its worst body is onWsMessage at line 138), AT OR 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)”. 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 11:42:17 +01:00' --until='2026-11-11 11:42:17 +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.
D17 · Explicit Debt · FixmeComment · ×1
  • FixmeComment warpgate-database-protocols/src/mysql/protocol/packet.rs:34 — // FIXME: Support larger packets — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · Api · ×1
  • 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.
D2 · Cognitive Complexity · DirtyTracker · ×1
  • 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.
D2 · Cognitive Complexity · warpgate_web_desktop · ×1
  • 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.
D2 · Cognitive Complexity · warpgate_protocol_ssh · ×1
  • 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.
D2 · Cognitive Complexity · PostgresClient · ×1
  • PostgresClient::connect (cognitive 23) warpgate-protocol-postgres/src/client.rs:59 — PostgresClient::connect has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 4 (8 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TlsCertificateBundle · ×1
  • 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.
D2 · Cognitive Complexity · MySqlClient · ×1
  • 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.
D2 · Cognitive Complexity · warpgate_web_clients_common · ×1
  • 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.
D2 · Cognitive Complexity · ListenerSupervisor · ×1
  • 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.
D2 · Cognitive Complexity · helpers.toClassName (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · HandshakeResponse · ×1
  • 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.
D2 · Cognitive Complexity · protocols.getEffectivePossibleCredentials (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · Services · ×1
  • Services::new (cognitive 17) warpgate-core/src/services.rs:183 — 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.
D2 · Cognitive Complexity · ResponseRelay · ×1
  • 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.
D2 · Cognitive Complexity · PostgresSession · ×1
  • 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.
D2 · Cognitive Complexity · TargetMenu · ×1
  • 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.
D2 · Cognitive Complexity · CookieHostMiddlewareEndpoint · ×1
  • 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.
D2 · Cognitive Complexity · CommandDetector · ×1
  • CommandDetector::extract (cognitive 16) warpgate-protocol-ssh/src/command_detector.rs:193 — CommandDetector::extract has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · TooManyMethods · ×1
  • 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.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (50 shared lines) · ×1
  • 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.
D4 · Code Duplication · Edited copies of one member (3 members, 47+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 47+ corresponding lines) warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:43 — warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:43-89 | warpgate-db-migrations/src/m00081_http_session_user_session_id.rs:69-116 | warpgate-db-migrations/src/m00087_drop_null_target_options.rs:78-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 47 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (55 corresponding lines) · ×1
  • Edited copy of a member (55 corresponding lines) warpgate-core/src/config_providers/db.rs:822 — warpgate-core/src/config_providers/db.rs:822-876 | warpgate-core/src/config_providers/db.rs:883-939 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (66 corresponding lines) · ×1
  • Edited copy of a member (66 corresponding lines) warpgate-protocol-mysql/src/lib.rs:43 — warpgate-protocol-mysql/src/lib.rs:43-112 | warpgate-protocol-vnc/src/server/mod.rs:48-113 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) warpgate-admin/src/api/users.rs:839 — warpgate-admin/src/api/users.rs:839-883 | warpgate-admin/src/api/users.rs:896-934 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) warpgate-admin/src/api/public_key_credentials.rs:143 — warpgate-admin/src/api/public_key_credentials.rs:143-183 | warpgate-protocol-http/src/api/credentials.rs:389-431 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) warpgate-protocol-http/src/api/credentials.rs:443 — warpgate-protocol-http/src/api/credentials.rs:443-476 | warpgate-protocol-http/src/api/credentials.rs:670-713 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) warpgate-admin/src/api/otp_credentials.rs:89 — warpgate-admin/src/api/otp_credentials.rs:89-120 | warpgate-admin/src/api/sso_credentials.rs:105-135 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) warpgate-db-migrations/src/m00057_password_login_mode.rs:11 — warpgate-db-migrations/src/m00057_password_login_mode.rs:11-47 | warpgate-db-migrations/src/m00057_password_login_mode.rs:49-83 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 31+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 31+ corresponding lines) warpgate-admin/src/api/otp_credentials.rs:146 — warpgate-admin/src/api/otp_credentials.rs:146-176 | warpgate-admin/src/api/password_credentials.rs:154-184 | warpgate-admin/src/api/public_key_credentials.rs:263-298 | warpgate-admin/src/api/sso_credentials.rs:197-229 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) warpgate-core/src/ticket_requests.rs:280 — warpgate-core/src/ticket_requests.rs:280-321 | warpgate-core/src/ticket_requests.rs:441-473 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 30+ corresponding lines) warpgate-db-migrations/src/m00036_user_role_expiry_history.rs:8 — warpgate-db-migrations/src/m00036_user_role_expiry_history.rs:8-37 | warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:15-62 | warpgate-db-migrations/src/m00041_fix_user_role_assignment_dates.rs:64-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) warpgate-db-migrations/src/m00049_text_columns.rs:9 — warpgate-db-migrations/src/m00049_text_columns.rs:9-30 | warpgate-db-migrations/src/m00049_text_columns.rs:32-57 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) warpgate-db-migrations/src/m00074_encryption_key_rotation.rs:8 — warpgate-db-migrations/src/m00074_encryption_key_rotation.rs:8-41 | warpgate-db-migrations/src/m00074_encryption_key_rotation.rs:43-68 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) warpgate-db-migrations/src/m00017_descriptions.rs:90 — warpgate-db-migrations/src/m00017_descriptions.rs:90-116 | warpgate-db-migrations/src/m00019_rate_limits.rs:58-84 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 23+ corresponding lines) warpgate-db-migrations/src/m00013_add_openssh_public_key_dates.rs:15 — warpgate-db-migrations/src/m00013_add_openssh_public_key_dates.rs:15-37 | warpgate-db-migrations/src/m00015_fix_public_key_dates.rs:17-50 | warpgate-db-migrations/src/m00015_fix_public_key_dates.rs:52-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) warpgate-admin/src/api/admin_roles.rs:266 — warpgate-admin/src/api/admin_roles.rs:266-282 | warpgate-admin/src/api/targets.rs:311-327 | warpgate-admin/src/api/users.rs:810-826 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) warpgate-db-migrations/src/m00081_http_session_user_session_id.rs:27 — warpgate-db-migrations/src/m00081_http_session_user_session_id.rs:27-47 | warpgate-db-migrations/src/m00092_http_session_sso_identity.rs:17-41 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) warpgate-common/src/eventhub.rs:55 — warpgate-common/src/eventhub.rs:55-69 | warpgate-common/src/eventhub.rs:71-85 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 14+ corresponding lines) warpgate-admin/src/api/certificate_credentials.rs:96 — warpgate-admin/src/api/certificate_credentials.rs:96-109 | warpgate-admin/src/api/otp_credentials.rs:63-76 | warpgate-admin/src/api/password_credentials.rs:60-73 | warpgate-admin/src/api/public_key_credentials.rs:117-130 | warpgate-admin/src/api/sso_credentials.rs:79-92 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) warpgate-db-entities/src/TargetRoleAssignment.rs:23 — warpgate-db-entities/src/TargetRoleAssignment.rs:23-34 | warpgate-db-entities/src/UserRoleAssignment.rs:98-109 | warpgate-db-migrations/src/m00007_targets_and_roles.rs:85-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) warpgate-core/src/resources/roles.rs:44 — warpgate-core/src/resources/roles.rs:44-54 | warpgate-core/src/resources/target_groups.rs:43-53 | warpgate-core/src/resources/targets.rs:73-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 9+ corresponding lines) warpgate-admin/src/api/roles.rs:176 — warpgate-admin/src/api/roles.rs:176-184 | warpgate-admin/src/api/target_groups.rs:168-176 | warpgate-admin/src/api/targets.rs:219-231 | warpgate-admin/src/api/targets.rs:359-367 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 12+ corresponding lines) warpgate-protocol-ssh/src/server/russh_handler.rs:523 — warpgate-protocol-ssh/src/server/russh_handler.rs:523-535 | warpgate-protocol-ssh/src/server/russh_handler.rs:542-553 | warpgate-protocol-ssh/src/server/russh_handler.rs:559-570 | warpgate-protocol-ssh/src/server/russh_handler.rs:576-590 | warpgate-protocol-ssh/src/server/russh_handler.rs:596-609 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 16+ corresponding lines) warpgate-db-migrations/src/m00018_ticket_description.rs:16 — warpgate-db-migrations/src/m00018_ticket_description.rs:16-33 | warpgate-db-migrations/src/m00037_allowed_ip_range.rs:16-31 | warpgate-db-migrations/src/m00055_ssh_banner.rs:11-29 | warpgate-db-migrations/src/m00085_default_credential_policy.rs:14-29 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) warpgate-protocol-mysql/src/session.rs:137 — warpgate-protocol-mysql/src/session.rs:137-144 | warpgate-protocol-postgres/src/session.rs:186-193 | warpgate-protocol-ssh/src/server/session.rs:532-539 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 15+ corresponding lines) warpgate-db-migrations/src/m00037_show_session_menu.rs:15 — warpgate-db-migrations/src/m00037_show_session_menu.rs:15-31 | warpgate-db-migrations/src/m00047_record_scp.rs:10-26 | warpgate-db-migrations/src/m00056_web_ssh_enabled.rs:10-24 | warpgate-db-migrations/src/m00083_record_desktop_keyboard_input.rs:10-26 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) warpgate-core/src/recordings/writer.rs:151 — warpgate-core/src/recordings/writer.rs:151-154 | warpgate-protocol-ssh/src/server/service_output.rs:273-276 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×1
  • Duplicated block (20–21 lines × 2) warpgate-protocol-rdp/src/server/mod.rs:134 — warpgate-protocol-rdp/src/server/mod.rs:134-154 | warpgate-protocol-vnc/src/server/mod.rs:94-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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-rdp/src/server/mod.rs:134` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-core/src/logging/json_console.rs:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) warpgate-protocol-ssh/src/server/session.rs:806 — warpgate-protocol-ssh/src/server/session.rs:806-821 | warpgate-protocol-ssh/src/server/session.rs:2541-2557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-ssh/src/server/session.rs:806` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (9–13 lines × 2) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00072_session_node_id_not_null.rs:19` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) warpgate-admin/src/api/certificate_credentials.rs:143 — warpgate-admin/src/api/certificate_credentials.rs:143-154 | 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/certificate_credentials.rs:143` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8–12 lines × 2) · ×1
  • 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 — before extracting anything, compare `warpgate-protocol-mysql/src/lib.rs` and `warpgate-protocol-postgres/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) warpgate-admin/src/api/certificate_credentials.rs:196 — warpgate-admin/src/api/certificate_credentials.rs:196-203 | warpgate-admin/src/api/certificate_credentials.rs:229-237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-admin/src/api/certificate_credentials.rs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1
  • 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `warpgate-common/src/audit.rs:549` calls `as_deref` and `warpgate-common/src/audit.rs:618` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • 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 — before extracting anything, compare `warpgate-protocol-mysql/src/lib.rs` and `warpgate-protocol-postgres/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:76 — warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:76-82 | 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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00073_redact_session_target_snapshots.rs:76` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • 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 — before extracting anything, compare `warpgate-db-migrations/src/m00066_cluster_token.rs` and `warpgate-db-migrations/src/m00091_drop_cluster_token.rs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-protocol-mysql/src/session_handle.rs:9` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • 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 — before extracting anything, compare `warpgate-db-entities/src/ApiToken.rs` and `warpgate-db-entities/src/CertificateCredential.rs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:88` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:200` calls `col`, `serial_id_column`, `primary_key` and `warpgate-db-migrations/src/m00078_assignment_composite_pks.rs:110` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17 lines × 4) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00044_ticket_requests.rs:121` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • 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 — before extracting anything, compare `warpgate-db-migrations/src/m00025_ssh_client_auth.rs` and `warpgate-db-migrations/src/m00037_show_session_menu.rs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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.
D4 · Code Duplication · Duplicated block (14 lines × 5) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00044_ticket_requests.rs:120` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-common/src/audit.rs:321` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00044_ticket_requests.rs:221` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • 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. Read the line range as the matched WINDOW rather than a finished unit: at `warpgate-db-migrations/src/m00025_ssh_client_auth.rs:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D5 · Coupling · Unstable project warpgate-admin (Cargo) · ×1
  • Unstable project warpgate-admin (Cargo) — warpgate-admin (Cargo) has instability 0.83 with 2 dependents.
D5 · Coupling · Unstable project warpgate-protocol-kubernetes · ×1
  • Unstable project warpgate-protocol-kubernetes — warpgate-protocol-kubernetes has instability 0.82 with 2 dependents.
D5 · Coupling · Unstable project warpgate-web-desktop · ×1
  • Unstable project warpgate-web-desktop — warpgate-web-desktop has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project warpgate-web-ssh · ×1
  • 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.
R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1
  • 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 (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) warpgate-web/src/admin/config/Policies.svelte:12 — warpgate-web/src/admin/config/Policies.svelte:12 · warpgate-web/src/admin/config/parameters/ParametersForm.svelte:39 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×1
  • 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:90 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1
  • Duplicated block (15 lines × 2 locations) warpgate-web/src/admin/config/AccessRole.svelte:29 — warpgate-web/src/admin/config/AccessRole.svelte:29 · warpgate-web/src/admin/config/AccessRole.svelte:45 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (15 lines × 3 locations) · ×1
  • Duplicated block (15 lines × 3 locations) warpgate-web/src/admin/config/AccessRole.svelte:64 — warpgate-web/src/admin/config/AccessRole.svelte:64 · warpgate-web/src/admin/config/AdminRole.svelte:129 · warpgate-web/src/admin/config/targets/Target.svelte:83 — 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.
R10 · Code Duplication · Duplicated block (14 lines × 3 locations) · ×1
  • 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:26 · 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.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×1
  • 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.
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×1
  • Duplicated block (8 lines × 2 locations) warpgate-web/src/admin/config/AccessRole.svelte:13 — warpgate-web/src/admin/config/AccessRole.svelte:13 · warpgate-web/src/admin/config/AdminRole.svelte:18 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (8 matched lines × 2 locations) warpgate-web/src/admin/config/ldap/LdapServer.svelte:18 — warpgate-web/src/admin/config/ldap/LdapServer.svelte:18 · warpgate-web/src/admin/config/ldap/LdapUserBrowser.svelte:15 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (5 lines × 2 locations) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function onMessage (cyclomatic 16, cognitive 11) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function mfaEnforcedFactor (cyclomatic 14, cognitive 14) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function parseHumantimeDuration (cyclomatic 13, cognitive 12) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function getEffectivePossibleCredentials (cyclomatic 12, cognitive 18) · ×1
  • 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 (anonymous) (cyclomatic 12, cognitive 11) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function updateActiveSectionFromScroll (cyclomatic 11, cognitive 18) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function onWsMessage (cyclomatic 11, cognitive 12) · ×1
  • 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.
R2 · Cyclomatic Complexity · Complex function save (cyclomatic 11, cognitive 10) · ×1
  • Complex function save (cyclomatic 11, cognitive 10) warpgate-web/src/admin/config/parameters/ParametersForm.svelte:63 — save has cyclomatic complexity 11 and cognitive complexity 10; 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.
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: 689 lines of code warpgate-web/src/admin/config/targets/Target.svelte:1 — warpgate-web/src/admin/config/targets/Target.svelte has 689 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: 589 lines of code warpgate-web/src/admin/config/users/User.svelte:1 — warpgate-web/src/admin/config/users/User.svelte has 589 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/TargetList.svelte · ×1
  • warpgate-web/src/gateway/TargetList.svelte: 459 lines of code warpgate-web/src/gateway/TargetList.svelte:1 — warpgate-web/src/gateway/TargetList.svelte has 459 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: 431 lines of code warpgate-web/src/gateway/TicketRequests.svelte:1 — warpgate-web/src/gateway/TicketRequests.svelte has 431 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: 404 lines of code warpgate-web/src/gateway/Login.svelte:1 — warpgate-web/src/gateway/Login.svelte has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~500 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~494 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~374 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~331 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~324 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~322 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~308 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~297 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~268 LoC) · ×1
  • Dead file (~268 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
R7 · Dead Code · Dead file (~242 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~233 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~221 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~217 LoC) · ×1
  • Dead file (~217 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
R7 · Dead Code · Dead file (~213 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~207 LoC) · ×1
  • Dead file (~207 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
R7 · Dead Code · Dead file (~206 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~184 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~183 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~160 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~150 LoC) · ×1
  • Dead file (~150 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
R7 · Dead Code · Dead file (~147 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~144 LoC) · ×1
  • Dead file (~144 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/Manage.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
R7 · Dead Code · Dead file (~143 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~141 LoC) · ×1
  • Dead file (~141 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/Manage.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
R7 · Dead Code · Dead file (~135 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~133 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~123 LoC) · ×1
  • 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/ParametersForm.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
R7 · Dead Code · Dead file (~119 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~116 LoC) · ×1
  • Dead file (~116 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
R7 · Dead Code · Dead file (~115 LoC) · ×1
  • 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/Network.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
R7 · Dead Code · Dead file (~114 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~111 LoC) · ×1
  • 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
R7 · Dead Code · Dead file (~109 LoC) · ×1
  • 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
R8 · Dependency Hygiene · Unused dependency '@otplib/plugin-base32-enc-dec' · ×1
  • 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.
R8 · Dependency Hygiene · Unused dependency '@otplib/plugin-crypto-js' · ×1
  • 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.
R8 · Dependency Hygiene · Unused dependency '@otplib/preset-browser' · ×1
  • 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.
R8 · Dependency Hygiene · Unused dependency 'svelte-observable' · ×1
  • Unused dependency 'svelte-observable' — 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.
R8 · Dependency Hygiene · Unused dependency 'tslib' · ×1
  • Unused dependency 'tslib' — 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.
S1 · Web-Security Posture · Obsolete TLS/SSL protocol version enabled · ×1
  • Obsolete TLS/SSL protocol version enabled warpgate-protocol-rdp/src/client/tls.rs:244 — `set_min_proto_version(SslVersion::TLS1)` explicitly admits a protocol version that is broken (SSL 3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Remove the pin: reqwest, native-tls and openssl negotiate the highest version both sides support, and rustls implements only TLS 1.2 and 1.3 — so naming no older version is the strongest setting. Where a floor must be named, use `min_tls_version(tls::Version::TLS_1_2)` / `set_min_proto_version(Some(SslVersion::TLS1_2))`.
Minor — 83 finding(s)
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • 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`.
  • + 15 more in this group — see findings.md.
D31 · IaC & Container Security · Low IaC · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned file · ×7
  • 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.
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Pending state with no failure state · ×3
  • Pending state with no failure state warpgate-web/src/gateway/App.svelte:143 — The view draws `<DelayedSpinner />` under `redirecting`, but `redirecting` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state warpgate-web/src/admin/player/DesktopRecordingPlayer.svelte:247 — The view draws `<Spinner color="primary" />` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state warpgate-web/src/admin/player/TerminalRecordingPlayer.svelte:331 — The view draws `<Spinner color="primary" />` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×2
  • REDACTED
  • REDACTED
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate warpgate-db-entities/src/KubernetesSession.rs:193 — `sql.contains("ON DUPLICATE KEY UPDATE") || sql.contains("ON CONFLICT")` appears character-identically in 2 files — warpgate-db-entities/src/KubernetesSession.rs, warpgate-db-entities/src/TargetSession.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate 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.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 19 significant file(s) lose their only recent owner: warpgate-tls/src/rustls_helpers.rs, warpgate-db-entities/src/SessionApprovalRequest.rs, warpgate-protocol-rdp/src/clipboard.rs, warpgate-core/src/approvals/gate.rs, warpgate-core/src/approvals/wait.rs, warpgate-protocol-rdp/src/client/input.rs, warpgate-protocol-ssh/src/server/channel_registry.rs, warpgate-core/src/approvals/self_approval.rs (+11 more). Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (21 single-owned of 286 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 286 of the 523 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: warpgate-core/src/recordings/tests.rs, warpgate-database-protocols/src/mysql/protocol/text/column.rs.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found warpgate-protocol-http/src/main.rs:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `warpgate-protocol-http/src/main.rs` makes this repository a deployable product (line 1).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 3 of 29 project(s) overshoot their size bounds, lowering Project Cohesion to 8.2/10. The most over is `warpgate-core` (15366 LoC, 140 module-visible types across 10 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 7 of 286 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; 286 of the 523 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
M2 · Architecture documentation · No ADRs · ×1
  • 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.
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.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~0.9 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 3323 source line(s) of the 40 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. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
X7 · Silent fallback defaults · Silent fallback default on Err · ×1
  • 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.
Minor — 44 finding(s)
D12 · Dependency Hygiene · Outdated · ×42
  • Outdated: aes — `aes` is locked at 0.9.2 but 0.9.4 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.2 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-lc-rs — `aws-lc-rs` is locked at 1.18.2 but 1.19.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in warpgate-ca/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-lc-rs` and commit the updated REDACTED.
  • Outdated: aws-sdk-ec2 — `aws-sdk-ec2` is locked at 1.267.0 but 1.280.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.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-ec2instanceconnect` and commit the updated REDACTED.
  • Outdated: aws-sdk-eks — `aws-sdk-eks` is locked at 1.154.0 but 1.162.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.162.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.159.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.126.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.5 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.21.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-runtime-api` and commit the updated REDACTED.
  • Outdated: aws-smithy-types — `aws-smithy-types` is locked at 1.8.1 but 1.9.4 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.11 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.31 but 1.1.33 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.2 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: openssl — `openssl` is locked at 0.10.81 but 0.10.82 is the current stable release on crates.io, and it already satisfies the `"0.10"` requirement declared in warpgate-protocol-rdp/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p openssl` and commit the updated REDACTED.
  • + 17 more in this group — see findings.md.
D5 · Coupling · Off the main sequence · ×2
  • 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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8c5477e941dc45538c5c0cd36c750d79/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8c5477e941dc45538c5c0cd36c750d79/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .75artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .24artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .23artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1db08-ab23-7996-a022-83fd24677f53 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md