Public report of nolabs-ai/nono, 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, 21:35 UTC · Survey ID cd_02f70ccefb9b4643ac03944cf7eb1954

nolabs-ai/nono

Measured 14 November 2026, 21:27 UTC, at code version 165e2f7

CAI score 71out of 100 Strong
CriticalWeakAdequateStrongExemplary
No change since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 240,615 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 2.3 person-years · Weakest lens: Code Health, 59

Findings by how serious they are

13 critical 1109 serious 114 minor

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

This survey was produced by

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

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

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

56of 56 dimensions measured by tools.
1213of 1236 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
56dimensions across 7 lenses, read from 240,615 lines of product code in 5 projects.
Chapters

Executive summary

nolabs-ai/nono meets our standard for a preview release. It scores 71 out of 100 and is rated Strong, and all 13 of its critical findings are security problems.

Code Health, at 59, is the weakest lens and counts most in the score. The best first step is writing log messages as searchable templates, worth about 10 points. Raising Code Health to 67 would lift the score to about 75.

Four pipeline steps install packages that can change without warning. Three secrets can leak from the build pipeline, and three settings leave the servers or containers unsafe. Pinning what the pipeline installs, limiting each secret to its own step and correcting the unsafe settings would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the password or key in the code's history needs replacing, with the old one switched off.

The product code is 240,615 lines, about €340,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 59 · counts for 46%Security and Compliance 75 · counts for 25%Production Readiness 83 · counts for 14%Architecture 89 · counts for 8%Maturity 89 · counts for 4%Event Sourcing 100 · counts for 2%Performance 100 · counts for 1%

If Code Health rose from 59 to 67, the lowest score rated Strong, the score would rise from 71 to about 75.

Code composition: what the lines of code are
Product code 96%Tests 4%
New since the last survey: 339 findings

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

  • Cyclomatic Complexity · nono_cli::login_cmd::run_login (cyclomatic 29) crates/nono-cli/src/login_cmd.rs
  • Cyclomatic Complexity · nono_proxy::aws::operation::resolve (cyclomatic 28) crates/nono-proxy/src/aws/operation.rs
  • Cyclomatic Complexity · nono_proxy::server::start_with_network_approval (cyclomatic 27) crates/nono-proxy/src/server.rs
  • Cyclomatic Complexity · CredentialStore::load_with_registry (cyclomatic 26) crates/nono-proxy/src/credential.rs
  • Cyclomatic Complexity · RouteStore::load_with_registry (cyclomatic 22) crates/nono-proxy/src/route.rs
  • Cyclomatic Complexity · TerminalApproval::prompt (cyclomatic 21) crates/nono-cli/src/terminal_approval.rs
  • Cyclomatic Complexity · nono_proxy::endpoint_approval::authorize_group (cyclomatic 21) crates/nono-proxy/src/endpoint_approval.rs
  • Cyclomatic Complexity · nono_cli::login_cmd::login_summary (cyclomatic 20) crates/nono-cli/src/login_cmd.rs
  • Cyclomatic Complexity · nono_proxy::aws::endpoints::validate_aws_upstream (cyclomatic 19) crates/nono-proxy/src/aws/endpoints.rs
  • Cyclomatic Complexity · nono_cli::sandbox_prepare::validate_block_net_conflicts (cyclomatic 18) crates/nono-cli/src/sandbox_prepare.rs
  • Cyclomatic Complexity · nono_cli::login_cmd::enroll_device (cyclomatic 17) crates/nono-cli/src/login_cmd.rs
  • Cyclomatic Complexity · nono_proxy::server::handle_forward_http (cyclomatic 17) crates/nono-proxy/src/server.rs
  • Cyclomatic Complexity · DetachMatcher::push (cyclomatic 16) crates/nono-cli/src/connect_client.rs
  • Cyclomatic Complexity · nono_cli::terminal_capture::delivery::run_uploader (cyclomatic 16) crates/nono-cli/src/terminal_capture/delivery.rs
  • Cyclomatic Complexity · nono_cli::terminal_prompt::read_consent_line_from (cyclomatic 16) crates/nono-cli/src/terminal_prompt.rs
  • Cognitive Complexity · CredentialStore::load_with_registry (cognitive 65) crates/nono-proxy/src/credential.rs
  • Cognitive Complexity · nono_proxy::server::start_with_network_approval (cognitive 43) crates/nono-proxy/src/server.rs
  • Cognitive Complexity · nono_proxy::endpoint_approval::authorize_group (cognitive 38) crates/nono-proxy/src/endpoint_approval.rs
  • Cognitive Complexity · nono_cli::login_cmd::run_login (cognitive 37) crates/nono-cli/src/login_cmd.rs
  • Cognitive Complexity · RouteStore::load_with_registry (cognitive 37) crates/nono-proxy/src/route.rs
  • Cognitive Complexity · nono_proxy::aws::operation::resolve (cognitive 37) crates/nono-proxy/src/aws/operation.rs
  • Cognitive Complexity · nono_cli::profile::merge_allow_domain (cognitive 28) crates/nono-cli/src/profile/mod.rs
  • Cognitive Complexity · nono_cli::terminal_prompt::read_consent_line_from (cognitive 26) crates/nono-cli/src/terminal_prompt.rs
  • Cognitive Complexity · TerminalApproval::prompt (cognitive 25) crates/nono-cli/src/terminal_approval.rs
  • Cognitive Complexity · nono_cli::command_policy::validate_endpoint_policy (cognitive 24) crates/nono-cli/src/command_policy.rs
  • Cognitive Complexity · nono_cli::terminal_capture::delivery::run_uploader (cognitive 24) crates/nono-cli/src/terminal_capture/delivery.rs
  • Cognitive Complexity · nono_cli::login_cmd::run_tenant (cognitive 21) crates/nono-cli/src/login_cmd.rs
  • Cognitive Complexity · nono::broker_path::walk_chain_with_budget (cognitive 20) crates/nono/src/broker_path.rs
  • Cognitive Complexity · Renderer::sample (cognitive 18) crates/nono-cli/src/terminal_capture/transcript.rs
  • Cognitive Complexity · nono_cli::startup_runtime::run_detached_launch (cognitive 18) crates/nono-cli/src/startup_runtime.rs
  • Cognitive Complexity · nono_proxy::server::handle_forward_http (cognitive 18) crates/nono-proxy/src/server.rs
  • Cognitive Complexity · nono_proxy::aws::endpoints::validate_aws_upstream (cognitive 17) crates/nono-proxy/src/aws/endpoints.rs
  • Cognitive Complexity · nono_proxy::server::validate_phantom_formats (cognitive 17) crates/nono-proxy/src/server.rs
  • Cognitive Complexity · Writer::run (cognitive 16) crates/nono-cli/src/terminal_capture/writer.rs
  • Cognitive Complexity · nono_cli::login_cmd::enroll_device (cognitive 16) crates/nono-cli/src/login_cmd.rs
  • Cognitive Complexity · nono_cli::terminal_capture::transcript::render (cognitive 16) crates/nono-cli/src/terminal_capture/transcript.rs
  • Cognitive Complexity · nono_proxy::aws::endpoints::resolve_signing_params (cognitive 16) crates/nono-proxy/src/aws/endpoints.rs
  • Cognitive Complexity · nono_proxy::reverse::host_endpoint_policies (cognitive 16) crates/nono-proxy/src/reverse.rs
  • God Classes · FunctionTooLong: nono_proxy::server::start_with_network_approval crates/nono-proxy/src/server.rs
  • God Classes · MethodTooLong: RouteStore.load_with_registry crates/nono-proxy/src/route.rs
  • God Classes · FileTooLong: src/login_cmd.rs crates/nono-cli/src/login_cmd.rs
  • God Classes · MethodTooLong: TerminalApproval.prompt crates/nono-cli/src/terminal_approval.rs
  • God Classes · FileTooLong: src/platform_client.rs crates/nono-cli/src/platform_client.rs
  • God Classes · FunctionTooLong: nono_cli::login_cmd::run_login crates/nono-cli/src/login_cmd.rs
  • God Classes · FileTooLong: platform_oauth/client.rs crates/nono-cli/src/platform_oauth/client.rs
  • God Classes · FileTooLong: src/route.rs crates/nono-proxy/src/route.rs
  • God Classes · FileTooLong: src/approval_runtime.rs crates/nono-cli/src/approval_runtime.rs
  • God Classes · FunctionTooLong: nono_cli::query_ext::print_result crates/nono-cli/src/query_ext.rs
  • God Classes · TooManyFields: WhyArgs crates/nono-cli/src/cli.rs
  • God Classes · FunctionTooLong: nono_cli::network_policy::resolve_credentials crates/nono-cli/src/network_policy.rs
  • God Classes · FunctionTooLong: nono_cli::login_cmd::enroll_device crates/nono-cli/src/login_cmd.rs
  • God Classes · FileTooLong: src/launch_runtime.rs crates/nono-cli/src/launch_runtime.rs
  • God Classes · FunctionTooLong: nono_proxy::reverse::host_endpoint_policies crates/nono-proxy/src/reverse.rs
  • God Classes · TooManyFields: ProfileDeserialize crates/nono-cli/src/profile/mod.rs
  • Code Duplication · Near-duplicate member pair (597 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Near-duplicate member pair (54 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Near-duplicate member pair (38 shared lines) crates/nono-proxy/src/oauth2.rs
  • Code Duplication · Near-duplicate member pair (37 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (28 corresponding lines) crates/nono-cli/src/sandbox_state.rs
  • Code Duplication · Edited copy of a member (7 corresponding lines) crates/nono-cli/src/profile_cmd.rs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) crates/nono-cli/src/command_policy.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (104 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (86 corresponding lines) crates/nono-cli/src/capability_ext.rs
  • Code Duplication · Edited copy of a member (77 corresponding lines) crates/nono/src/capability.rs
  • Code Duplication · Edited copy of a member (67 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (75 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (52 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (74 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (49 corresponding lines) crates/nono-cli/src/profile_cmd.rs
  • Code Duplication · Edited copy of a member (39 corresponding lines) crates/nono-cli/src/profile/mod.rs
  • Code Duplication · Edited copy of a member (34 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) crates/nono-cli/src/profile/mod.rs
  • Code Duplication · Edited copy of a member (51 corresponding lines) crates/nono/src/keystore.rs
  • Code Duplication · Edited copy of a member (32 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (54 corresponding lines) crates/nono/src/undo/object_store.rs
  • Code Duplication · Edited copy of a member (41 corresponding lines) crates/nono-proxy/src/audit.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) crates/nono-cli/src/audit_session.rs
  • Code Duplication · Edited copy of a member (35 corresponding lines) crates/nono-proxy/src/tls_intercept/h2_forward.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) crates/nono-cli/src/exec_strategy.rs
  • Code Duplication · Edited copy of a member (43 corresponding lines) crates/nono/src/trust/bundle.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) crates/nono-cli/src/pty_proxy.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/macos.rs
  • Code Duplication · Edited copy of a member (44 corresponding lines) crates/nono-cli/src/output.rs
  • Code Duplication · Edited copy of a member (32 corresponding lines) crates/nono/src/keystore.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (37 corresponding lines) crates/nono-proxy/src/oauth2.rs
  • Code Duplication · Edited copy of a member (39 corresponding lines) crates/nono/src/keystore.rs
  • Code Duplication · Edited copy of a member (39 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (34 corresponding lines) crates/nono-proxy/src/reverse.rs
  • Code Duplication · Edited copy of a member (41 corresponding lines) crates/nono-cli/src/proxy_runtime.rs
  • Code Duplication · Edited copy of a member (28 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) crates/nono/src/trust/signing.rs
  • Code Duplication · Edited copy of a member (28 corresponding lines) crates/nono-cli/src/wiring.rs
  • Code Duplication · Edited copy of a member (26 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) crates/nono-cli/src/audit_commands.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) crates/nono-cli/src/pack_update_hint.rs
  • Code Duplication · Edited copy of a member (30 corresponding lines) crates/nono-cli/src/wiring.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (32 corresponding lines) bindings/c/src/capability_set.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: 127 findings

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

  • Cyclomatic Complexity · nono_proxy::server::start_with_nonce_resolver (cyclomatic 27) crates/nono-proxy/src/server.rs
  • Cyclomatic Complexity · CredentialStore::load_with_diagnostics (cyclomatic 19) crates/nono-proxy/src/credential.rs
  • Cognitive Complexity · CredentialStore::load_with_diagnostics (cognitive 45) crates/nono-proxy/src/credential.rs
  • Cognitive Complexity · nono_proxy::server::start_with_nonce_resolver (cognitive 43) crates/nono-proxy/src/server.rs
  • Cognitive Complexity · RouteStore::load (cognitive 16) crates/nono-proxy/src/route.rs
  • God Classes · MethodTooLong: CredentialStore.load_with_diagnostics crates/nono-proxy/src/credential.rs
  • God Classes · FunctionTooLong: nono_proxy::server::start_with_nonce_resolver crates/nono-proxy/src/server.rs
  • God Classes · MethodTooLong: RouteStore.load crates/nono-proxy/src/route.rs
  • Code Duplication · Near-duplicate member pair (298 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Near-duplicate member pair (54 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Near-duplicate member pair (45 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Near-duplicate member pair (39 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Near-duplicate member pair (37 shared lines) crates/nono-proxy/src/tls_intercept/handle.rs
  • Code Duplication · Near-duplicate member pair (33 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Edited copy of a member (28 corresponding lines) crates/nono-cli/src/sandbox_state.rs
  • Code Duplication · Edited copy of a member (7 corresponding lines) crates/nono-cli/src/profile_cmd.rs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) crates/nono-cli/src/command_policy.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (64–65 lines × 2) crates/nono-cli/src/query_ext.rs
  • Code Duplication · Duplicated block (30–34 lines × 2) crates/nono-cli/src/profile_save_runtime.rs
  • Code Duplication · Duplicated block (28–29 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (28–29 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs
  • Code Duplication · Duplicated block (26 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (24 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (20–22 lines × 2) crates/nono-proxy/src/reverse.rs
  • Code Duplication · Duplicated block (20–21 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (21 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (20 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (18–19 lines × 2) crates/nono-cli/src/session.rs
  • Code Duplication · Duplicated block (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (17–19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs
  • Code Duplication · Duplicated block (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs
  • Code Duplication · Duplicated block (18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (17–18 lines × 2) crates/nono/src/undo/snapshot.rs
  • Code Duplication · Duplicated block (15–17 lines × 2) crates/nono-cli/src/exec_strategy.rs
  • Code Duplication · Duplicated block (17 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (17 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs
  • Code Duplication · Duplicated block (17 lines × 2) crates/nono-proxy/src/reverse.rs
  • Code Duplication · Duplicated block (16 lines × 3) crates/nono-cli/src/registry_client.rs
  • Code Duplication · Duplicated block (14–16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (16 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs
  • Code Duplication · Duplicated block (14–15 lines × 2) crates/nono-cli/src/diagnostic/formatter.rs
  • Code Duplication · Duplicated block (15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (9–15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (14 lines × 2) crates/nono-proxy/src/reverse.rs
  • Code Duplication · Duplicated block (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (11–13 lines × 2) crates/nono-cli/src/why_runtime.rs
  • Code Duplication · Duplicated block (10–12 lines × 2) crates/nono-cli/src/profile/mod.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (11–12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/nono-proxy/src/reverse.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs
  • Code Duplication · Duplicated block (11 lines × 4) crates/nono-proxy/src/tls_intercept/handle.rs
  • Code Duplication · Duplicated block (10–11 lines × 2) crates/nono-cli/src/command_policy.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/nono-cli/src/command_policy.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/nono-cli/src/proxy_command.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (10–11 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (10–11 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/nono-cli/src/trust_keystore.rs
  • Code Duplication · Duplicated block (10–11 lines × 2) crates/nono-proxy/src/reverse.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/nono-proxy/src/server.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/nono/src/keystore.rs
  • Code Duplication · Duplicated block (10 lines × 4) crates/nono-cli/src/trust_keystore.rs
  • Code Duplication · Duplicated block (8–10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (9–10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (10 lines × 2) crates/nono-proxy/src/connect.rs
  • Code Duplication · Duplicated block (10 lines × 2) crates/nono-proxy/src/credential.rs
  • Code Duplication · Duplicated block (9–10 lines × 2) crates/nono-proxy/src/reverse.rs
  • Code Duplication · Duplicated block (10 lines × 2) crates/nono-proxy/src/tls_intercept/h2_forward.rs
  • Code Duplication · Duplicated block (9 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (9 lines × 2) crates/nono-cli/src/proxy_runtime.rs
  • Code Duplication · Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/dynamic_providers.rs
  • Code Duplication · Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/policy.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/nono-cli/src/audit_client.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/nono-cli/src/connect_client.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/nono-cli/src/proxy_command.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/nono/src/supervisor/socket.rs
  • Code Duplication · Duplicated block (7 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/nono-cli/src/proxy_runtime.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (6 lines × 2) crates/nono-cli/src/profile/mod.rs
  • Code Duplication · Duplicated block (6 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs
  • Code Duplication · Duplicated block (14 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs
  • Code Duplication · Duplicated block (13 lines × 3) crates/nono-proxy/src/reverse.rs
Rebuild cost: about €340,000 · Estimate
Cost to rebuild€110,000 to €560,000, for 1,866 to 5,921 hours of work, about 2.3 person-years for 1 to 5 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×1.0 at a score of 71. 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.
SizeLarge: 240,615 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
Interpolated log message defeats structured logging
Raises the score by about 10 points · Medium effort · Structured logging
2
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.
Raises the score by about 2 points · Medium effort · Web-Security Posture
3
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with nono_cli::exec_strategy::execute_supervised (cyclomatic 115), nono_cli::profile_cmd::cmd_diff (cyclomatic 62).
Raises the score by about 0.9 points · Medium effort · Cyclomatic Complexity

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.

Files that change often carry extra risk · Combined risk
15 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (43 files) · Code Coverage (56 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: exec_strategy.rs, mod.rs and execution_runtime.rs
What to do: Add tests to these files and have a second person review every change to them, starting with exec_strategy.rs, mod.rs and execution_runtime.rs.
Where the investment is most exposed · Value at risk
This code would cost about €340,000 to build again, about 2.3 person-years of work. Its weakest lens is Code Health, at 59 (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
Interpolated log message defeats structured logging. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 10% on every change. The history of the code shows how much it changes: about 113,282 lines over the last 90 days, which is about 459,421 lines a year. At that pace, the extra work comes to an estimated 49.4 to 296.5 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch nono nono nono-cli nono-cli nono-cli->nono nono-proxy nono-proxy nono-cli->nono-proxy nono-ffi nono-ffi nono-ffi->nono nono-proxy->nono

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.

226 modules, with 485 dependencies between them. 4 loops run through 9 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 186 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 nono.capability2 nono.scrub3 nono.undo.types4 nono_cli.package5 nono_proxy.approval6 nono_proxy.secret_registry7 nono.diagnostic.codes8 nono.supervisor.types9 nono_cli.audit_session10 nono_proxy.audit11 nono_proxy.config12 nono.audit13 nono.diagnostic.records14 nono.error15 nono_cli.command_policy16 nono_cli.platform_oauth.client17 nono_proxy.credential18 nono_proxy.route19 nono_cli.diagnostic.formatter20 nono_cli.platform_oauth.session21 nono_cli.profile22 nono_proxy.reverse23 nono_proxy.server24 nono_proxy.tls_intercept.handle25 nono_cli.cli26 nono_cli.output27 nono_cli.policy28 nono_cli.terminal_capture29 nono_cli.platform_client30 nono_cli.pty_proxy31 nono_cli.sandbox_prepare32 nono_cli.exec_strategy.supervisor_linux33 nono_cli.exec_strategy34 nono_cli.exec_strategy.clone_files35 nono_cli.launch_runtime36 nono_cli.proxy_runtime37 nono_cli.rollback_runtime38 nono_cli.tool-sandbox.platform.linux39 nono_cli.supervised_runtime40 nono_cli.tool-sandbox.platform.macos
1 nono.capability
2 nono.scrub
3 nono.undo.types
4 nono_cli.package
5 nono_proxy.approval
6 nono_proxy.secret_registry
7 nono.diagnostic.codes1
8 nono.supervisor.types1
9 nono_cli.audit_session2
10 nono_proxy.audit11
11 nono_proxy.config11
12 nono.audit3242
13 nono.diagnostic.records21
14 nono.error2
15 nono_cli.command_policy11
16 nono_cli.platform_oauth.client1
17 nono_proxy.credential232
18 nono_proxy.route414
19 nono_cli.diagnostic.formatter6234
20 nono_cli.platform_oauth.session12
21 nono_cli.profile1118
22 nono_proxy.reverse312153
23 nono_proxy.server121512
24 nono_proxy.tls_intercept.handle2144
25 nono_cli.cli2
26 nono_cli.output3111
27 nono_cli.policy5113
28 nono_cli.terminal_capture21
29 nono_cli.platform_client2141
30 nono_cli.pty_proxy2
31 nono_cli.sandbox_prepare431011
32 nono_cli.exec_strategy.supervisor_linux313122
33 nono_cli.exec_strategy514117321121
34 nono_cli.exec_strategy.clone_files1111
35 nono_cli.launch_runtime11581123
36 nono_cli.proxy_runtime22122771112
37 nono_cli.rollback_runtime1141111
38 nono_cli.tool-sandbox.platform.linux5216191
39 nono_cli.supervised_runtime2211111161
40 nono_cli.tool-sandbox.platform.macos52161111114
Uses a module listed above itPart of a loopThe module itself
1 nono.capability2 nono.scrub3 nono.undo.types4 nono_cli.package5 nono_proxy.approval6 nono_proxy.secret_registry7 nono.diagnostic.codes8 nono.supervisor.types9 nono_cli.audit_session10 nono_proxy.audit11 nono_proxy.config12 nono.audit13 nono.diagnostic.records14 nono.error15 nono_cli.command_policy16 nono_cli.platform_oauth.client17 nono_proxy.credential18 nono_proxy.route19 nono_cli.diagnostic.formatter20 nono_cli.platform_oauth.session21 nono_cli.profile22 nono_proxy.reverse23 nono_proxy.server24 nono_proxy.tls_intercept.handle25 nono_cli.cli26 nono_cli.output27 nono_cli.policy28 nono_cli.terminal_capture29 nono_cli.platform_client30 nono_cli.pty_proxy31 nono_cli.sandbox_prepare32 nono_cli.exec_strategy.supervisor_linux33 nono_cli.exec_strategy34 nono_cli.exec_strategy.clone_files35 nono_cli.launch_runtime36 nono_cli.proxy_runtime37 nono_cli.rollback_runtime38 nono_cli.tool-sandbox.platform.linux39 nono_cli.supervised_runtime40 nono_cli.tool-sandbox.platform.macosnono.capability1nono.scrub2nono.undo.types3nono_cli.package4nono_proxy.approval5nono_proxy.secret_registry6nono.diagnostic.codes7nono.supervisor.types8nono_cli.audit_session9nono_proxy.audit10nono_proxy.config11nono.audit12nono.diagnostic.records13nono.error14nono_cli.command_policy15nono_cli.platform_oauth.client16nono_proxy.credential17nono_proxy.route18nono_cli.diagnostic.formatter19nono_cli.platform_oauth.session20nono_cli.profile21nono_proxy.reverse22nono_proxy.server23nono_proxy.tls_intercept.handle24nono_cli.cli25nono_cli.output26nono_cli.policy27nono_cli.terminal_capture28nono_cli.platform_client29nono_cli.pty_proxy30nono_cli.sandbox_prepare31nono_cli.exec_strategy.supervisor_linux32nono_cli.exec_strategy33nono_cli.exec_strategy.clone_files34nono_cli.launch_runtime35nono_cli.proxy_runtime36nono_cli.rollback_runtime37nono_cli.tool-sandbox.platform.linux38nono_cli.supervised_runtime39nono_cli.tool-sandbox.platform.macos40112111132422121112324146234121118312153121512214423111511321214124310113131225141173211211111115811232212277111211411115216191221111116152161111114+186 more modules (most-connected shown)

At a glance — Code Health · 59% · Adequate · gated by D2, X4 ·

At a glance — Architecture · 89% · Adequate · gated by D26 ·

At a glance — Maturity · 89% · Exemplary ·

At a glance — Readiness · 83% · Exemplary ·

At a glance — Security · 75% · Adequate · gated by D29 ·

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

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
A02:2025 — Security Misconfiguration38High / Critical
A05:2025 — Injection11High / Critical
A03:2025 — Software Supply Chain Failures11Medium
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: Interpolated log message defeats structured logging; 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; Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with nono_cli::exec_strategy::execute_supervised (cognitive 219), nono_proxy::server::handle_connection (cognitive 140), nono_cli::profile_cmd::cmd_diff (cognitive 121).

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

Do thisHelpsEffortDimension
Interpolated log message defeats structured logging+9.9 ptsMediumStructured logging
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.+2.1 ptsMediumWeb-Security Posture
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with nono_cli::exec_strategy::execute_supervised (cyclomatic 115), nono_cli::profile_cmd::cmd_diff (cyclomatic 62).+0.9 ptsMediumCyclomatic Complexity
Resolve the 1 No network policy finding(s) in Network Egress Confinement.+0.9 ptsLowNetwork Egress Confinement
Resolve the 2 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (2).+0.9 ptsLowKernel & Syscall Confinement
Resolve the 56 Low coverage finding(s) in Code Coverage — start with app_runtime.rs, audit_client.rs, audit_commands.rs.+0.9 ptsMediumCode Coverage
Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with nono_cli::exec_strategy::execute_supervised (cognitive 219), nono_proxy::server::handle_connection (cognitive 140), nono_cli::profile_cmd::cmd_diff (cognitive 121).+1.5 ptsHighCognitive Complexity
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED.+0.7 ptsLowStatic Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 156 files carrying findings, judged against the Preview bar: 1% slop · 27% mixed · 72% near-clean.

FileScoreBandWorst signal
REDACTED2.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
crates/nono-cli/src/audit_commands.rs4.0MixedCyclomatic Complexity: nono_cli::audit_commands::cmd_show (cyclomatic 33)
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
crates/nono-cli/src/profile_cmd.rs5.5MixedCyclomatic Complexity: nono_cli::profile_cmd::cmd_diff (cyclomatic 62)
crates/nono-cli/src/exec_strategy/supervisor_linux.rs5.5MixedCyclomatic Complexity: nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification (cyclomatic 47)
crates/nono-cli/src/exec_strategy/clone_files.rs5.5MixedCyclomatic Complexity: nono_cli::exec_strategy::clone_files::child_exec (cyclomatic 43)
crates/nono-cli/src/tool-sandbox/platform/linux.rs5.5MixedCyclomatic Complexity: nono_cli::tool-sandbox::platform::linux::handle_shim_stream_inner (cyclomatic 39)
crates/nono-cli/src/profile/mod.rs5.5MixedCyclomatic Complexity: nono_cli::profile::validate_custom_credential (cyclomatic 34)
crates/nono-cli/src/pty_proxy.rs5.5MixedCyclomatic Complexity: nono_cli::pty_proxy::run_attach_loop (cyclomatic 34)
crates/nono-cli/src/output.rs5.5MixedCyclomatic Complexity: nono_cli::output::print_capabilities (cyclomatic 26)
crates/nono-cli/src/proxy_runtime.rs5.5MixedCyclomatic Complexity: nono_cli::proxy_runtime::prepare_proxy_launch_options (cyclomatic 26)
crates/nono/src/capability.rs5.5MixedCyclomatic Complexity: nono::capability::tokenize_sexp (cyclomatic 25)
crates/nono-cli/src/connect_client.rs5.5MixedCyclomatic Complexity: nono_cli::connect_client::attach (cyclomatic 23)
crates/nono-cli/src/profile_save_runtime.rs5.5MixedCyclomatic Complexity: nono_cli::profile_save_runtime::interactive_denial_selector (cyclomatic 23)
crates/nono-cli/src/login_cmd.rs5.5MixedCyclomatic Complexity: nono_cli::login_cmd::run_login (cyclomatic 29)
crates/nono-cli/src/trust_scan.rs5.5MixedCyclomatic Complexity: nono_cli::trust_scan::run_pre_exec_scan (cyclomatic 27)
crates/nono-proxy/src/oauth2.rs5.5MixedGod Classes: FunctionTooLong: nono_proxy::oauth2::exchange_token
crates/nono-cli/src/why_runtime.rs5.5MixedCyclomatic Complexity: nono_cli::why_runtime::run_why (cyclomatic 24)

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

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

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

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

Could not be resolved — 21

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

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 56 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 — 56 dimensions across the health lenses
D1D2D3D4D5D6D7D8D12D13D14D15D16D17D19D20D26D28D29D30D31D34D35D36D37D40D41D42D43D44AX10AX3AX4AX8AX9ES1ES2M1M2M3M4P1P10P2P3P4P6PF3S1X1X14X15X21X28X30X4

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, 1213 of 1236 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 01a1dbf5-a618-70c9-bc3e-6ff5d3c95718.

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.

  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 227 test files), but it was not re-run: its build outgrew the 7 GB scratch ceiling (7.922 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • 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.
  • 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 — 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D27 Navigability — not measured this run — 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.
  • 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — 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 REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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. 532 further occurrence(s) are not listed individually; the score already reflects all 572.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality 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.
  • 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.
  • D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • 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".
  • 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 Complexity5.4 / 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 5.4 / 10 · rule-coverage 100% · ceiling Prevented

117 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was nono_cli::exec_strategy::execute_supervised at 115. A further 3 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being nono_cli::app_runtime::dispatch_command at 32 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/nono-cli/src/app_runtime.rs (nono_cli::app_runtime::dispatch_command at 32), bindings/c/src/lib.rs (nono_ffi::map_error at 23), bindings/c/src/types.rs (NonoDiagnosticCode::from at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

nono_cli::exec_strategy::execute_supervised (cyclomatic 115) · ×80crates/nono-cli/src/exec_strategy.rs:572
nono_proxy::tls_intercept::handle::handle_inner_request (cyclomatic 47) · ×13crates/nono-proxy/src/tls_intercept/handle.rs:1018
CapabilitySet::from_profile (cyclomatic 52) · ×5crates/nono-cli/src/capability_ext.rs:693
nono::audit::verify_audit_attestation_bundle (cyclomatic 25) · ×4crates/nono/src/audit.rs:1258
DiagnosticFormatter::format_supervised_footer_with_diagnostics (cyclomatic 26) · ×3crates/nono-cli/src/diagnostic/formatter.rs:1313

+ 10 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 Cyclomatic Complexity — start with nono_cli::exec_strategy::execute_supervised (cyclomatic 115), nono_cli::profile_cmd::cmd_diff (cyclomatic 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.4 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D2 · Cognitive Complexity2.1 / 10Critical✓ 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 2.1 / 10 · rule-coverage 100% · ceiling Prevented

204 function(s) exceeded the cognitive complexity threshold of 15; the worst was nono_cli::exec_strategy::execute_supervised at 219.

nono_cli::exec_strategy::execute_supervised (cognitive 219) · ×131crates/nono-cli/src/exec_strategy.rs:572
nono_proxy::server::handle_connection (cognitive 140) · ×24crates/nono-proxy/src/server.rs:1719
nono::capability::tokenize_sexp (cognitive 63) · ×14crates/nono/src/capability.rs:682
CapabilitySet::from_profile (cognitive 103) · ×6crates/nono-cli/src/capability_ext.rs:693
SnapshotManager::walk_and_store (cognitive 43) · ×5crates/nono/src/undo/snapshot.rs:732

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

What to do

  1. Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with nono_cli::exec_strategy::execute_supervised (cognitive 219), nono_proxy::server::handle_connection (cognitive 140), nono_cli::profile_cmd::cmd_diff (cognitive 121). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 2.1 to about 3.4/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

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

D3 · God Classes8.9 / 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.9 / 10 · rule-coverage 100% · ceiling Prevented

125 god class(es) detected.

FunctionTooLong: nono_cli::execution_runtime::execute_sandboxed · ×59crates/nono-cli/src/execution_runtime.rs:203
FileTooLong: src/exec_strategy.rs · ×43crates/nono-cli/src/exec_strategy.rs
TooManyFields: PreparedSandbox · ×8crates/nono-cli/src/sandbox_prepare.rs:529
MethodTooLong: CapabilitySet.from_profile · ×6crates/nono-cli/src/capability_ext.rs:693
ClassTooLong: DiagnosticFormatter · ×6crates/nono-cli/src/diagnostic/formatter.rs:651

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

What to do

  1. Resolve the 59 FunctionTooLong finding(s) in God Classes — start with reverse.rs (6), profile_cmd.rs (5), handle.rs (5). — One of this dimension's main actionable groups (59 warning-level).
  2. Resolve the 43 FileTooLong finding(s) in God Classes — start with exec_strategy.rs, mod.rs, proxy_runtime.rs. — One of this dimension's main actionable groups (43 warning-level).
  3. Resolve the 8 TooManyFields finding(s) in God Classes — start with cli.rs (3), sandbox_prepare.rs, profile_runtime.rs. — One of this dimension's main actionable groups (8 warning-level).

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

D4 · Code Duplication7.6 / 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.6 / 10 · rule-coverage 100% · ceiling Verified

360 duplicated block group(s) detected. 5.9 % of the production lines (14,236 of 240,615) are in a reported copy. A further 147 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 15 of the 507 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (10 lines × 2) · ×25crates/nono-cli/src/capability_ext.rs:922
Duplicated block (9 lines × 2) · ×23crates/nono-cli/src/capability_ext.rs:720
Duplicated block (13 lines × 2) · ×21bindings/c/src/capability_set.rs:314
Duplicated block (8 lines × 2) · ×20crates/nono-cli/src/audit_client.rs:396
Duplicated block (11 lines × 2) · ×17crates/nono-cli/src/audit_commands.rs:313

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

What to do

  1. Resolve the 25 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with linux.rs (8), capability_ext.rs (2), reverse.rs (2). — One of this dimension's main actionable groups (25 warning-level).
  2. Resolve the 23 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with linux.rs (7), pty_proxy.rs (2), snapshot.rs (2). — One of this dimension's main actionable groups (23 warning-level).
  3. Resolve the 21 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with linux.rs (5), exec_strategy.rs (3), proxy_runtime.rs (2). — One of this dimension's main actionable groups (21 warning-level).

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

D5 · Coupling8.0 / 10Strong✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

4 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.

Off the main sequence: nono

What to do

  1. Resolve the 1 Off the main sequence 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)9.9 / 10Stronggated by 1 serious finding✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 of 138 classes have LCOM4 above 3.

Low cohesion: CapabilitySet (LCOM4 12)crates/nono/src/capability.rs:952

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with capability.rs. — One of this dimension's main actionable groups (1 warning-level).

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

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Detailed fixes: d7_recommendation.md.

D8 · Code Coverage9.1 / 10Stronggated by 56 serious findings✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

Line coverage 57.3% — 56 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 218 production file(s), 35 test binaries and 1 doc-test binaries).

Low coverage: crates/nono-cli/src/app_runtime.rs · ×56crates/nono-cli/src/app_runtime.rs:1

What to do

  1. Resolve the 56 Low coverage finding(s) in Code Coverage — start with app_runtime.rs, audit_client.rs, audit_commands.rs. — One of this dimension's main actionable groups (56 warning-level).

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

D12 · Dependency Hygiene9.5 9.4 / 10Exemplary✓ 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 9.4 / 10 · rule-coverage 99% · ceiling Verified

10 outdated, 0 yanked direct Cargo dependencies. 81 of 82 direct crates were graded against crates.io (0 not published there, 1 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: aho-corasick · ×10

✓ On the Gold path — maintain.

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

D13 · REDACTED 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

REDACTED scan ran and found no leaked secrets.

✓ 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 492 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots8.9 / 10Strong✓ 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 8.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: crates/nono-cli/src/exec_strategy.rs (23×115=2645); crates/nono-proxy/src/server.rs (27×44=1188); crates/nono-proxy/src/tls_intercept/handle.rs (22×47=1034) Repeated repair below the complexity floor: crates/nono-cli/src/tool-sandbox/mod.rs (6 of 9 changes were fixes); crates/nono-cli/src/network_policy.rs (4 of 7 changes were fixes); crates/nono-cli/src/sandbox_state.rs (4 of 6 changes were fixes)

Hotspot: crates/nono-cli/src/exec_strategy.rs · ×35crates/nono-cli/src/exec_strategy.rs:572
Repeated repair: crates/nono-cli/src/tool-sandbox/mod.rs · ×12crates/nono-cli/src/tool-sandbox/mod.rs:333

What to do

  1. Resolve the 35 Hotspot finding(s) in Churn × Complexity Hotspots — start with linux.rs (2), macos.rs (2), exec_strategy.rs. — One of this dimension's main actionable groups (35 warning-level).
  2. Resolve the 12 Repeated repair finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), network_policy.rs, sandbox_state.rs. — One of this dimension's main actionable groups (12 warning-level).

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

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

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

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

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

12 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/nono-cli/src/connect_client.rs. Counted over 221 of the 236 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 2 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

2 deducted task-comment markers across 240615 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 · ×2crates/nono-cli/src/exec_strategy.rs:4079

What to do

  1. Resolve the 2 TodoComment finding(s) in Explicit Debt — start with exec_strategy.rs, trust_cmd.rs. — One of this dimension's main actionable groups (2 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. 70 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 9 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D26 · Project Cohesion0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

3 of 5 build units (Cargo) 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)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)1.9 / 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 1.9 / 10 · rule-coverage 100% · ceiling Documented

11 finding(s): 0 critical, 9 high, 2 medium, 0 low. semgrep hit a parse error in 8 file(s) — `crates/nono-cli/src/sandbox_prepare.rs` (line 1634, lines 1634–1676, lines 1676–1677), `crates/nono-cli/src/session.rs` (line 182, line 190), `crates/nono-cli/src/setup.rs` (line 131, line 160, line 447), `crates/nono-cli/src/tool-sandbox/platform/macos.rs` (line 64, line 73), `crates/nono/src/sandbox/macos.rs` (line 24, line 27, line 33, …), … (+3 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 7 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

What to do

  1. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D30 · Dependency Vulnerabilities9.2 / 10Stronggated by 4 serious findings✓ 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 9.2 / 10 · rule-coverage 100% · ceiling Documented

4 finding(s): 0 critical, 0 high, 4 medium, 0 low.

REDACTED

What to do

  1. Resolve the 4 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — 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 Security5.6 / 10Adequate✓ 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 5.6 / 10 · rule-coverage 100% · ceiling Documented

38 finding(s): 0 critical, 3 high, 34 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 34 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (19), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (34 warning-level).
  2. Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D34 · Knowledge Freshness10.0 / 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 221 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/nono-proxy/src/rate_limit.rs. Counted over 221 of the 236 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned filecrates/nono-proxy/src/rate_limit.rs:1

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.7 / 10Stronggated by 4 serious 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.7 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: proxy_runtime.rs↔h2_forward.rs 58%; cli.rs↔package.rs 55%; mod.rs↔credential.rs 54%

Change coupling: proxy_runtime.rs ↔ h2_forward.rs · ×4crates/nono-cli/src/proxy_runtime.rs:1

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with proxy_runtime.rs, cli.rs, mod.rs. — One of this dimension's main actionable groups (4 warning-level).

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

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
REDACTED

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

What to do

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

0/2 workload(s) run every container under a seccomp profile; 0/2 declare an AppArmor/SELinux profile.

No seccomp profile · ×2REDACTED:2

What to do

  1. Resolve the 2 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

D42 · Runtime Threat Enforcement8.0 / 10Strong✓ Tool-verified

What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.

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

1/2 runtime-enforcement controls present (threat detection, admission control).

No runtime threat detection

What to do

  1. Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d42_recommendation.md · top locations in Appendix A, every location in findings.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.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.8 / 10Exemplary✓ 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.

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)8.5 / 10Exemplary✓ 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.

M2 · Architecture documentation8.0 / 10Strong✓ 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.

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 & versioning9.9 / 10Exemplary✓ Tool-verified

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

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language'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.

  • 2 public types in `nono.diagnostic.detail` are marked as implementation by their own namespace, folder or name: `NonoDiagnosticDetail` (crates/nono/src/diagnostic/detail.rs:9, `detail`), `StderrObservationKind` (crates/nono/src/diagnostic/detail.rs:32, `detail`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — crates/nono/src/diagnostic/detail.rs:9

What to do

  • Hide `nono.diagnostic.detail` (`NonoDiagnosticDetail`, `StderrObservationKind`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability6.8 / 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.

  • Only 3/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.

  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:5

What to do

  • Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.

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.

S1 · Web-Security Posture8.0 / 10Strong✓ 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 (`hyper` (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.

  • 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. — crates/nono-proxy/src/tls_intercept/websocket.rs:22

What to do

  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
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.

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.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

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 logging1.6 / 10Critical✓ 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.

  • `warn!` at line 148 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:148
  • `warn!` at line 172 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:172
  • `warn!` 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: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:193
  • `warn!` at line 276 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:276
  • `warn!` at line 304 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:304
  • `info!` at line 321 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:321
  • `info!` at line 341 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:341
  • `info!` at line 441 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:441
  • `info!` at line 470 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:470
  • `info!` at line 531 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/audit.rs:531
  • `debug!` at line 232 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:232
  • `debug!` at line 240 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:240
  • `debug!` at line 244 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:244
  • `debug!` at line 338 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:338
  • `warn!` at line 576 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:576
  • `warn!` at line 582 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:582
  • `warn!` at line 591 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:591
  • `warn!` at line 630 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:630
  • `debug!` at line 674 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:674
  • `debug!` at line 678 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/connect.rs:678
  • `debug!` at line 343 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:343
  • `warn!` at line 359 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:359
  • `debug!` at line 450 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:450
  • `warn!` at line 473 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:473
  • `warn!` at line 520 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:520
  • `debug!` at line 531 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:531
  • `warn!` at line 597 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:597
  • `debug!` at line 616 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:616
  • `debug!` at line 634 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:634
  • `debug!` at line 642 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:642
  • `debug!` at line 675 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:675
  • `warn!` at line 686 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:686
  • `warn!` at line 846 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/credential.rs:846
  • `warn!` at line 78 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/endpoint_approval.rs:78
  • `warn!` at line 162 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/endpoint_approval.rs:162
  • `warn!` at line 184 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/endpoint_approval.rs:184
  • `warn!` at line 350 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/endpoint_approval.rs:350
  • `debug!` at line 198 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/external.rs:198
  • `debug!` at line 203 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/external.rs:203
  • `debug!` at line 324 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/nono-proxy/src/external.rs:324

What to do

  • Interpolated log message defeats structured logging

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 Health59%Adequate — gated by D2, X4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture89%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity89%ExemplarySolid.
Readiness83%ExemplarySolid.
Security75%Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event Sourcing100%ExemplaryStrongest area.
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.

  • X10 Duplicated predicate — 33 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X9 Subsumed condition operand — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 58 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's Python 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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
  • AX2 Stateful singletons — 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.
  • 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~9939 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — N/A — too few peers to establish a naming convention (15553 declarations, no unit with a dominant convention).
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (nono-cli), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — None of 4 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • 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) — 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.
  • DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 43 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage data present for 218 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — 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.
  • X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 13 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 1109 finding(s)
D2 · Cognitive Complexity · nono_cli · ×131
  • nono_cli::exec_strategy::execute_supervised (cognitive 219) crates/nono-cli/src/exec_strategy.rs:572 — nono_cli::exec_strategy::execute_supervised has cognitive complexity 219 (threshold 15). Drivers by points: if/else 87 (168 pts), boolean chains 25, match/switch 9 (24 pts), loops 2 (nesting depth added 96). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::profile_cmd::cmd_diff (cognitive 121) crates/nono-cli/src/profile_cmd.rs:1489 — nono_cli::profile_cmd::cmd_diff has cognitive complexity 121 (threshold 15). Drivers by points: if/else 40 (77 pts), loops 18 (36 pts), boolean chains 8 (nesting depth added 55). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::execution_runtime::execute_sandboxed (cognitive 89) crates/nono-cli/src/execution_runtime.rs:203 — nono_cli::execution_runtime::execute_sandboxed has cognitive complexity 89 (threshold 15). Drivers by points: if/else 43 (55 pts), boolean chains 12, match/switch 6 (12 pts), loops 6 (10 pts) (nesting depth added 22). 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.
  • nono_cli::profile_cmd::cmd_show (cognitive 83) crates/nono-cli/src/profile_cmd.rs:883 — nono_cli::profile_cmd::cmd_show has cognitive complexity 83 (threshold 15). Drivers by points: if/else 40 (54 pts), loops 10 (20 pts), boolean chains 6, match/switch 1 (3 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification (cognitive 74) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:248 — nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification has cognitive complexity 74 (threshold 15). Drivers by points: if/else 31 (48 pts), match/switch 12 (19 pts), boolean chains 7 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::tool-sandbox::platform::linux::handle_shim_stream_inner (cognitive 72) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1269 — nono_cli::tool-sandbox::platform::linux::handle_shim_stream_inner has cognitive complexity 72 (threshold 15). Drivers by points: if/else 28 (48 pts), match/switch 13 (24 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::command_policy::validate_credential (cognitive 70) crates/nono-cli/src/command_policy.rs:2763 — nono_cli::command_policy::validate_credential has cognitive complexity 70 (threshold 15). Drivers by points: if/else 29 (52 pts), boolean chains 17, match/switch 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::pty_proxy::run_attach_loop (cognitive 69) crates/nono-cli/src/pty_proxy.rs:2869 — nono_cli::pty_proxy::run_attach_loop has cognitive complexity 69 (threshold 15). Drivers by points: if/else 19 (55 pts), match/switch 3 (10 pts), boolean chains 3, loops 1 (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::tool-sandbox::platform::macos::handle_shim_stream_inner (cognitive 69) crates/nono-cli/src/tool-sandbox/platform/macos.rs:992 — nono_cli::tool-sandbox::platform::macos::handle_shim_stream_inner has cognitive complexity 69 (threshold 15). Drivers by points: if/else 28 (47 pts), match/switch 12 (22 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::profile::validate_credential_capture_entries (cognitive 64) crates/nono-cli/src/profile/mod.rs:1527 — nono_cli::profile::validate_credential_capture_entries has cognitive complexity 64 (threshold 15). Drivers by points: if/else 19 (44 pts), boolean chains 9, loops 4 (9 pts), match/switch 1 (2 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::exec_strategy::run_supervisor_loop_inner (cognitive 61) crates/nono-cli/src/exec_strategy.rs:3096 — nono_cli::exec_strategy::run_supervisor_loop_inner has cognitive complexity 61 (threshold 15). Drivers by points: if/else 17 (40 pts), boolean chains 12, match/switch 3 (8 pts), loops 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::sandbox_prepare::prepare_sandbox (cognitive 61) crates/nono-cli/src/sandbox_prepare.rs:1482 — nono_cli::sandbox_prepare::prepare_sandbox has cognitive complexity 61 (threshold 15). Drivers by points: if/else 30 (42 pts), loops 4 (10 pts), boolean chains 9 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::exec_strategy::supervisor_linux::handle_received_network_notification (cognitive 55) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:1273 — nono_cli::exec_strategy::supervisor_linux::handle_received_network_notification has cognitive complexity 55 (threshold 15). Drivers by points: if/else 13 (29 pts), match/switch 10 (22 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::policy::apply_macos_keychain_db_exception (cognitive 52) crates/nono-cli/src/policy.rs:1486 — nono_cli::policy::apply_macos_keychain_db_exception has cognitive complexity 52 (threshold 15). Drivers by points: if/else 11 (22 pts), match/switch 9 (18 pts), loops 6 (8 pts), boolean chains 4 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::output::print_capabilities (cognitive 51) crates/nono-cli/src/output.rs:97 — nono_cli::output::print_capabilities has cognitive complexity 51 (threshold 15). Drivers by points: if/else 25 (39 pts), loops 3 (6 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::exec_strategy::handle_supervisor_message (cognitive 49) crates/nono-cli/src/exec_strategy.rs:3555 — nono_cli::exec_strategy::handle_supervisor_message has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (32 pts), match/switch 6 (16 pts), boolean chains 1 (nesting depth added 27). 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.
  • nono_cli::profile_cmd::cmd_validate (cognitive 49) crates/nono-cli/src/profile_cmd.rs:2487 — nono_cli::profile_cmd::cmd_validate has cognitive complexity 49 (threshold 15). Drivers by points: if/else 19 (33 pts), loops 7 (12 pts), boolean chains 3, match/switch 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::audit_commands::cmd_show (cognitive 48) crates/nono-cli/src/audit_commands.rs:348 — nono_cli::audit_commands::cmd_show has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (30 pts), loops 5 (10 pts), match/switch 3 (8 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::policy::apply_deny_overrides (cognitive 48) crates/nono-cli/src/policy.rs:1895 — nono_cli::policy::apply_deny_overrides has cognitive complexity 48 (threshold 15). Drivers by points: if/else 19 (37 pts), loops 3 (5 pts), match/switch 1 (4 pts), boolean chains 2 (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.
  • nono_cli::exec_strategy::clone_files::child_exec (cognitive 46) crates/nono-cli/src/exec_strategy/clone_files.rs:443 — nono_cli::exec_strategy::clone_files::child_exec has cognitive complexity 46 (threshold 15). Drivers by points: if/else 32 (37 pts), boolean chains 6, match/switch 2, loops 1 (nesting depth added 5). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
  • nono_cli::capability_ext::add_cli_unix_socket_caps (cognitive 45) crates/nono-cli/src/capability_ext.rs:130 — nono_cli::capability_ext::add_cli_unix_socket_caps has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (37 pts), loops 6, boolean chains 2 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::profile_runtime::prepare_profile_with_options (cognitive 45) crates/nono-cli/src/profile_runtime.rs:672 — nono_cli::profile_runtime::prepare_profile_with_options has cognitive complexity 45 (threshold 15). Drivers by points: if/else 19 (36 pts), loops 3 (7 pts), boolean chains 2 (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.
  • nono_cli::remote_run::run (cognitive 45) crates/nono-cli/src/remote_run.rs:55 — nono_cli::remote_run::run has cognitive complexity 45 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 11, match/switch 5 (8 pts), loops 2 (nesting depth added 8). 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.
  • nono_cli::exec_strategy::run_supervisor_loop (cognitive 44) crates/nono-cli/src/exec_strategy.rs:2784 — nono_cli::exec_strategy::run_supervisor_loop has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (32 pts), match/switch 2 (6 pts), boolean chains 5, loops 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_cli::proxy_runtime::build_proxy_config_from_flags (cognitive 44) crates/nono-cli/src/proxy_runtime.rs:2405 — nono_cli::proxy_runtime::build_proxy_config_from_flags has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (33 pts), loops 5 (8 pts), boolean chains 3 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • + 106 more in this group — see findings.md.
D1 · Cyclomatic Complexity · nono_cli · ×80
  • nono_cli::exec_strategy::execute_supervised (cyclomatic 115) crates/nono-cli/src/exec_strategy.rs:572 — nono_cli::exec_strategy::execute_supervised has cyclomatic complexity 115 (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.
  • nono_cli::profile_cmd::cmd_diff (cyclomatic 62) crates/nono-cli/src/profile_cmd.rs:1489 — nono_cli::profile_cmd::cmd_diff has cyclomatic complexity 62 (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.
  • nono_cli::profile_cmd::cmd_show (cyclomatic 59) crates/nono-cli/src/profile_cmd.rs:883 — nono_cli::profile_cmd::cmd_show has cyclomatic complexity 59 (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.
  • nono_cli::execution_runtime::execute_sandboxed (cyclomatic 56) crates/nono-cli/src/execution_runtime.rs:203 — nono_cli::execution_runtime::execute_sandboxed has cyclomatic complexity 56 (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.
  • nono_cli::command_policy::validate_credential (cyclomatic 50) crates/nono-cli/src/command_policy.rs:2763 — nono_cli::command_policy::validate_credential has cyclomatic complexity 50 (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.
  • nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification (cyclomatic 47) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:248 — nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification 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.
  • nono_cli::exec_strategy::clone_files::child_exec (cyclomatic 43) crates/nono-cli/src/exec_strategy/clone_files.rs:443 — nono_cli::exec_strategy::clone_files::child_exec has cyclomatic complexity 43 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
  • nono_cli::exec_strategy::run_supervisor_loop_inner (cyclomatic 39) crates/nono-cli/src/exec_strategy.rs:3096 — nono_cli::exec_strategy::run_supervisor_loop_inner has cyclomatic complexity 39 (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.
  • nono_cli::tool-sandbox::platform::linux::handle_shim_stream_inner (cyclomatic 39) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1269 — nono_cli::tool-sandbox::platform::linux::handle_shim_stream_inner has cyclomatic complexity 39 (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.
  • nono_cli::profile_cmd::resolve_to_manifest (cyclomatic 38) crates/nono-cli/src/profile_cmd.rs:3027 — nono_cli::profile_cmd::resolve_to_manifest has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
  • nono_cli::remote_run::run (cyclomatic 38) crates/nono-cli/src/remote_run.rs:55 — nono_cli::remote_run::run has cyclomatic complexity 38 (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.
  • nono_cli::sandbox_prepare::prepare_sandbox (cyclomatic 38) crates/nono-cli/src/sandbox_prepare.rs:1482 — nono_cli::sandbox_prepare::prepare_sandbox has cyclomatic complexity 38 (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.
  • nono_cli::tool-sandbox::platform::macos::handle_shim_stream_inner (cyclomatic 38) crates/nono-cli/src/tool-sandbox/platform/macos.rs:992 — nono_cli::tool-sandbox::platform::macos::handle_shim_stream_inner has cyclomatic complexity 38 (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.
  • nono_cli::exec_strategy::supervisor_linux::handle_received_network_notification (cyclomatic 34) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:1273 — nono_cli::exec_strategy::supervisor_linux::handle_received_network_notification 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.
  • nono_cli::policy::apply_macos_keychain_db_exception (cyclomatic 34) crates/nono-cli/src/policy.rs:1486 — nono_cli::policy::apply_macos_keychain_db_exception has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
  • nono_cli::profile::validate_custom_credential (cyclomatic 34) crates/nono-cli/src/profile/mod.rs:647 — nono_cli::profile::validate_custom_credential has cyclomatic complexity 34 (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.
  • nono_cli::profile::validate_credential_capture_entries (cyclomatic 34) crates/nono-cli/src/profile/mod.rs:1527 — nono_cli::profile::validate_credential_capture_entries 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.
  • nono_cli::pty_proxy::run_attach_loop (cyclomatic 34) crates/nono-cli/src/pty_proxy.rs:2869 — nono_cli::pty_proxy::run_attach_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.
  • nono_cli::audit_commands::cmd_show (cyclomatic 33) crates/nono-cli/src/audit_commands.rs:348 — nono_cli::audit_commands::cmd_show has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • nono_cli::exec_strategy::clone_files::spawn (cyclomatic 32) crates/nono-cli/src/exec_strategy/clone_files.rs:218 — nono_cli::exec_strategy::clone_files::spawn has cyclomatic complexity 32 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
  • nono_cli::login_cmd::run_login (cyclomatic 29) crates/nono-cli/src/login_cmd.rs:63 — nono_cli::login_cmd::run_login has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • nono_cli::profile_cmd::cmd_validate (cyclomatic 27) crates/nono-cli/src/profile_cmd.rs:2487 — nono_cli::profile_cmd::cmd_validate has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • nono_cli::trust_scan::run_pre_exec_scan (cyclomatic 27) crates/nono-cli/src/trust_scan.rs:375 — nono_cli::trust_scan::run_pre_exec_scan has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • nono_cli::exec_strategy::run_supervisor_loop (cyclomatic 26) crates/nono-cli/src/exec_strategy.rs:2784 — nono_cli::exec_strategy::run_supervisor_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.
  • nono_cli::output::print_capabilities (cyclomatic 26) crates/nono-cli/src/output.rs:97 — nono_cli::output::print_capabilities 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.
  • + 55 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×59
  • FunctionTooLong: nono_cli::execution_runtime::execute_sandboxed crates/nono-cli/src/execution_runtime.rs:203 — FunctionTooLong — nono_cli::execution_runtime::execute_sandboxed runs 508 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 408 over it, 5.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_cli::sandbox_prepare::prepare_sandbox crates/nono-cli/src/sandbox_prepare.rs:1482 — FunctionTooLong — nono_cli::sandbox_prepare::prepare_sandbox runs 433 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 333 over it, 4.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_cli::profile_cmd::cmd_diff crates/nono-cli/src/profile_cmd.rs:1489 — FunctionTooLong — nono_cli::profile_cmd::cmd_diff runs 422 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 322 over it, 4.22× 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: nono_proxy::reverse::handle_reverse_proxy crates/nono-proxy/src/reverse.rs:129 — FunctionTooLong — nono_proxy::reverse::handle_reverse_proxy runs 400 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 300 over it, 4.00× 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: nono_proxy::server::handle_connection crates/nono-proxy/src/server.rs:1719 — FunctionTooLong — nono_proxy::server::handle_connection runs 348 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 248 over it, 3.48× 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: nono_proxy::tls_intercept::handle::handle_inner_request crates/nono-proxy/src/tls_intercept/handle.rs:1018 — FunctionTooLong — nono_proxy::tls_intercept::handle::handle_inner_request runs 347 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 247 over it, 3.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification crates/nono-cli/src/exec_strategy/supervisor_linux.rs:248 — FunctionTooLong — nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification runs 334 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 234 over it, 3.34× 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: nono_cli::profile_cmd::cmd_show crates/nono-cli/src/profile_cmd.rs:883 — FunctionTooLong — nono_cli::profile_cmd::cmd_show runs 279 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 179 over it, 2.79× 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: nono_cli::profile_cmd::resolve_to_manifest crates/nono-cli/src/profile_cmd.rs:3027 — FunctionTooLong — nono_cli::profile_cmd::resolve_to_manifest runs 279 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 179 over it, 2.79× 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: nono_cli::profile_runtime::prepare_profile_with_options crates/nono-cli/src/profile_runtime.rs:672 — FunctionTooLong — nono_cli::profile_runtime::prepare_profile_with_options runs 261 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 161 over it, 2.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_proxy::tls_intercept::handle::select_intercept_route crates/nono-proxy/src/tls_intercept/handle.rs:493 — FunctionTooLong — nono_proxy::tls_intercept::handle::select_intercept_route runs 260 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 160 over it, 2.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_cli::supervised_runtime::execute_supervised_runtime crates/nono-cli/src/supervised_runtime.rs:222 — FunctionTooLong — nono_cli::supervised_runtime::execute_supervised_runtime runs 244 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 144 over it, 2.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_proxy::server::start_with_network_approval crates/nono-proxy/src/server.rs:1281 — FunctionTooLong — nono_proxy::server::start_with_network_approval runs 243 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 143 over it, 2.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_proxy::tls_intercept::h2_forward::handle_h2_stream crates/nono-proxy/src/tls_intercept/h2_forward.rs:232 — FunctionTooLong — nono_proxy::tls_intercept::h2_forward::handle_h2_stream runs 243 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 143 over it, 2.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_cli::profile::merge_profiles crates/nono-cli/src/profile/mod.rs:4126 — FunctionTooLong — nono_cli::profile::merge_profiles runs 213 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 113 over it, 2.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_proxy::tls_intercept::handle::handle_inner_request_aws crates/nono-proxy/src/tls_intercept/handle.rs:1789 — FunctionTooLong — nono_proxy::tls_intercept::handle::handle_inner_request_aws runs 193 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 93 over it, 1.93× 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: nono_proxy::server::handle_forward_http crates/nono-proxy/src/server.rs:2275 — FunctionTooLong — nono_proxy::server::handle_forward_http runs 185 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 85 over it, 1.85× 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: nono_proxy::reverse::handle_spiffe_route crates/nono-proxy/src/reverse.rs:709 — FunctionTooLong — nono_proxy::reverse::handle_spiffe_route runs 183 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 83 over it, 1.83× 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: nono::audit::verify_audit_attestation_bundle crates/nono/src/audit.rs:1258 — FunctionTooLong — nono::audit::verify_audit_attestation_bundle runs 177 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_cli::why_runtime::run_why crates/nono-cli/src/why_runtime.rs:122 — FunctionTooLong — nono_cli::why_runtime::run_why 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.
  • FunctionTooLong: nono_cli::proxy_runtime::prepare_proxy_launch_options crates/nono-cli/src/proxy_runtime.rs:1446 — FunctionTooLong — nono_cli::proxy_runtime::prepare_proxy_launch_options 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: nono_cli::remote_run::run crates/nono-cli/src/remote_run.rs:55 — FunctionTooLong — nono_cli::remote_run::run runs 171 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 71 over it, 1.71× 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: nono_cli::command_policy::validate_credential crates/nono-cli/src/command_policy.rs:2763 — FunctionTooLong — nono_cli::command_policy::validate_credential runs 168 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: nono_cli::proxy_runtime::start_proxy_runtime crates/nono-cli/src/proxy_runtime.rs:3042 — FunctionTooLong — nono_cli::proxy_runtime::start_proxy_runtime runs 163 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 63 over it, 1.63× 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: nono_cli::policy::apply_macos_keychain_db_exception crates/nono-cli/src/policy.rs:1486 — FunctionTooLong — nono_cli::policy::apply_macos_keychain_db_exception runs 155 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 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 34 more in this group — see findings.md.
D8 · Code Coverage · Low coverage · ×56
  • Low coverage: crates/nono-cli/src/app_runtime.rs crates/nono-cli/src/app_runtime.rs:1 — 0.0% line coverage (0/119).
  • Low coverage: crates/nono-cli/src/audit_client.rs crates/nono-cli/src/audit_client.rs:1 — 43.4% line coverage (154/355).
  • Low coverage: crates/nono-cli/src/audit_commands.rs crates/nono-cli/src/audit_commands.rs:1 — 16.8% line coverage (132/784).
  • Low coverage: crates/nono-cli/src/cli_bootstrap.rs crates/nono-cli/src/cli_bootstrap.rs:1 — 39.3% line coverage (46/117).
  • Low coverage: crates/nono-cli/src/command_runtime.rs crates/nono-cli/src/command_runtime.rs:1 — 19.3% line coverage (63/327).
  • Low coverage: crates/nono-cli/src/config/version.rs crates/nono-cli/src/config/version.rs:1 — 35.0% line coverage (21/60).
  • Low coverage: crates/nono-cli/src/connect_client.rs crates/nono-cli/src/connect_client.rs:1 — 28.4% line coverage (374/1317).
  • Low coverage: crates/nono-cli/src/credential_runtime.rs crates/nono-cli/src/credential_runtime.rs:1 — 24.1% line coverage (21/87).
  • Low coverage: crates/nono-cli/src/device_key.rs crates/nono-cli/src/device_key.rs:1 — 28.9% line coverage (11/38).
  • Low coverage: crates/nono-cli/src/exec_strategy.rs crates/nono-cli/src/exec_strategy.rs:1 — 32.7% line coverage (820/2506).
  • Low coverage: crates/nono-cli/src/exec_strategy/clone_files.rs crates/nono-cli/src/exec_strategy/clone_files.rs:1 — 44.1% line coverage (326/740).
  • Low coverage: crates/nono-cli/src/exec_strategy/supervisor_linux.rs crates/nono-cli/src/exec_strategy/supervisor_linux.rs:1 — 42.7% line coverage (473/1107).
  • Low coverage: crates/nono-cli/src/execution_runtime.rs crates/nono-cli/src/execution_runtime.rs:1 — 12.1% line coverage (78/645).
  • Low coverage: crates/nono-cli/src/launch_runtime.rs crates/nono-cli/src/launch_runtime.rs:1 — 26.7% line coverage (107/401).
  • Low coverage: crates/nono-cli/src/lineage_cgroup.rs crates/nono-cli/src/lineage_cgroup.rs:1 — 17.0% line coverage (30/176).
  • Low coverage: crates/nono-cli/src/login_cmd.rs crates/nono-cli/src/login_cmd.rs:1 — 16.6% line coverage (127/765).
  • Low coverage: crates/nono-cli/src/main.rs crates/nono-cli/src/main.rs:1 — 0.0% line coverage (0/30).
  • Low coverage: crates/nono-cli/src/migration.rs crates/nono-cli/src/migration.rs:1 — 30.9% line coverage (30/97).
  • Low coverage: crates/nono-cli/src/open_url_runtime.rs crates/nono-cli/src/open_url_runtime.rs:1 — 0.0% line coverage (0/31).
  • Low coverage: crates/nono-cli/src/output.rs crates/nono-cli/src/output.rs:1 — 24.0% line coverage (235/981).
  • Low coverage: crates/nono-cli/src/pack_update_hint.rs crates/nono-cli/src/pack_update_hint.rs:1 — 8.2% line coverage (16/194).
  • Low coverage: crates/nono-cli/src/package_cmd.rs crates/nono-cli/src/package_cmd.rs:1 — 3.4% line coverage (32/951).
  • Low coverage: crates/nono-cli/src/profile_cmd.rs crates/nono-cli/src/profile_cmd.rs:1 — 23.9% line coverage (642/2681).
  • Low coverage: crates/nono-cli/src/profile_save_runtime.rs crates/nono-cli/src/profile_save_runtime.rs:1 — 24.7% line coverage (340/1377).
  • Low coverage: crates/nono-cli/src/proxy_command.rs crates/nono-cli/src/proxy_command.rs:1 — 7.0% line coverage (22/315).
  • + 31 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×43
  • FileTooLong: src/exec_strategy.rs crates/nono-cli/src/exec_strategy.rs — FileTooLong — 2820 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 69 free functions. The bar is 500 significant lines; this is 2320 over it, 5.64× 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: profile/mod.rs crates/nono-cli/src/profile/mod.rs — FileTooLong — 2723 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 91 free functions. The bar is 500 significant lines; this is 2223 over it, 5.45× 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/proxy_runtime.rs crates/nono-cli/src/proxy_runtime.rs — FileTooLong — 2611 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 73 free functions. The bar is 500 significant lines; this is 2111 over it, 5.22× 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/command_policy.rs crates/nono-cli/src/command_policy.rs — FileTooLong — 2478 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 56 free functions. The bar is 500 significant lines; this is 1978 over it, 4.96× 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/profile_cmd.rs crates/nono-cli/src/profile_cmd.rs — FileTooLong — 2325 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 52 free functions. The bar is 500 significant lines; this is 1825 over it, 4.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/cli.rs crates/nono-cli/src/cli.rs — FileTooLong — 2037 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 1537 over it, 4.07× 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/reverse.rs crates/nono-proxy/src/reverse.rs — FileTooLong — 1968 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 57 free functions. The bar is 500 significant lines; this is 1468 over it, 3.94× 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: diagnostic/formatter.rs crates/nono-cli/src/diagnostic/formatter.rs — FileTooLong — 1880 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 63% of them inside a single declaration: DiagnosticFormatter (2 blocks, 651-2481), declaring 43 free functions. The bar is 500 significant lines; this is 1380 over it, 3.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/pty_proxy.rs crates/nono-cli/src/pty_proxy.rs — FileTooLong — 1800 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 64 free functions. The bar is 500 significant lines; this is 1300 over it, 3.60× 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: tls_intercept/handle.rs crates/nono-proxy/src/tls_intercept/handle.rs — FileTooLong — 1632 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 1132 over it, 3.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/server.rs crates/nono-proxy/src/server.rs — FileTooLong — 1554 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 35 free functions. The bar is 500 significant lines; this is 1054 over it, 3.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/profile_save_runtime.rs crates/nono-cli/src/profile_save_runtime.rs — FileTooLong — 1340 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 62 free functions. The bar is 500 significant lines; this is 840 over it, 2.68× 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/sandbox_prepare.rs crates/nono-cli/src/sandbox_prepare.rs — FileTooLong — 1321 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 47 free functions. The bar is 500 significant lines; this is 821 over it, 2.64× 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/policy.rs crates/nono-cli/src/policy.rs — FileTooLong — 1309 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 46 free functions. The bar is 500 significant lines; this is 809 over it, 2.62× 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/connect_client.rs crates/nono-cli/src/connect_client.rs — FileTooLong — 1283 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 61 free functions. The bar is 500 significant lines; this is 783 over it, 2.57× 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: exec_strategy/supervisor_linux.rs crates/nono-cli/src/exec_strategy/supervisor_linux.rs — FileTooLong — 1161 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 661 over it, 2.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/audit.rs crates/nono/src/audit.rs — FileTooLong — 1131 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 631 over it, 2.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/keystore.rs crates/nono/src/keystore.rs — FileTooLong — 1100 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 49 free functions. The bar is 500 significant lines; this is 600 over it, 2.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/config.rs crates/nono-proxy/src/config.rs — FileTooLong — 984 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 41 free functions. The bar is 500 significant lines; this is 484 over it, 1.97× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/trust_cmd.rs crates/nono-cli/src/trust_cmd.rs — FileTooLong — 976 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 39 free functions. The bar is 500 significant lines; this is 476 over it, 1.95× 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/capability.rs crates/nono/src/capability.rs — FileTooLong — 972 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 472 over it, 1.94× 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/wiring.rs crates/nono-cli/src/wiring.rs — FileTooLong — 931 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 41 free functions. The bar is 500 significant lines; this is 431 over it, 1.86× 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/output.rs crates/nono-cli/src/output.rs — FileTooLong — 896 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 43 free functions. The bar is 500 significant lines; this is 396 over it, 1.79× 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/package_cmd.rs crates/nono-cli/src/package_cmd.rs — FileTooLong — 856 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 36 free functions. The bar is 500 significant lines; this is 356 over it, 1.71× 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/profile_runtime.rs crates/nono-cli/src/profile_runtime.rs — FileTooLong — 844 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 344 over it, 1.69× 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.
  • + 18 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×35
  • Hotspot: crates/nono-cli/src/exec_strategy.rs crates/nono-cli/src/exec_strategy.rs:572 — crates/nono-cli/src/exec_strategy.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 115 in nono_cli::exec_strategy::execute_supervised at line 572. 12 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/exec_strategy.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: crates/nono-proxy/src/server.rs crates/nono-proxy/src/server.rs:1719 — crates/nono-proxy/src/server.rs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in nono_proxy::server::handle_connection at line 1719. 13 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/server.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: crates/nono-proxy/src/tls_intercept/handle.rs crates/nono-proxy/src/tls_intercept/handle.rs:1018 — crates/nono-proxy/src/tls_intercept/handle.rs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in nono_proxy::tls_intercept::handle::handle_inner_request at line 1018. 13 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/tls_intercept/handle.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: crates/nono-cli/src/profile/mod.rs crates/nono-cli/src/profile/mod.rs:647 — crates/nono-cli/src/profile/mod.rs changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in nono_cli::profile::validate_custom_credential at line 647. 8 of those changes were fix/bug commits, and the other 22 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/profile/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: crates/nono-cli/src/execution_runtime.rs crates/nono-cli/src/execution_runtime.rs:203 — crates/nono-cli/src/execution_runtime.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in nono_cli::execution_runtime::execute_sandboxed at line 203. 6 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/execution_runtime.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: crates/nono-cli/src/tool-sandbox/platform/linux.rs crates/nono-cli/src/tool-sandbox/platform/linux.rs:1269 — crates/nono-cli/src/tool-sandbox/platform/linux.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in nono_cli::tool-sandbox::platform::linux::handle_shim_stream_inner at line 1269. 9 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/tool-sandbox/platform/linux.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: crates/nono-cli/src/command_policy.rs crates/nono-cli/src/command_policy.rs:2763 — crates/nono-cli/src/command_policy.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in nono_cli::command_policy::validate_credential at line 2763. 2 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/command_policy.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: crates/nono-cli/src/tool-sandbox/platform/macos.rs crates/nono-cli/src/tool-sandbox/platform/macos.rs:992 — crates/nono-cli/src/tool-sandbox/platform/macos.rs changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in nono_cli::tool-sandbox::platform::macos::handle_shim_stream_inner at line 992. 9 of those changes were fix/bug commits, and the other 11 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/tool-sandbox/platform/macos.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: crates/nono-cli/src/proxy_runtime.rs crates/nono-cli/src/proxy_runtime.rs:1446 — crates/nono-cli/src/proxy_runtime.rs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in nono_cli::proxy_runtime::prepare_proxy_launch_options at line 1446. 10 of those changes were fix/bug commits, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/proxy_runtime.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: crates/nono-cli/src/sandbox_prepare.rs crates/nono-cli/src/sandbox_prepare.rs:1482 — crates/nono-cli/src/sandbox_prepare.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in nono_cli::sandbox_prepare::prepare_sandbox at line 1482. 8 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/sandbox_prepare.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: crates/nono-cli/src/profile_cmd.rs crates/nono-cli/src/profile_cmd.rs:883 — crates/nono-cli/src/profile_cmd.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in nono_cli::profile_cmd::cmd_show at line 883. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/profile_cmd.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: crates/nono-cli/src/policy.rs crates/nono-cli/src/policy.rs:1486 — crates/nono-cli/src/policy.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in nono_cli::policy::apply_macos_keychain_db_exception at line 1486. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/policy.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: crates/nono-cli/src/exec_strategy/supervisor_linux.rs crates/nono-cli/src/exec_strategy/supervisor_linux.rs:248 — crates/nono-cli/src/exec_strategy/supervisor_linux.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification at line 248. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/exec_strategy/supervisor_linux.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: crates/nono-proxy/src/reverse.rs crates/nono-proxy/src/reverse.rs:129 — crates/nono-proxy/src/reverse.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in nono_proxy::reverse::handle_reverse_proxy at line 129. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/reverse.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: crates/nono-proxy/src/tls_intercept/h2_forward.rs crates/nono-proxy/src/tls_intercept/h2_forward.rs:232 — crates/nono-proxy/src/tls_intercept/h2_forward.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in nono_proxy::tls_intercept::h2_forward::handle_h2_stream at line 232. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/tls_intercept/h2_forward.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: crates/nono/src/sandbox/linux.rs crates/nono/src/sandbox/linux.rs:1183 — crates/nono/src/sandbox/linux.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in nono::sandbox::linux::apply_with_abi_inner at line 1183. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono/src/sandbox/linux.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: crates/nono-proxy/src/route.rs crates/nono-proxy/src/route.rs:252 — crates/nono-proxy/src/route.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in RouteStore::load_with_registry at line 252. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/route.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: crates/nono-cli/src/profile_runtime.rs crates/nono-cli/src/profile_runtime.rs:672 — crates/nono-cli/src/profile_runtime.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in nono_cli::profile_runtime::prepare_profile_with_options at line 672. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/profile_runtime.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: crates/nono-cli/src/diagnostic/formatter.rs crates/nono-cli/src/diagnostic/formatter.rs:1313 — crates/nono-cli/src/diagnostic/formatter.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in DiagnosticFormatter::format_supervised_footer_with_diagnostics at line 1313. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/diagnostic/formatter.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: crates/nono/src/sandbox/macos.rs crates/nono/src/sandbox/macos.rs:503 — crates/nono/src/sandbox/macos.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in nono::sandbox::macos::generate_profile at line 503. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono/src/sandbox/macos.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: crates/nono-cli/src/capability_ext.rs crates/nono-cli/src/capability_ext.rs:693 — crates/nono-cli/src/capability_ext.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in CapabilitySet::from_profile at line 693. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/capability_ext.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: crates/nono-proxy/src/credential.rs crates/nono-proxy/src/credential.rs:286 — crates/nono-proxy/src/credential.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in CredentialStore::load_with_registry at line 286. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/credential.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: crates/nono-cli/src/launch_runtime.rs crates/nono-cli/src/launch_runtime.rs:366 — crates/nono-cli/src/launch_runtime.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in nono_cli::launch_runtime::prepare_run_launch_plan at line 366. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/launch_runtime.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: crates/nono-cli/src/pty_proxy.rs crates/nono-cli/src/pty_proxy.rs:1612 — crates/nono-cli/src/pty_proxy.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in nono_cli::pty_proxy::match_enhanced_key_sequence at line 1612. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/pty_proxy.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: crates/nono-cli/src/terminal_approval.rs crates/nono-cli/src/terminal_approval.rs:92 — crates/nono-cli/src/terminal_approval.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in TerminalApproval::prompt at line 92. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/terminal_approval.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.
  • + 10 more in this group — see findings.md.
D31 · IaC & Container Security · Medium IaC · ×34
  • 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
  • + 9 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×25
  • Duplicated block (10 lines × 2) crates/nono-cli/src/capability_ext.rs:922 — crates/nono-cli/src/capability_ext.rs:922-931 | crates/nono-cli/src/capability_ext.rs:976-985 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/capability_ext.rs:922` 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) crates/nono-cli/src/capability_ext.rs:949 — crates/nono-cli/src/capability_ext.rs:949-958 | crates/nono-cli/src/capability_ext.rs:1003-1012 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/capability_ext.rs:949` 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) crates/nono-cli/src/exec_strategy.rs:2944 — crates/nono-cli/src/exec_strategy.rs:2944-2953 | crates/nono-cli/src/exec_strategy.rs:3419-3428 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:2944` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/profile/mod.rs:103 — crates/nono-cli/src/profile/mod.rs:103-112 | crates/nono-cli/src/profile/mod.rs:2161-2170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/profile/mod.rs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:422 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:422-431 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:394-403 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:422` 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:956 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:956-965 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:785-794 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2495 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2495-2504 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5020-5029 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2915 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2915-2924 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5450-5459 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3570 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3570-3579 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3067-3076 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4665 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4665-4674 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4201-4210 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:557 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:557-567 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:604-613 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/macos.rs:557` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/trust_cmd.rs:1006 — crates/nono-cli/src/trust_cmd.rs:1006-1015 | crates/nono-cli/src/trust_intercept.rs:327-336 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_cmd.rs:1006` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/trust_scan.rs:466 — crates/nono-cli/src/trust_scan.rs:466-475 | crates/nono-cli/src/trust_scan.rs:497-506 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_scan.rs:466` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) crates/nono-proxy/src/reverse.rs:803 — crates/nono-proxy/src/reverse.rs:803-812 | crates/nono-proxy/src/tls_intercept/handle.rs:1593-1602 — before extracting anything, compare `crates/nono-proxy/src/reverse.rs` and `crates/nono-proxy/src/tls_intercept/handle.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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.
  • Duplicated block (10 lines × 2) crates/nono-proxy/src/reverse.rs:858 — crates/nono-proxy/src/reverse.rs:858-867 | crates/nono-proxy/src/reverse.rs:1486-1495 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/nono-proxy/src/reverse.rs:857` calls `as_deref`, `unwrap_or` and `crates/nono-proxy/src/reverse.rs:1482` 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 (10 lines × 2) crates/nono-proxy/src/tls_intercept/h2_forward.rs:643 — crates/nono-proxy/src/tls_intercept/h2_forward.rs:643-652 | crates/nono-proxy/src/tls_intercept/h2_forward.rs:680-689 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/h2_forward.rs:643` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1269 — crates/nono-proxy/src/tls_intercept/handle.rs:1269-1278 | crates/nono-proxy/src/tls_intercept/handle.rs:2084-2093 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:1269` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) crates/nono/src/capability.rs:713 — crates/nono/src/capability.rs:713-722 | crates/nono/src/capability.rs:766-775 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/capability.rs:713` 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4134 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4134-4143 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3813-3822 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5509 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5509-5518 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4758-4767 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) crates/nono/src/keystore.rs:492 — crates/nono/src/keystore.rs:492-502 | crates/nono/src/keystore.rs:625-634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:492` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) crates/nono-proxy/src/route.rs:981 — crates/nono-proxy/src/route.rs:981-990 | crates/nono-proxy/src/route.rs:1044-1053 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/route.rs:981` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) crates/nono-cli/src/query_ext.rs:831 — crates/nono-cli/src/query_ext.rs:831-840 | crates/nono-cli/src/query_ext.rs:845-854 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/query_ext.rs:831` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) crates/nono/src/undo/snapshot.rs:654 — crates/nono/src/undo/snapshot.rs:654-663 | crates/nono/src/undo/snapshot.rs:699-708 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:654` 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) tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:14 — tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:14-23 | tool-sandbox-examples/kubernetes/make-proxy-kubeconfig.py:14-23 — `tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py` and `tool-sandbox-examples/kubernetes/make-proxy-kubeconfig.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 98 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D2 · Cognitive Complexity · nono_proxy · ×24
  • nono_proxy::server::handle_connection (cognitive 140) crates/nono-proxy/src/server.rs:1719 — nono_proxy::server::handle_connection has cognitive complexity 140 (threshold 15). Drivers by points: if/else 39 (102 pts), match/switch 3 (16 pts), loops 3 (13 pts), boolean chains 9 (nesting depth added 86). 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.
  • nono_proxy::tls_intercept::handle::handle_inner_request (cognitive 62) crates/nono-proxy/src/tls_intercept/handle.rs:1018 — nono_proxy::tls_intercept::handle::handle_inner_request has cognitive complexity 62 (threshold 15). Drivers by points: if/else 30 (38 pts), match/switch 10 (17 pts), boolean chains 6, loops 1 (nesting depth added 15). 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.
  • nono_proxy::tls_intercept::handle::select_intercept_route (cognitive 56) crates/nono-proxy/src/tls_intercept/handle.rs:493 — nono_proxy::tls_intercept::handle::select_intercept_route has cognitive complexity 56 (threshold 15). Drivers by points: if/else 22 (39 pts), match/switch 5 (12 pts), boolean chains 4, loops 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::reverse::handle_reverse_proxy (cognitive 53) crates/nono-proxy/src/reverse.rs:129 — nono_proxy::reverse::handle_reverse_proxy has cognitive complexity 53 (threshold 15). Drivers by points: if/else 28 (38 pts), match/switch 6 (9 pts), boolean chains 5, 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.
  • nono_proxy::server::start_with_network_approval (cognitive 43) crates/nono-proxy/src/server.rs:1281 — nono_proxy::server::start_with_network_approval has cognitive complexity 43 (threshold 15). Drivers by points: if/else 28 (35 pts), match/switch 3 (4 pts), boolean chains 3, loops 1 (nesting depth added 8). 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.
  • nono_proxy::tls_intercept::h2_forward::handle_h2_stream (cognitive 43) crates/nono-proxy/src/tls_intercept/h2_forward.rs:232 — nono_proxy::tls_intercept::h2_forward::handle_h2_stream has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (26 pts), match/switch 6 (9 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::endpoint_approval::authorize_group (cognitive 38) crates/nono-proxy/src/endpoint_approval.rs:237 — nono_proxy::endpoint_approval::authorize_group has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 5 (15 pts), loops 3 (5 pts), boolean chains 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.
  • nono_proxy::aws::operation::resolve (cognitive 37) crates/nono-proxy/src/aws/operation.rs:141 — nono_proxy::aws::operation::resolve has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 13, match/switch 1 (3 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.
  • nono_proxy::config::validate_no_proxy_host_pattern (cognitive 27) crates/nono-proxy/src/config.rs:622 — nono_proxy::config::validate_no_proxy_host_pattern has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::reverse::classify_upgrade_attempt (cognitive 25) crates/nono-proxy/src/reverse.rs:2166 — nono_proxy::reverse::classify_upgrade_attempt has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 4, match/switch 2 (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.
  • nono_proxy::server::normalize_authority (cognitive 24) crates/nono-proxy/src/server.rs:1680 — nono_proxy::server::normalize_authority has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::tls_intercept::h2_forward::forward_h2_connection (cognitive 23) crates/nono-proxy/src/tls_intercept/h2_forward.rs:56 — nono_proxy::tls_intercept::h2_forward::forward_h2_connection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 3 (8 pts), loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::reverse::read_chunked_request_body (cognitive 22) crates/nono-proxy/src/reverse.rs:1708 — nono_proxy::reverse::read_chunked_request_body has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::server::accept_loop (cognitive 22) crates/nono-proxy/src/server.rs:1630 — nono_proxy::server::accept_loop has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (16 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::config::validate_no_proxy_entry (cognitive 19) crates/nono-proxy/src/config.rs:410 — nono_proxy::config::validate_no_proxy_entry has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4 (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.
  • nono_proxy::tls_intercept::http1::relay_chunked (cognitive 19) crates/nono-proxy/src/tls_intercept/http1.rs:184 — nono_proxy::tls_intercept::http1::relay_chunked has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::forward::rewrite_http1_response (cognitive 18) crates/nono-proxy/src/forward.rs:382 — nono_proxy::forward::rewrite_http1_response has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::reverse::strip_proxy_path_token (cognitive 18) crates/nono-proxy/src/reverse.rs:2734 — nono_proxy::reverse::strip_proxy_path_token has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 2 (5 pts), boolean chains 2 (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.
  • nono_proxy::server::handle_forward_http (cognitive 18) crates/nono-proxy/src/server.rs:2275 — nono_proxy::server::handle_forward_http has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), match/switch 6, boolean chains 3 (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.
  • nono_proxy::aws::endpoints::validate_aws_upstream (cognitive 17) crates/nono-proxy/src/aws/endpoints.rs:236 — nono_proxy::aws::endpoints::validate_aws_upstream has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 3, 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.
  • nono_proxy::server::validate_phantom_formats (cognitive 17) crates/nono-proxy/src/server.rs:1156 — nono_proxy::server::validate_phantom_formats has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::aws::endpoints::resolve_signing_params (cognitive 16) crates/nono-proxy/src/aws/endpoints.rs:392 — nono_proxy::aws::endpoints::resolve_signing_params has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 6 (10 pts), if/else 4 (5 pts), boolean chains 1 (nesting depth added 5). 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.
  • nono_proxy::forward::is_complete_http1_response (cognitive 16) crates/nono-proxy/src/forward.rs:472 — nono_proxy::forward::is_complete_http1_response has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono_proxy::reverse::host_endpoint_policies (cognitive 16) crates/nono-proxy/src/reverse.rs:1094 — nono_proxy::reverse::host_endpoint_policies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×23
  • Duplicated block (9 lines × 2) crates/nono-cli/src/capability_ext.rs:720 — crates/nono-cli/src/capability_ext.rs:720-728 | crates/nono-cli/src/capability_ext.rs:1112-1120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/capability_ext.rs:720` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/profile_save_runtime.rs:366 — crates/nono-cli/src/profile_save_runtime.rs:366-374 | crates/nono-cli/src/profile_save_runtime.rs:426-434 — 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) crates/nono-cli/src/proxy_runtime.rs:683 — crates/nono-cli/src/proxy_runtime.rs:683-691 | crates/nono-cli/src/proxy_runtime.rs:765-773 — 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) crates/nono-cli/src/pty_proxy.rs:2519 — crates/nono-cli/src/pty_proxy.rs:2519-2527 | crates/nono-cli/src/pty_proxy.rs:2561-2569 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/pty_proxy.rs:2519` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/pty_proxy.rs:2927 — crates/nono-cli/src/pty_proxy.rs:2927-2935 | crates/nono-cli/src/pty_proxy.rs:2999-3007 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/pty_proxy.rs:2927` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/session.rs:607 — crates/nono-cli/src/session.rs:607-615 | crates/nono/src/audit.rs:1020-1028 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/session.rs:607` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:232 — crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:232-240 | crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:328-336 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:232` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3016 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3016-3024 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3031-3039 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3016` 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 (9 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4146 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4146-4154 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3825-3833 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) crates/nono/src/undo/snapshot.rs:472 — crates/nono/src/undo/snapshot.rs:472-480 | crates/nono/src/undo/snapshot.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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:472` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/audit_commands.rs:994 — crates/nono-cli/src/audit_commands.rs:994-1002 | crates/nono-cli/src/rollback_commands.rs:191-199 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/audit_commands.rs:962 — crates/nono-cli/src/audit_commands.rs:962-970 | crates/nono-cli/src/session_commands.rs:27-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:523 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:523-531 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:480-488 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2470 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2470-2478 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4995-5003 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4743 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4743-4751 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4283-4291 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4900 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4900-4908 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4438-4446 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5520 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5520-5528 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4769-4777 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) crates/nono/src/diagnostic/observation.rs:157 — crates/nono/src/diagnostic/observation.rs:157-165 | crates/nono/src/diagnostic/report.rs:252-260 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `path` to `&std::path::Path` in one and `&Path` 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 (9 lines × 2) crates/nono-cli/src/output.rs:755 — crates/nono-cli/src/output.rs:755-766 | crates/nono-cli/src/output.rs:788-796 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/output.rs:755` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/nono/src/keystore.rs:1923 — crates/nono/src/keystore.rs:1923-1931 | crates/nono/src/keystore.rs:1953-1962 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:1923` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) crates/nono-cli/src/execution_runtime.rs:452 — crates/nono-cli/src/execution_runtime.rs:452-460 | crates/nono-cli/src/execution_runtime.rs:485-493 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/execution_runtime.rs:452` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/nono/src/keystore.rs:1122 — crates/nono/src/keystore.rs:1122-1130 | crates/nono/src/keystore.rs:1590-1598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:1122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/nono/src/undo/snapshot.rs:643 — crates/nono/src/undo/snapshot.rs:643-651 | crates/nono/src/undo/snapshot.rs:688-696 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:643` 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 (13 lines × 2) · ×21
  • Duplicated block (13 lines × 2) bindings/c/src/capability_set.rs:314 — bindings/c/src/capability_set.rs:314-326 | bindings/c/src/capability_set.rs:343-355 — 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) crates/nono-cli/src/audit_session.rs:233 — crates/nono-cli/src/audit_session.rs:233-245 | crates/nono-cli/src/rollback_session.rs:147-159 — before extracting anything, compare `crates/nono-cli/src/audit_session.rs` and `crates/nono-cli/src/rollback_session.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/command_policy.rs:2793 — crates/nono-cli/src/command_policy.rs:2793-2805 | crates/nono-cli/src/command_policy.rs:2833-2845 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/command_policy.rs:2793` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/command_runtime.rs:212 — crates/nono-cli/src/command_runtime.rs:212-224 | crates/nono-cli/src/command_runtime.rs:377-389 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/command_runtime.rs:212` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/exec_strategy.rs:1186 — crates/nono-cli/src/exec_strategy.rs:1186-1198 | crates/nono-cli/src/exec_strategy.rs:1204-1216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:1186` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/exec_strategy.rs:3168 — crates/nono-cli/src/exec_strategy.rs:3168-3180 | crates/nono-cli/src/exec_strategy.rs:3195-3207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:3168` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/network_policy.rs:369 — crates/nono-cli/src/network_policy.rs:369-381 | crates/nono-cli/src/network_policy.rs:392-404 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/network_policy.rs:369` 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:397 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:397-409 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:366-378 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:397` 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:461 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:461-473 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:434-446 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3822 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3822-3834 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3355-3367 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3822` 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, `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3835` calls `add_runtime_baseline` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs:3368` 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5833 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5833-5845 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:5866-5878 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:5833` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/trust_cmd.rs:945 — crates/nono-cli/src/trust_cmd.rs:945-957 | crates/nono-cli/src/trust_intercept.rs:365-377 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_cmd.rs:945` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/wiring.rs:935 — crates/nono-cli/src/wiring.rs:935-947 | crates/nono-cli/src/wiring.rs:1442-1454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/wiring.rs:935` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) crates/nono-proxy/src/server.rs:2201 — crates/nono-proxy/src/server.rs:2201-2213 | crates/nono-proxy/src/server.rs:2339-2351 — 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) crates/nono/src/undo/object_store.rs:185 — crates/nono/src/undo/object_store.rs:185-197 | crates/nono/src/undo/object_store.rs:247-259 — 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) crates/nono-cli/src/exec_strategy.rs:2929 — crates/nono-cli/src/exec_strategy.rs:2929-2941 | crates/nono-cli/src/exec_strategy.rs:3404-3416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:2929` 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 before the matched lines, `crates/nono-cli/src/exec_strategy.rs:3400` calls `Some`, `reap_reparented_orphans`, `Ok` and `crates/nono-cli/src/exec_strategy.rs:2927` 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 (13 lines × 2) crates/nono-cli/src/proxy_runtime.rs:719 — crates/nono-cli/src/proxy_runtime.rs:719-731 | crates/nono-cli/src/proxy_runtime.rs:737-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.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/proxy_runtime.rs:227 — crates/nono-cli/src/proxy_runtime.rs:227-239 | crates/nono-cli/src/proxy_runtime.rs:252-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/proxy_runtime.rs:227` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) crates/nono-proxy/src/reverse.rs:1255 — crates/nono-proxy/src/reverse.rs:1255-1267 | crates/nono-proxy/src/reverse.rs:1284-1296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:1255` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3361 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3361-3373 | crates/nono/src/sandbox/linux.rs:1568-1580 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3361` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) crates/nono-proxy/src/tls_intercept/h2_forward.rs:626 — crates/nono-proxy/src/tls_intercept/h2_forward.rs:626-638 | crates/nono-proxy/src/tls_intercept/h2_forward.rs:663-675 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/h2_forward.rs:626` 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 × 2) · ×20
  • Duplicated block (8 lines × 2) crates/nono-cli/src/audit_client.rs:396 — crates/nono-cli/src/audit_client.rs:396-403 | crates/nono-cli/src/platform_client.rs:394-401 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_client.rs:396` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/capability_ext.rs:53 — crates/nono-cli/src/capability_ext.rs:53-60 | crates/nono-cli/src/capability_ext.rs:88-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/capability_ext.rs:53` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/command_policy.rs:3798 — crates/nono-cli/src/command_policy.rs:3798-3805 | crates/nono-cli/src/profile/mod.rs:4430-4437 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/command_policy.rs:3798` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/exec_strategy.rs:4375 — crates/nono-cli/src/exec_strategy.rs:4375-4382 | crates/nono/src/capability.rs:2161-2168 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:220 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:220-227 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:238-245 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:232 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:232-239 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:255-262 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/nono-cli/src/tool-sandbox/platform/linux.rs:240` calls `resolve_policy_exec_helpers`, `validate_controlled_exec_helper_immutability` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs:263` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2130 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2130-2137 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1934-1941 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3652 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3652-3659 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3670-3677 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) crates/nono-proxy/src/forward.rs:167 — crates/nono-proxy/src/forward.rs:167-174 | crates/nono-proxy/src/tls_intercept/h2_forward.rs:214-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) crates/nono-proxy/src/oauth2.rs:322 — crates/nono-proxy/src/oauth2.rs:322-329 | crates/nono-proxy/src/oauth2.rs:672-679 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/oauth2.rs:322` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) crates/nono-proxy/src/reverse.rs:425 — crates/nono-proxy/src/reverse.rs:425-432 | crates/nono-proxy/src/tls_intercept/handle.rs:824-831 — before extracting anything, compare `crates/nono-proxy/src/reverse.rs` and `crates/nono-proxy/src/tls_intercept/handle.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:425` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) crates/nono-proxy/src/reverse.rs:2475 — crates/nono-proxy/src/reverse.rs:2475-2482 | crates/nono-proxy/src/reverse.rs:2586-2593 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/exec_strategy.rs:561 — crates/nono-cli/src/exec_strategy.rs:561-568 | crates/nono-cli/src/exec_strategy.rs:711-718 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:561` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/connect_client.rs:626 — crates/nono-cli/src/connect_client.rs:626-633 | crates/nono-cli/src/platform_oauth/client.rs:866-873 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2461 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2461-2468 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4986-4993 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2556 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2556-2563 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5081-5088 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2578 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2578-2585 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5092-5099 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/connect_client.rs:1805 — crates/nono-cli/src/connect_client.rs:1805-1812 | crates/nono-cli/src/pty_proxy.rs:1592-1599 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3498 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3498-3505 | crates/nono/src/supervisor/socket.rs:340-347 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3498` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:538 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:538-545 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:591-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/macos.rs:538` 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 (11 lines × 2) · ×17
  • Duplicated block (11 lines × 2) crates/nono-cli/src/audit_commands.rs:313 — crates/nono-cli/src/audit_commands.rs:313-323 | crates/nono-cli/src/rollback_commands.rs:266-276 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_commands.rs:313` 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 `sessions` to `&[SessionInfo]` in one and `&[&SessionInfo]` 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 (11 lines × 2) crates/nono-cli/src/audit_commands.rs:895 — crates/nono-cli/src/audit_commands.rs:895-905 | crates/nono-cli/src/rollback_commands.rs:569-579 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_commands.rs:895` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) crates/nono-cli/src/audit_commands.rs:918 — crates/nono-cli/src/audit_commands.rs:918-928 | crates/nono-cli/src/rollback_commands.rs:591-601 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_commands.rs:918` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) crates/nono-cli/src/proxy_command.rs:394 — crates/nono-cli/src/proxy_command.rs:394-404 | crates/nono-cli/src/proxy_runtime.rs:1597-1607 — before extracting anything, compare `crates/nono-cli/src/proxy_command.rs` and `crates/nono-cli/src/proxy_runtime.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 `crates/nono-cli/src/proxy_command.rs:394` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2507 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2507-2517 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5032-5042 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3453 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3453-3463 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3486-3496 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) crates/nono-cli/src/trust_keystore.rs:235 — crates/nono-cli/src/trust_keystore.rs:235-245 | crates/nono-cli/src/trust_keystore.rs:339-349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_keystore.rs:235` 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) crates/nono/src/audit.rs:1051 — crates/nono/src/audit.rs:1051-1061 | crates/nono/src/audit.rs:1129-1139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/audit.rs:1051` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) crates/nono/src/capability.rs:158 — crates/nono/src/capability.rs:158-168 | crates/nono/src/capability.rs:196-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/capability.rs:158` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) crates/nono-cli/src/exec_strategy.rs:2386 — crates/nono-cli/src/exec_strategy.rs:2386-2396 | crates/nono-cli/src/pty_proxy.rs:2600-2610 — 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 (11 lines × 2) crates/nono/src/keystore.rs:333 — crates/nono/src/keystore.rs:333-345 | crates/nono/src/keystore.rs:486-496 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:333` 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2977 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2977-2987 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5540-5550 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2977` 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) crates/nono-cli/src/output.rs:918 — crates/nono-cli/src/output.rs:918-928 | crates/nono-cli/src/output.rs:984-994 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/output.rs:918` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) crates/nono-cli/src/audit_ledger.rs:38 — crates/nono-cli/src/audit_ledger.rs:38-48 | crates/nono-cli/src/audit_ledger.rs:99-109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_ledger.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 (11 lines × 2) crates/nono-proxy/src/reverse.rs:2352 — crates/nono-proxy/src/reverse.rs:2352-2362 | crates/nono-proxy/src/reverse.rs:2370-2380 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:2352` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) crates/nono-cli/src/exec_strategy.rs:3843 — crates/nono-cli/src/exec_strategy.rs:3843-3853 | crates/nono-cli/src/exec_strategy.rs:3912-3922 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:3843` 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) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:520 — crates/nono-cli/src/exec_strategy/supervisor_linux.rs:520-530 | crates/nono-cli/src/exec_strategy/supervisor_linux.rs:546-556 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy/supervisor_linux.rs:520` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×15
  • Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:907 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:907-913 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:762-768 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1499 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1499-1505 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1628-1634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1499` 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) crates/nono-proxy/src/oauth2.rs:348 — crates/nono-proxy/src/oauth2.rs:348-354 | crates/nono-proxy/src/oauth2.rs:696-702 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/oauth2.rs:348` 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) crates/nono-proxy/src/reverse.rs:1958 — crates/nono-proxy/src/reverse.rs:1958-1964 | crates/nono-proxy/src/reverse.rs:2005-2011 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:1958` 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) crates/nono/src/keystore.rs:1260 — crates/nono/src/keystore.rs:1260-1266 | crates/nono/src/keystore.rs:1346-1352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:1260` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2946 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2946-2952 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5521-5527 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2946` 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) crates/nono-cli/src/audit_commands.rs:237 — crates/nono-cli/src/audit_commands.rs:237-243 | crates/nono-cli/src/rollback_commands.rs:990-996 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) crates/nono-cli/src/audit_commands.rs:283 — crates/nono-cli/src/audit_commands.rs:283-289 | crates/nono-cli/src/rollback_commands.rs:1041-1047 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_commands.rs:283` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2733 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2733-2739 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5296-5302 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2733` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3742 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3742-3748 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3146-3152 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5066 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5066-5072 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:2753-2759 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2294 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2294-2304 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4810-4816 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2294` 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. 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 (7 lines × 2) crates/nono-cli/src/remote_run.rs:202 — crates/nono-cli/src/remote_run.rs:202-209 | crates/nono-cli/src/remote_run.rs:365-371 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/remote_run.rs:202` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) crates/nono/src/undo/snapshot.rs:354 — crates/nono/src/undo/snapshot.rs:354-360 | crates/nono/src/undo/snapshot.rs:379-385 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:354` 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) crates/nono-cli/src/profile/mod.rs:3625 — crates/nono-cli/src/profile/mod.rs:3625-3631 | crates/nono-cli/src/profile/mod.rs:3638-3644 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/profile/mod.rs:3625` 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.
D2 · Cognitive Complexity · nono · ×14
  • nono::capability::tokenize_sexp (cognitive 63) crates/nono/src/capability.rs:682 — nono::capability::tokenize_sexp has cognitive complexity 63 (threshold 15). Drivers by points: if/else 12 (40 pts), loops 6 (18 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono::keystore::build_mappings_from_list (cognitive 47) crates/nono/src/keystore.rs:1912 — nono::keystore::build_mappings_from_list has cognitive complexity 47 (threshold 15). Drivers by points: if/else 20 (42 pts), match/switch 1 (4 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.
  • nono::trust::policy::merge_policies (cognitive 29) crates/nono/src/trust/policy.rs:62 — nono::trust::policy::merge_policies has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 7 (12 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono::audit::verify_audit_log (cognitive 26) crates/nono/src/audit.rs:1610 — nono::audit::verify_audit_log has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3, 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.
  • nono::audit::verify_audit_attestation_bundle (cognitive 24) crates/nono/src/audit.rs:1258 — nono::audit::verify_audit_attestation_bundle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16, match/switch 6, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • nono::audit::verify_inclusion_proof (cognitive 22) crates/nono/src/audit.rs:910 — nono::audit::verify_inclusion_proof has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono::path::resolve_hops (cognitive 22) crates/nono/src/path.rs:69 — nono::path::resolve_hops has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (19 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono::trust::policy::find_files_recursive (cognitive 21) crates/nono/src/trust/policy.rs:321 — nono::trust::policy::find_files_recursive has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono::broker_path::walk_chain_with_budget (cognitive 20) crates/nono/src/broker_path.rs:172 — nono::broker_path::walk_chain_with_budget has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (4 pts), match/switch 2 (4 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.
  • nono::capability::validate_platform_rule (cognitive 18) crates/nono/src/capability.rs:616 — nono::capability::validate_platform_rule has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2, match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono::net_filter::host_pattern_matches (cognitive 18) crates/nono/src/net_filter.rs:67 — nono::net_filter::host_pattern_matches has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 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.
  • nono::trust::types::wildcard_match (cognitive 18) crates/nono/src/trust/types.rs:264 — nono::trust::types::wildcard_match has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 1 (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.
  • nono::audit::build_inclusion_proof (cognitive 17) crates/nono/src/audit.rs:849 — nono::audit::build_inclusion_proof has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • nono::scrub::scrub_argv_with_policy (cognitive 17) crates/nono/src/scrub.rs:313 — nono::scrub::scrub_argv_with_policy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×14
  • Duplicated block (14 lines × 2) crates/nono-cli/src/audit_session.rs:217 — crates/nono-cli/src/audit_session.rs:217-230 | crates/nono-cli/src/rollback_session.rs:196-209 — before extracting anything, compare `crates/nono-cli/src/audit_session.rs` and `crates/nono-cli/src/rollback_session.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) crates/nono-cli/src/audit_session.rs:248 — crates/nono-cli/src/audit_session.rs:248-261 | crates/nono-cli/src/rollback_session.rs:166-179 — before extracting anything, compare `crates/nono-cli/src/audit_session.rs` and `crates/nono-cli/src/rollback_session.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) crates/nono-cli/src/exec_strategy.rs:4211 — crates/nono-cli/src/exec_strategy.rs:4211-4224 | crates/nono-cli/src/exec_strategy.rs:4276-4289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:4211` 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) crates/nono-cli/src/output.rs:133 — crates/nono-cli/src/output.rs:133-146 | crates/nono-cli/src/output.rs:186-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/output.rs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:790 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:790-803 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:676-689 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:790` 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 before the matched lines, `crates/nono-cli/src/tool-sandbox/platform/linux.rs:789` calls `now` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs:674` 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 (14 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1100 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1100-1113 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4587-4600 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1100` 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. 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 (14 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5816 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5816-5829 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:5849-5862 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:5816` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) crates/nono-cli/src/trust_cmd.rs:347 — crates/nono-cli/src/trust_cmd.rs:347-360 | crates/nono-cli/src/trust_cmd.rs:505-518 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_cmd.rs:347` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) crates/nono-proxy/src/reverse.rs:1435 — crates/nono-proxy/src/reverse.rs:1435-1448 | crates/nono-proxy/src/reverse.rs:1525-1538 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:1435` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1397 — crates/nono-proxy/src/tls_intercept/handle.rs:1397-1410 | crates/nono-proxy/src/tls_intercept/handle.rs:1993-2006 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:1397` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) crates/nono/src/undo/snapshot.rs:903 — crates/nono/src/undo/snapshot.rs:903-916 | crates/nono/src/undo/snapshot.rs:1024-1037 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:903` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3752 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3752-3765 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3156-3169 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3752` 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) crates/nono-proxy/src/reverse.rs:1717 — crates/nono-proxy/src/reverse.rs:1717-1730 | crates/nono-proxy/src/reverse.rs:1760-1773 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:1717` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) crates/nono/src/keystore.rs:811 — crates/nono/src/keystore.rs:811-824 | crates/nono/src/keystore.rs:901-914 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:811` 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.
D1 · Cyclomatic Complexity · nono_proxy · ×13
  • nono_proxy::tls_intercept::handle::handle_inner_request (cyclomatic 47) crates/nono-proxy/src/tls_intercept/handle.rs:1018 — nono_proxy::tls_intercept::handle::handle_inner_request has cyclomatic complexity 47 (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.
  • nono_proxy::server::handle_connection (cyclomatic 44) crates/nono-proxy/src/server.rs:1719 — nono_proxy::server::handle_connection has cyclomatic complexity 44 (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.
  • nono_proxy::reverse::handle_reverse_proxy (cyclomatic 38) crates/nono-proxy/src/reverse.rs:129 — nono_proxy::reverse::handle_reverse_proxy has cyclomatic complexity 38 (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.
  • nono_proxy::tls_intercept::h2_forward::handle_h2_stream (cyclomatic 33) crates/nono-proxy/src/tls_intercept/h2_forward.rs:232 — nono_proxy::tls_intercept::h2_forward::handle_h2_stream has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • nono_proxy::tls_intercept::handle::select_intercept_route (cyclomatic 29) crates/nono-proxy/src/tls_intercept/handle.rs:493 — nono_proxy::tls_intercept::handle::select_intercept_route has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • nono_proxy::aws::operation::resolve (cyclomatic 28) crates/nono-proxy/src/aws/operation.rs:141 — nono_proxy::aws::operation::resolve has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • nono_proxy::server::start_with_network_approval (cyclomatic 27) crates/nono-proxy/src/server.rs:1281 — nono_proxy::server::start_with_network_approval has cyclomatic complexity 27 (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.
  • nono_proxy::reverse::classify_upgrade_attempt (cyclomatic 23) crates/nono-proxy/src/reverse.rs:2166 — nono_proxy::reverse::classify_upgrade_attempt has cyclomatic complexity 23 (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.
  • nono_proxy::endpoint_approval::authorize_group (cyclomatic 21) crates/nono-proxy/src/endpoint_approval.rs:237 — nono_proxy::endpoint_approval::authorize_group 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.
  • nono_proxy::config::validate_no_proxy_host_pattern (cyclomatic 20) crates/nono-proxy/src/config.rs:622 — nono_proxy::config::validate_no_proxy_host_pattern 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.
  • nono_proxy::aws::endpoints::validate_aws_upstream (cyclomatic 19) crates/nono-proxy/src/aws/endpoints.rs:236 — nono_proxy::aws::endpoints::validate_aws_upstream 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.
  • nono_proxy::config::validate_no_proxy_entry (cyclomatic 17) crates/nono-proxy/src/config.rs:410 — nono_proxy::config::validate_no_proxy_entry 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.
  • nono_proxy::server::handle_forward_http (cyclomatic 17) crates/nono-proxy/src/server.rs:2275 — nono_proxy::server::handle_forward_http 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×13
  • Duplicated block (12 lines × 2) crates/nono-cli/src/profile_cmd.rs:1655 — crates/nono-cli/src/profile_cmd.rs:1655-1666 | crates/nono-cli/src/profile_cmd.rs:2136-2147 — 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 (12 lines × 2) crates/nono-cli/src/proxy_command.rs:330 — crates/nono-cli/src/proxy_command.rs:330-341 | crates/nono-cli/src/proxy_runtime.rs:1546-1557 — before extracting anything, compare `crates/nono-cli/src/proxy_command.rs` and `crates/nono-cli/src/proxy_runtime.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 `crates/nono-cli/src/proxy_command.rs:330` 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 (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2427 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2427-2438 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4952-4963 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2427` 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, `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2439` calls `caller_pid` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs:4964` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:2615 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:2615-2626 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:2688-2699 — 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 (12 lines × 2) crates/nono-cli/src/trust_scan.rs:965 — crates/nono-cli/src/trust_scan.rs:965-976 | crates/nono-cli/src/trust_scan.rs:996-1007 — 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 (12 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:2166 — crates/nono-proxy/src/tls_intercept/handle.rs:2166-2177 | crates/nono-proxy/src/tls_intercept/handle.rs:2273-2284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:2166` 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 (12 lines × 2) crates/nono/src/trust/signing.rs:103 — crates/nono/src/trust/signing.rs:103-114 | crates/nono/src/trust/signing.rs:191-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) crates/nono/src/undo/snapshot.rs:217 — crates/nono/src/undo/snapshot.rs:217-228 | crates/nono/src/undo/snapshot.rs:289-300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:217` 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 (12 lines × 2) crates/nono-cli/src/exec_strategy.rs:1188 — crates/nono-cli/src/exec_strategy.rs:1188-1199 | crates/nono-cli/src/exec_strategy.rs:1299-1313 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:1188` 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 (12 lines × 2) crates/nono-cli/src/exec_strategy.rs:2212 — crates/nono-cli/src/exec_strategy.rs:2212-2223 | crates/nono-cli/src/exec_strategy.rs:2900-2912 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:2212` 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 (12 lines × 2) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:430 — crates/nono-cli/src/exec_strategy/supervisor_linux.rs:430-441 | crates/nono-cli/src/exec_strategy/supervisor_linux.rs:488-499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy/supervisor_linux.rs:430` 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 (12 lines × 2) crates/nono-proxy/src/reverse.rs:1917 — crates/nono-proxy/src/reverse.rs:1917-1928 | crates/nono-proxy/src/tls_intercept/handle.rs:2419-2430 — before extracting anything, compare `crates/nono-proxy/src/reverse.rs` and `crates/nono-proxy/src/tls_intercept/handle.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:1917` 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 (12 lines × 2) crates/nono/src/sandbox/macos.rs:221 — crates/nono/src/sandbox/macos.rs:221-232 | crates/nono/src/sandbox/macos.rs:235-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/sandbox/macos.rs:221` 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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×12
  • Repeated repair: crates/nono-cli/src/tool-sandbox/mod.rs crates/nono-cli/src/tool-sandbox/mod.rs:333 — crates/nono-cli/src/tool-sandbox/mod.rs changed 9 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is nono_cli::tool-sandbox::restore_dir_tree_writable at line 333), 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: “fix: file grants negate filesystem.deny - #1949 (#2019)”; “fix(tool-sandbox): derive shim broker socket from executable path (#2002)”; “fix(tool-sandbox): isolate network policy by effective command scope (#1981)”; “fix(exec): keep session temp files alive against the OS reaper (#1942)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/tool-sandbox/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.
  • Repeated repair: crates/nono-cli/src/network_policy.rs crates/nono-cli/src/network_policy.rs:184 — crates/nono-cli/src/network_policy.rs changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is nono_cli::network_policy::resolve_credentials at line 184), 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: “fix: apply rustfmt to ENDPOINT_ROUTE_PREFIX use sites”; “fix(policy): enable Nix runtime and cache/channel access (#2151)”; “fix(proxy): add redeem_phantoms for by-value phantom redemption (#1469)”; “fix(proxy): honor host:port deny entries under wildcard allow (#1709)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/network_policy.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-cli/src/sandbox_state.rs crates/nono-cli/src/sandbox_state.rs:724 — crates/nono-cli/src/sandbox_state.rs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is nono_cli::sandbox_state::cleanup_stale_state_files at line 724), 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: “fix(why): add pathname Unix socket policy diagnostics (#2220)”; “fix: file grants negate filesystem.deny - #1949 (#2019)”; “fix(why): tolerate volatile process-relative aliases in --self reload (#1873)”; “fix(why): evaluate network.deny_domain in nono why host queries (#1751)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/sandbox_state.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-proxy/src/oauth_capture/rewrite.rs crates/nono-proxy/src/oauth_capture/rewrite.rs:385 — crates/nono-proxy/src/oauth_capture/rewrite.rs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is OAuthCaptureStore::rewrite_form_response_body at line 385), 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: “fix(proxy): redeem phantoms inside Basic credentials on token endpoints (#2225)”; “fix(oauth-capture): rewrite form-urlencoded OAuth token responses (#1836)”; “fix(proxy): resolve the Authorization phantom on token endpoint requests (#2136)”; “fix(credentials): configurable phantom format for prefix-sniffing clients (#1489)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/oauth_capture/rewrite.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-proxy/src/filter.rs crates/nono-proxy/src/filter.rs:202 — crates/nono-proxy/src/filter.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is ProxyFilter::check_host_result at line 202), 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: “fix(proxy): honor host:port deny entries under wildcard allow (#1709)”; “fix(net_filter): normalize hostnames before deny/allow-list matching (#1676)”; “fix(proxy): check hostname allowlist before DNS resolution (#1675)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/filter.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-proxy/src/token.rs crates/nono-proxy/src/token.rs:176 — crates/nono-proxy/src/token.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is PhantomTemplate::parse_route at line 176), 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: “fix(credentials): configurable phantom format for prefix-sniffing clients (#1489)”; “fix(proxy): add redeem_phantoms for by-value phantom redemption (#1469)”; “fix(proxy): decode Basic auth for basic_auth phantom validation (#1683)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/token.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-proxy/src/oauth_capture/mod.rs crates/nono-proxy/src/oauth_capture/mod.rs:62 — crates/nono-proxy/src/oauth_capture/mod.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is OAuthCaptureStore::load_with_persistence at line 62), 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: “fix(oauth-capture): rewrite form-urlencoded OAuth token responses (#1836)”; “fix(proxy): resolve the Authorization phantom on token endpoint requests (#2136)”; “fix(credentials): configurable phantom format for prefix-sniffing clients (#1489)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/oauth_capture/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.
  • Repeated repair: crates/nono-cli/src/tool-sandbox/credentials.rs crates/nono-cli/src/tool-sandbox/credentials.rs:39 — crates/nono-cli/src/tool-sandbox/credentials.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is nono_cli::tool-sandbox::credentials::resolve_credentials at line 39), 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: “fix(tool-sandbox): isolate network policy by effective command scope (#1981)”; “fix(sandbox): expand env vars anywhere in local-socket path, not just as prefix (#1762)”; “fix(credentials): configurable phantom format for prefix-sniffing clients (#1489)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/tool-sandbox/credentials.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-cli/src/tool-sandbox/token_broker.rs crates/nono-cli/src/tool-sandbox/token_broker.rs:273 — crates/nono-cli/src/tool-sandbox/token_broker.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is TokenBroker::scan_and_reissue at line 273), 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: “fix(cli): always re-invoke the credential source for ambient captures (#1849)”; “fix(credentials): configurable phantom format for prefix-sniffing clients (#1489)”; “fix(proxy): add redeem_phantoms for by-value phantom redemption (#1469)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-cli/src/tool-sandbox/token_broker.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-proxy/src/capture.rs crates/nono-proxy/src/capture.rs:76 — crates/nono-proxy/src/capture.rs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is CredentialCaptureError::new at line 76), 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: “fix(proxy): explain unavailable managed credentials to clients”; “fix(proxy): omit credential failure bodies for HTTP/1.1 HEAD”; “fix(proxy): distinguish credential capture failures in HTTP responses”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/capture.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-proxy/src/external.rs crates/nono-proxy/src/external.rs:186 — crates/nono-proxy/src/external.rs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is nono_proxy::external::handle_external_proxy at line 186), 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: “fix(proxy): fail upstream connections that go silent (#2237)”; “fix(proxy): answer 407 when an unauthenticated CONNECT arrives with an upstream proxy (#2133)”; “fix(proxy): bound per-line reads of the WebSocket upgrade response (#1617)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/external.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: crates/nono-proxy/src/forward.rs crates/nono-proxy/src/forward.rs:382 — crates/nono-proxy/src/forward.rs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is nono_proxy::forward::rewrite_http1_response at line 382), 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: “fix(proxy): fail upstream connections that go silent (#2237)”; “fix(oauth-capture): rewrite form-urlencoded OAuth token responses (#1836)”; “fix(proxy): fail closed when upstream DNS returns no addresses (#1894)”. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:47:02 +00:00' --until='2026-11-14 19:47:02 +00:00' --full-history --no-merges -- crates/nono-proxy/src/forward.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 (6 lines × 2) · ×12
  • Duplicated block (6 lines × 2) crates/nono-cli/src/config/version.rs:46 — crates/nono-cli/src/config/version.rs:46-51 | crates/nono-cli/src/package.rs:337-342 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1223 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1223-1228 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:930-935 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) crates/nono-cli/src/url_open.rs:103 — crates/nono-cli/src/url_open.rs:103-108 | crates/nono-cli/src/url_open.rs:112-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/url_open.rs:103` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) crates/nono-proxy/src/config.rs:729 — crates/nono-proxy/src/config.rs:729-734 | crates/nono/src/net_filter.rs:224-229 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/config.rs:729` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) crates/nono-proxy/src/config.rs:1299 — crates/nono-proxy/src/config.rs:1299-1304 | crates/nono-proxy/src/config.rs:1490-1495 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/config.rs:1299` 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 `rules` to `&[EndpointRule]` in one and `&[EndpointPolicyRule]` 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) crates/nono-cli/src/profile_cmd.rs:1512 — crates/nono-cli/src/profile_cmd.rs:1512-1517 | crates/nono-cli/src/profile_cmd.rs:1755-1760 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/profile_cmd.rs:1512` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2621 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2621-2626 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5150-5155 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) crates/nono-cli/src/pty_proxy.rs:2532 — crates/nono-cli/src/pty_proxy.rs:2532-2537 | crates/nono-cli/src/pty_proxy.rs:2574-2580 — 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 (6 lines × 2) crates/nono-cli/src/connect_client.rs:656 — crates/nono-cli/src/connect_client.rs:656-661 | crates/nono-cli/src/url_open.rs:121-127 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/connect_client.rs:656` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2306 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2306-2311 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4818-4823 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2306` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) crates/nono-cli/src/sandbox_prepare.rs:1376 — crates/nono-cli/src/sandbox_prepare.rs:1376-1381 | crates/nono-cli/src/sandbox_prepare.rs:1387-1392 — 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 (6 lines × 2) crates/nono/src/sandbox/linux.rs:1045 — crates/nono/src/sandbox/linux.rs:1045-1050 | crates/nono/src/sandbox/linux.rs:1221-1226 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×11
  • Duplicated block (5 lines × 2) crates/nono-cli/src/connect_client.rs:878 — crates/nono-cli/src/connect_client.rs:878-884 | crates/nono-cli/src/remote_run.rs:367-371 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/connect_client.rs:878` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2545 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2545-2549 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5070-5074 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2822 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2822-2826 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5357-5361 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5305 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5305-5309 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4607-4611 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) crates/nono/src/keystore.rs:523 — crates/nono/src/keystore.rs:523-530 | crates/nono/src/keystore.rs:706-710 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:523` 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 (5 lines × 2) crates/nono-cli/src/trust_keystore.rs:315 — crates/nono-cli/src/trust_keystore.rs:315-320 | crates/nono-cli/src/trust_keystore.rs:324-328 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_keystore.rs:315` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) crates/nono-cli/src/profile_cmd.rs:1895 — crates/nono-cli/src/profile_cmd.rs:1895-1899 | crates/nono-cli/src/profile_cmd.rs:1924-1928 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/profile_cmd.rs:1895` 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 (5 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3012 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3012-3016 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5651-5655 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3012` 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 (5 lines × 2) crates/nono-cli/src/profile_cmd.rs:2130 — crates/nono-cli/src/profile_cmd.rs:2130-2134 | crates/nono-cli/src/profile_cmd.rs:2267-2271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/profile_cmd.rs:2130` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3800 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3800-3804 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3223-3227 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/nono-cli/src/tool-sandbox/platform/macos.rs:3228` calls `add_launch_services_caps`, `add_child_process_exec_gate_with_policy`, `Some` and `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3805` 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 (5 lines × 2) crates/nono/src/sandbox/macos.rs:422 — crates/nono/src/sandbox/macos.rs:422-426 | crates/nono/src/sandbox/macos.rs:444-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/sandbox/macos.rs:422` 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 (15 lines × 2) · ×9
  • Duplicated block (15 lines × 2) crates/nono-cli/src/exec_strategy.rs:1123 — crates/nono-cli/src/exec_strategy.rs:1123-1137 | crates/nono-cli/src/exec_strategy.rs:1329-1343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:1123` 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:481 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:481-495 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:457-471 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/nono-cli/src/tool-sandbox/platform/macos.rs:472` calls `add_macos_cwd_metadata_rules`, `add_outer_process_exec_gate` and `crates/nono-cli/src/tool-sandbox/platform/linux.rs:496` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1858 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1858-1872 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1593-1607 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1858` 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) crates/nono-cli/src/trust_intercept.rs:137 — crates/nono-cli/src/trust_intercept.rs:137-151 | crates/nono-cli/src/trust_intercept.rs:285-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) crates/nono-proxy/src/reverse.rs:524 — crates/nono-proxy/src/reverse.rs:524-538 | crates/nono-proxy/src/reverse.rs:816-830 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:524` 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 (15 lines × 2) crates/nono/src/undo/snapshot.rs:229 — crates/nono/src/undo/snapshot.rs:229-243 | crates/nono/src/undo/snapshot.rs:335-349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:229` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) crates/nono-cli/src/exec_strategy.rs:754 — crates/nono-cli/src/exec_strategy.rs:754-768 | crates/nono-cli/src/exec_strategy.rs:780-794 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:569 — crates/nono-cli/src/exec_strategy/supervisor_linux.rs:569-583 | crates/nono-cli/src/exec_strategy/supervisor_linux.rs:586-600 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy/supervisor_linux.rs:586` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 2) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:586 — crates/nono-cli/src/exec_strategy/supervisor_linux.rs:586-600 | crates/nono-cli/src/exec_strategy/supervisor_linux.rs:603-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 `crates/nono-cli/src/exec_strategy/supervisor_linux.rs:586` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D3 · God Classes · TooManyFields · ×8
  • TooManyFields: PreparedSandbox crates/nono-cli/src/sandbox_prepare.rs:529 — TooManyFields — 50 stored fields. The bar is 30 stored fields; this is 20 over it, 1.67× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
  • TooManyFields: SandboxArgs crates/nono-cli/src/cli.rs:1061 — TooManyFields — 48 stored fields beside 2 methods. The bar is 30 stored fields; this is 18 over it, 1.60× 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: PreparedProfile crates/nono-cli/src/profile_runtime.rs:8 — TooManyFields — 43 stored fields. The bar is 30 stored fields; this is 13 over it, 1.43× 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: NetworkAuditEvent crates/nono/src/undo/types.rs:303 — TooManyFields — 35 stored fields. The bar is 30 stored fields; this is 5 over it, 1.17× 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: ExecutionFlags crates/nono-cli/src/launch_runtime.rs:239 — TooManyFields — 33 stored fields beside 1 method. The bar is 30 stored fields; this is 3 over it, 1.10× 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: WhyArgs crates/nono-cli/src/cli.rs:2345 — 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.
  • TooManyFields: WrapSandboxArgs crates/nono-cli/src/cli.rs:1670 — TooManyFields — 31 stored fields. The bar is 30 stored fields; this is 1 over it, 1.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: ProfileDeserialize crates/nono-cli/src/profile/mod.rs:3203 — TooManyFields — 31 stored fields. The bar is 30 stored fields; this is 1 over it, 1.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.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×8
  • Edited copy of a member (10 corresponding lines) crates/nono-cli/src/command_policy.rs:3796 — crates/nono-cli/src/command_policy.rs:3796-3805 | crates/nono-cli/src/profile/mod.rs:4428-4437 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) crates/nono-cli/src/connect_client.rs:1106 — crates/nono-cli/src/connect_client.rs:1106-1115 | crates/nono-cli/src/connect_client.rs:1117-1126 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) crates/nono-cli/src/rollback_runtime.rs:313 — crates/nono-cli/src/rollback_runtime.rs:313-322 | crates/nono-cli/src/rollback_runtime.rs:328-341 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) crates/nono-cli/src/capability_ext.rs:51 — crates/nono-cli/src/capability_ext.rs:51-60 | crates/nono-cli/src/capability_ext.rs:86-95 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) crates/nono-cli/src/profile_save_runtime.rs:1642 — crates/nono-cli/src/profile_save_runtime.rs:1642-1651 | crates/nono-cli/src/profile_save_runtime.rs:1653-1662 — 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) bindings/c/src/query.rs:84 — bindings/c/src/query.rs:84-93 | bindings/c/src/state.rs:28-37 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2321 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2321-2333 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4833-4842 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) crates/nono-cli/src/policy.rs:467 — crates/nono-cli/src/policy.rs:467-476 | crates/nono-proxy/src/config.rs:1587-1596 — 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 (22 lines × 2) · ×8
  • Duplicated block (22 lines × 2) crates/nono-cli/src/pty_proxy.rs:2458 — crates/nono-cli/src/pty_proxy.rs:2458-2479 | crates/nono-cli/src/pty_proxy.rs:2486-2507 — 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 (22 lines × 2) crates/nono-cli/src/rollback_commands.rs:901 — crates/nono-cli/src/rollback_commands.rs:901-922 | crates/nono-cli/src/rollback_commands.rs:962-983 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/rollback_commands.rs:901` 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 (22 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1533 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1533-1554 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1673-1694 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1533` 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 (22 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2655 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2655-2676 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5184-5205 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1263 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:1263-1284 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1395-1416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/macos.rs:1263` 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 (22 lines × 2) crates/nono-proxy/src/connect.rs:666 — crates/nono-proxy/src/connect.rs:666-687 | crates/nono-proxy/src/forward.rs:232-253 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 2) crates/nono/src/supervisor/socket.rs:259 — crates/nono/src/supervisor/socket.rs:259-280 | crates/nono/src/supervisor/socket.rs:316-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (22 lines × 2) tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:62 — tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:62-83 | tool-sandbox-examples/kubernetes/https-front-proxy.py:62-83 — `tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py` and `tool-sandbox-examples/kubernetes/https-front-proxy.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 102 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×8
  • Duplicated block (16 lines × 2) crates/nono-cli/src/exec_strategy.rs:2863 — crates/nono-cli/src/exec_strategy.rs:2863-2878 | crates/nono-cli/src/exec_strategy.rs:3254-3269 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:2863` 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) crates/nono-cli/src/exec_strategy.rs:2912 — crates/nono-cli/src/exec_strategy.rs:2912-2927 | crates/nono-cli/src/exec_strategy.rs:3381-3396 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/nono-cli/src/exec_strategy.rs:3400` calls `Some`, `reap_reparented_orphans`, `Ok` and `crates/nono-cli/src/exec_strategy.rs:2929` 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 (16 lines × 2) crates/nono-cli/src/policy.rs:1610 — crates/nono-cli/src/policy.rs:1610-1625 | crates/nono-cli/src/policy.rs:1720-1735 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1585 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1585-1600 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1316-1331 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1585` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1584` calls `passthrough` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs:1315` 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 (16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2927 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2927-2942 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5462-5477 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3387 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3387-3402 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3405-3420 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2714 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2714-2729 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5247-5262 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2714` 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) crates/nono/src/sandbox/linux.rs:2823 — crates/nono/src/sandbox/linux.rs:2823-2840 | crates/nono/src/sandbox/linux.rs:2856-2871 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/sandbox/linux.rs:2823` 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. 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.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×7
  • Edited copy of a member (14 corresponding lines) crates/nono-cli/src/pack_update_hint.rs:301 — crates/nono-cli/src/pack_update_hint.rs:301-315 | crates/nono-cli/src/update_check.rs:289-302 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5602 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5602-5618 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:5621-5634 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/nono-cli/src/capability_ext.rs:479 — crates/nono-cli/src/capability_ext.rs:479-492 | crates/nono-cli/src/policy.rs:600-619 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1218 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1218-1236 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:925-938 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3164 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3164-3177 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3432-3452 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/nono-proxy/src/reverse.rs:1915 — crates/nono-proxy/src/reverse.rs:1915-1928 | crates/nono-proxy/src/tls_intercept/handle.rs:2417-2430 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/nono-cli/src/terminal_capture/file_sink.rs:116 — crates/nono-cli/src/terminal_capture/file_sink.rs:116-132 | crates/nono-proxy/src/oauth_capture/persist.rs:123-136 — 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) · ×7
  • Edited copy of a member (13 corresponding lines) crates/nono-proxy/src/route.rs:884 — crates/nono-proxy/src/route.rs:884-897 | crates/nono-proxy/src/server.rs:961-973 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/nono-cli/src/audit_event_reader.rs:76 — crates/nono-cli/src/audit_event_reader.rs:76-93 | crates/nono-cli/src/audit_event_reader.rs:151-163 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/nono-cli/src/audit_commands.rs:979 — crates/nono-cli/src/audit_commands.rs:979-991 | crates/nono-cli/src/rollback_commands.rs:173-187 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/nono-cli/src/lineage_cgroup.rs:289 — crates/nono-cli/src/lineage_cgroup.rs:289-302 | crates/nono-cli/src/resource_cgroup.rs:365-377 — 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) bindings/c/src/state.rs:68 — bindings/c/src/state.rs:68-80 | bindings/c/src/state.rs:123-136 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/nono-cli/src/trust_cmd.rs:1517 — crates/nono-cli/src/trust_cmd.rs:1517-1532 | crates/nono-cli/src/trust_scan.rs:1159-1171 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/nono-proxy/src/reverse.rs:2350 — crates/nono-proxy/src/reverse.rs:2350-2362 | crates/nono-proxy/src/reverse.rs:2368-2380 — 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 (12 corresponding lines) · ×7
  • Edited copy of a member (12 corresponding lines) crates/nono-proxy/src/config.rs:728 — crates/nono-proxy/src/config.rs:728-739 | crates/nono/src/net_filter.rs:223-238 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2164 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2164-2176 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:2641-2652 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) crates/nono-cli/src/sandbox_state.rs:705 — crates/nono-cli/src/sandbox_state.rs:705-716 | crates/nono-cli/src/session.rs:542-553 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) crates/nono-cli/src/terminal_capture/writer.rs:316 — crates/nono-cli/src/terminal_capture/writer.rs:316-330 | crates/nono-cli/src/terminal_capture/writer.rs:550-561 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:229 — crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:229-240 | crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:325-336 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2223 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2223-2237 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4895-4906 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2997 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2997-3008 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5598-5609 — 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 (19 lines × 2) · ×7
  • Duplicated block (19 lines × 2) crates/nono-cli/src/diagnostic/formatter.rs:2914 — crates/nono-cli/src/diagnostic/formatter.rs:2914-2932 | crates/nono-cli/src/exec_strategy.rs:4296-4314 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) crates/nono-cli/src/network_policy.rs:256 — crates/nono-cli/src/network_policy.rs:256-274 | crates/nono-cli/src/proxy_runtime.rs:1980-1998 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/network_policy.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.
  • Duplicated block (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1961 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1961-1979 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2040-2058 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1961` 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2441 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2441-2459 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4966-4984 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2441` 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2629 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2629-2647 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5158-5176 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5285 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5285-5303 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4534-4552 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1704 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:1704-1722 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1790-1808 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/macos.rs:1704` 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.
D2 · Cognitive Complexity · CapabilitySet · ×6
  • CapabilitySet::from_profile (cognitive 103) crates/nono-cli/src/capability_ext.rs:693 — CapabilitySet::from_profile has cognitive complexity 103 (threshold 15). Drivers by points: if/else 31 (71 pts), loops 23 (30 pts), boolean chains 2 (nesting depth added 47). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • CapabilitySet::try_from (cognitive 43) crates/nono/src/manifest_convert.rs:24 — CapabilitySet::try_from has cognitive complexity 43 (threshold 15). Drivers by points: loops 8 (21 pts), if/else 7 (13 pts), match/switch 3 (9 pts) (nesting depth added 25). 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.
  • CapabilitySet::deduplicate_unix_sockets (cognitive 41) crates/nono/src/capability.rs:1949 — CapabilitySet::deduplicate_unix_sockets has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (27 pts), boolean chains 7, loops 4, match/switch 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • CapabilitySet::deduplicate (cognitive 40) crates/nono/src/capability.rs:1792 — CapabilitySet::deduplicate has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (28 pts), boolean chains 5, loops 4, match/switch 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • CapabilitySet::from_args (cognitive 23) crates/nono-cli/src/capability_ext.rs:586 — CapabilitySet::from_args has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 10 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (nono_cli::capability_ext::add_cli_overrides) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • CapabilitySet::scan_covering (cognitive 18) crates/nono/src/capability.rs:1526 — CapabilitySet::scan_covering has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3, 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.
D3 · God Classes · MethodTooLong · ×6
  • MethodTooLong: CapabilitySet.from_profile crates/nono-cli/src/capability_ext.rs:693 — MethodTooLong — from_profile runs 313 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 213 over it, 3.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ProxyCredentialCaptureBackend.run_capture_command crates/nono-cli/src/proxy_runtime.rs:390 — MethodTooLong — run_capture_command runs 187 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 87 over it, 1.87× 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: RouteStore.load_with_registry crates/nono-proxy/src/route.rs:252 — MethodTooLong — load_with_registry runs 169 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 69 over it, 1.69× 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: DiagnosticFormatter.format_exit_explanation crates/nono-cli/src/diagnostic/formatter.rs:1035 — MethodTooLong — format_exit_explanation runs 139 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 39 over it, 1.39× 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: TerminalApproval.prompt crates/nono-cli/src/terminal_approval.rs:92 — MethodTooLong — prompt runs 137 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 37 over it, 1.37× 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: PtyProxy.try_accept crates/nono-cli/src/pty_proxy.rs:639 — MethodTooLong — try_accept 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.
D3 · God Classes · ClassTooLong · ×6
  • ClassTooLong: DiagnosticFormatter crates/nono-cli/src/diagnostic/formatter.rs:651 — ClassTooLong — 1183 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 74 methods, 2 blocks, lines 651-2481. The bar is 400 significant lines; this is 783 over it, 2.96× 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: PtyProxy crates/nono-cli/src/pty_proxy.rs:333 — ClassTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 45 methods, 3 blocks, lines 333-2017. The bar is 400 significant lines; this is 330 over it, 1.83× 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: SnapshotManager crates/nono/src/undo/snapshot.rs:62 — ClassTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 62-951. The bar is 400 significant lines; this is 118 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: CapabilitySet crates/nono/src/capability.rs:952 — ClassTooLong — 487 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 74 methods, 2 blocks, lines 952-2101. The bar is 400 significant lines; this is 87 over it, 1.22× 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: ProxyCredentialCaptureBackend crates/nono-cli/src/proxy_runtime.rs:144 — ClassTooLong — 452 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 3 blocks, lines 144-786. The bar is 400 significant lines; this is 52 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Commands crates/nono-cli/src/cli.rs:112 — ClassTooLong — 436 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 0 methods. The bar is 400 significant lines; this is 36 over it, 1.09× 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 (7 corresponding lines) · ×6
  • Edited copy of a member (7 corresponding lines) crates/nono-cli/src/profile_cmd.rs:2121 — crates/nono-cli/src/profile_cmd.rs:2121-2259 | crates/nono-cli/src/profile_cmd.rs:2264-2285 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2363 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2363-2369 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4875-4881 — 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) crates/nono-cli/src/trust_cmd.rs:1571 — crates/nono-cli/src/trust_cmd.rs:1571-1577 | crates/nono-cli/src/trust_keystore.rs:386-392 — 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) crates/nono/src/audit.rs:955 — crates/nono/src/audit.rs:955-961 | crates/nono/src/undo/merkle.rs:135-141 — 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) crates/nono-cli/src/platform_client.rs:707 — crates/nono-cli/src/platform_client.rs:707-714 | crates/nono/src/trust/digest.rs:42-48 — 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) crates/nono-cli/src/profile_save_runtime.rs:989 — crates/nono-cli/src/profile_save_runtime.rs:989-995 | crates/nono-cli/src/terminal_prompt.rs:27-33 — 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 · Duplicated block (26 lines × 2) · ×6
  • Duplicated block (26 lines × 2) crates/nono-cli/src/capability_ext.rs:654 — crates/nono-cli/src/capability_ext.rs:654-679 | crates/nono-cli/src/capability_ext.rs:1290-1315 — 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 (26 lines × 2) crates/nono-cli/src/sandbox_state.rs:352 — crates/nono-cli/src/sandbox_state.rs:352-377 | crates/nono-cli/src/session.rs:833-858 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `path` to `&std::path::Path` in one and `&Path` 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 (26 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:715 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:715-740 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:627-652 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/nono-cli/src/tool-sandbox/platform/macos.rs:654` calls `pub`, `record_main_start`, `log_main_total` and `crates/nono-cli/src/tool-sandbox/platform/linux.rs:742` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (26 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4074 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4074-4099 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3753-3778 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (26 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4224 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4224-4249 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3870-3895 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (26 lines × 2) tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:120 — tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:120-145 | tool-sandbox-examples/kubernetes/https-front-proxy.py:120-145 — `tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py` and `tool-sandbox-examples/kubernetes/https-front-proxy.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 102 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×6
  • Duplicated block (18 lines × 2) crates/nono-cli/src/registry_client.rs:233 — crates/nono-cli/src/registry_client.rs:233-250 | crates/nono-cli/src/registry_client.rs:354-371 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/registry_client.rs:233` 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 (18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4859 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4859-4876 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4397-4414 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) crates/nono-proxy/src/reverse.rs:233 — crates/nono-proxy/src/reverse.rs:233-250 | crates/nono-proxy/src/reverse.rs:468-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:233` 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 (18 lines × 2) crates/nono/src/capability.rs:1238 — crates/nono/src/capability.rs:1238-1255 | crates/nono/src/capability.rs:1435-1452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `mut` in one and `&mut` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (18 lines × 2) crates/nono-cli/src/profile/mod.rs:1649 — crates/nono-cli/src/profile/mod.rs:1649-1666 | crates/nono-cli/src/proxy_runtime.rs:1305-1322 — 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 (18 lines × 2) crates/nono-proxy/src/credential.rs:511 — crates/nono-proxy/src/credential.rs:511-528 | crates/nono-proxy/src/credential.rs:588-606 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/credential.rs:511` 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 (10 lines × 3) · ×6
  • Duplicated block (10 lines × 3) crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:255 — crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:255-264 | crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:306-315 | crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:351-360 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) crates/nono/src/capability.rs:162 — crates/nono/src/capability.rs:162-171 | crates/nono/src/capability.rs:200-209 | crates/nono/src/capability.rs:534-543 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) crates/nono/src/undo/snapshot.rs:416 — crates/nono/src/undo/snapshot.rs:416-425 | crates/nono/src/undo/snapshot.rs:782-791 | crates/nono/src/undo/snapshot.rs:868-877 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:416` 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 × 3) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2811 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2811-2820 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5346-5355 | crates/nono/src/broker_path.rs:219-228 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 3) crates/nono-cli/src/connect_client.rs:681 — crates/nono-cli/src/connect_client.rs:681-690 | crates/nono-cli/src/platform_oauth/client.rs:195-205 | crates/nono-cli/src/platform_oauth/client.rs:677-686 — there are 3 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 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/connect_client.rs:681` 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 × 3) crates/nono/src/keystore.rs:1261 — crates/nono/src/keystore.rs:1261-1271 | crates/nono/src/keystore.rs:1347-1357 | crates/nono/src/keystore.rs:1526-1535 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:1261` 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.
D1 · Cyclomatic Complexity · CapabilitySet · ×5
  • CapabilitySet::from_profile (cyclomatic 52) crates/nono-cli/src/capability_ext.rs:693 — CapabilitySet::from_profile has cyclomatic complexity 52 (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.
  • CapabilitySet::deduplicate_unix_sockets (cyclomatic 21) crates/nono/src/capability.rs:1949 — CapabilitySet::deduplicate_unix_sockets 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.
  • CapabilitySet::try_from (cyclomatic 20) crates/nono/src/manifest_convert.rs:24 — CapabilitySet::try_from has cyclomatic complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
  • CapabilitySet::deduplicate (cyclomatic 19) crates/nono/src/capability.rs:1792 — CapabilitySet::deduplicate 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.
  • CapabilitySet::from_args (cyclomatic 18) crates/nono-cli/src/capability_ext.rs:586 — CapabilitySet::from_args has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (nono_cli::capability_ext::add_cli_overrides) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SnapshotManager · ×5
  • SnapshotManager::walk_and_store (cognitive 43) crates/nono/src/undo/snapshot.rs:732 — SnapshotManager::walk_and_store has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (31 pts), match/switch 2 (7 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 27). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • SnapshotManager::restore_to (cognitive 34) crates/nono/src/undo/snapshot.rs:288 — SnapshotManager::restore_to has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 4, match/switch 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • SnapshotManager::walk_current (cognitive 22) crates/nono/src/undo/snapshot.rs:839 — SnapshotManager::walk_current has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • SnapshotManager::collect_atomic_temp_files (cognitive 20) crates/nono/src/undo/snapshot.rs:401 — SnapshotManager::collect_atomic_temp_files has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • SnapshotManager::validate_restore_target (cognitive 17) crates/nono/src/undo/snapshot.rs:621 — SnapshotManager::validate_restore_target has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 3 (5 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.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×5
  • Edited copy of a member (16 corresponding lines) crates/nono-cli/src/exec_strategy.rs:2385 — crates/nono-cli/src/exec_strategy.rs:2385-2400 | crates/nono-cli/src/pty_proxy.rs:2599-2614 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2944 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2944-2959 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5515-5536 — 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) crates/nono-cli/src/tool-sandbox/platform/macos.rs:2801 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:2801-2817 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:2930-2945 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2339 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2339-2354 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4848-4864 — 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) crates/nono/src/undo/snapshot.rs:901 — crates/nono/src/undo/snapshot.rs:901-916 | crates/nono/src/undo/snapshot.rs:1021-1037 — 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 copy of a member (8 corresponding lines) · ×5
  • Edited copy of a member (8 corresponding lines) crates/nono-cli/src/audit_commands.rs:1004 — crates/nono-cli/src/audit_commands.rs:1004-1011 | crates/nono-cli/src/rollback_commands.rs:1064-1075 — 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) crates/nono-proxy/src/aws/operation.rs:76 — crates/nono-proxy/src/aws/operation.rs:76-83 | crates/nono-cli/src/exec_strategy/env_sanitization.rs:131-138 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3057 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3057-3064 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5695-5702 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4156 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4156-4163 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3976-3983 — 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) crates/nono-cli/src/audit_session.rs:187 — crates/nono-cli/src/audit_session.rs:187-194 | crates/nono-cli/src/rollback_session.rs:137-144 — 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 (9 corresponding lines) · ×5
  • Edited copy of a member (9 corresponding lines) crates/nono-cli/src/pty_proxy.rs:442 — crates/nono-cli/src/pty_proxy.rs:442-451 | crates/nono-cli/src/pty_proxy.rs:1922-1930 — 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) crates/nono/src/keystore.rs:1727 — crates/nono/src/keystore.rs:1727-1735 | crates/nono/src/keystore.rs:1741-1750 — 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) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:1159 — crates/nono-cli/src/exec_strategy/supervisor_linux.rs:1159-1167 | crates/nono/src/capability.rs:1606-1614 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2772 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2772-2780 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5335-5344 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:742 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:742-750 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:657-665 — 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 · Duplicated block (14–15 lines × 2) · ×5
  • Duplicated block (14–15 lines × 2) crates/nono-cli/src/diagnostic/formatter.rs:125 — crates/nono-cli/src/diagnostic/formatter.rs:125-138 | crates/nono-cli/src/output.rs:1319-1333 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/diagnostic/formatter.rs:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:309 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:309-322 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:321-335 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14–15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1563 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1563-1577 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1298-1311 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1563` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2274 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2274-2288 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4793-4806 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2274` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (14–15 lines × 2) crates/nono-proxy/src/reverse.rs:585 — crates/nono-proxy/src/reverse.rs:585-598 | crates/nono-proxy/src/reverse.rs:1489-1503 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:1489` 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 × 3) · ×5
  • Duplicated block (7 lines × 3) crates/nono-cli/src/capability_ext.rs:769 — crates/nono-cli/src/capability_ext.rs:769-775 | crates/nono-cli/src/capability_ext.rs:792-798 | crates/nono-cli/src/capability_ext.rs:812-818 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/capability_ext.rs:769` 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 × 3) crates/nono-cli/src/command_policy.rs:2796 — crates/nono-cli/src/command_policy.rs:2796-2802 | crates/nono-cli/src/command_policy.rs:2836-2842 | crates/nono-cli/src/command_policy.rs:2995-3001 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/nono-cli/src/command_policy.rs:3002` calls `is_some` and `crates/nono-cli/src/command_policy.rs:2803` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) crates/nono-proxy/src/tls_intercept/handle.rs:1395 — crates/nono-proxy/src/tls_intercept/handle.rs:1395-1401 | crates/nono-proxy/src/tls_intercept/handle.rs:1651-1657 | crates/nono-proxy/src/tls_intercept/handle.rs:1991-1997 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:1395` 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 × 3) crates/nono-cli/src/output.rs:686 — crates/nono-cli/src/output.rs:686-692 | crates/nono-cli/src/output.rs:754-763 | crates/nono-cli/src/output.rs:787-793 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/nono-cli/src/output.rs:694` calls `Some` and `crates/nono-cli/src/output.rs:765` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) crates/nono-proxy/src/reverse.rs:2475 — crates/nono-proxy/src/reverse.rs:2475-2481 | crates/nono-proxy/src/reverse.rs:2586-2592 | crates/nono-proxy/src/reverse.rs:2596-2602 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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.
D1 · Cyclomatic Complexity · nono · ×4
  • nono::audit::verify_audit_attestation_bundle (cyclomatic 25) crates/nono/src/audit.rs:1258 — nono::audit::verify_audit_attestation_bundle has cyclomatic complexity 25 (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.
  • nono::capability::tokenize_sexp (cyclomatic 25) crates/nono/src/capability.rs:682 — nono::capability::tokenize_sexp 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.
  • nono::keystore::build_mappings_from_list (cyclomatic 18) crates/nono/src/keystore.rs:1912 — nono::keystore::build_mappings_from_list has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • nono::audit::verify_audit_log (cyclomatic 17) crates/nono/src/audit.rs:1610 — nono::audit::verify_audit_log 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.
D2 · Cognitive Complexity · DiagnosticFormatter · ×4
  • DiagnosticFormatter::format_consolidated_denial_guidance (cognitive 46) crates/nono-cli/src/diagnostic/formatter.rs:1824 — DiagnosticFormatter::format_consolidated_denial_guidance has cognitive complexity 46 (threshold 15). Drivers by points: if/else 27 (42 pts), loops 3 (4 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • DiagnosticFormatter::format_supervised_footer_with_diagnostics (cognitive 37) crates/nono-cli/src/diagnostic/formatter.rs:1313 — DiagnosticFormatter::format_supervised_footer_with_diagnostics has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 10 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • DiagnosticFormatter::format_exit_explanation (cognitive 29) crates/nono-cli/src/diagnostic/formatter.rs:1035 — DiagnosticFormatter::format_exit_explanation has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (26 pts), match/switch 2 (3 pts) (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • DiagnosticFormatter::format_network_denial_guidance (cognitive 18) crates/nono-cli/src/diagnostic/formatter.rs:2260 — DiagnosticFormatter::format_network_denial_guidance has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: proxy_runtime.rs ↔ h2_forward.rs crates/nono-cli/src/proxy_runtime.rs:1 — `crates/nono-cli/src/proxy_runtime.rs` and `crates/nono-proxy/src/tls_intercept/h2_forward.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 `9acac60f` feat(proxy): add phantom_format to custom credentials (#2281); `fc430c9b` feat(proxy): select aws_auth signing profile by placeholder access ke…; `b1c943e6` fix(oauth-capture): rewrite form-urlencoded OAuth token responses (#1… — run `git show` on any of them.
  • Change coupling: cli.rs ↔ package.rs crates/nono-cli/src/cli.rs:1 — `crates/nono-cli/src/cli.rs` and `crates/nono-cli/src/package.rs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `44df7f63` feat(profiles): require fully qualified package profile names (#2118); `64d9f283` feat(package): add package pinning and outdated commands; `829c341a` add commands to manage profile drafts and check package status — run `git show` on any of them.
  • Change coupling: mod.rs ↔ credential.rs crates/nono-cli/src/profile/mod.rs:1 — `crates/nono-cli/src/profile/mod.rs` and `crates/nono-proxy/src/credential.rs` change together 54% of the time (20 of the 37 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 20 shared commits counted here, the most recent 3 are `1afb2cc4` feat(proxy): accept AWS GovCloud regions and s3 bucket-subdomain wild…; `9acac60f` feat(proxy): add phantom_format to custom credentials (#2281); `f71b8d1d` feat(proxy): derive aws_auth signing region from request host for wil… — run `git show` on any of them.
  • Change coupling: audit_commands.rs ↔ rollback_commands.rs crates/nono-cli/src/audit_commands.rs:1 — `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e21e27d1` fix(cli): shell-quote command args in display output (#660); `6ecade2e` feat(audit): add audit attestation for session merkle roots; `02ee0bd1` feat(audit): record executable identity and improve integrity — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×4
  • Edited copy of a member (28 corresponding lines) crates/nono-cli/src/sandbox_state.rs:346 — crates/nono-cli/src/sandbox_state.rs:346-380 | crates/nono-cli/src/session.rs:829-861 — These two members are one piece of code written twice and then edited apart: 28 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 (28 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4105 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4105-4132 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3784-3811 — These two members are one piece of code written twice and then edited apart: 28 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 (28 corresponding lines) crates/nono-cli/src/wiring.rs:1151 — crates/nono-cli/src/wiring.rs:1151-1183 | crates/nono-cli/src/wiring.rs:1469-1496 — These two members are one piece of code written twice and then edited apart: 28 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 (28 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:547 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:547-576 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:495-522 — These two members are one piece of code written twice and then edited apart: 28 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) · ×4
  • Edited copy of a member (27 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3843 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3843-3869 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3374-3404 — 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.
  • Edited copy of a member (27 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4629 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4629-4655 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4160-4190 — 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.
  • Edited copy of a member (27 corresponding lines) crates/nono-cli/src/wiring.rs:1189 — crates/nono-cli/src/wiring.rs:1189-1215 | crates/nono-cli/src/wiring.rs:1223-1254 — 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.
  • Edited copy of a member (27 corresponding lines) crates/nono-cli/src/pty_proxy.rs:2457 — crates/nono-cli/src/pty_proxy.rs:2457-2483 | crates/nono-cli/src/pty_proxy.rs:2485-2515 — 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 copy of a member (19 corresponding lines) · ×4
  • Edited copy of a member (19 corresponding lines) crates/nono-proxy/src/connect.rs:692 — crates/nono-proxy/src/connect.rs:692-711 | crates/nono-proxy/src/external.rs:333-351 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:254 — crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:254-272 | crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:305-323 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) crates/nono-cli/src/config/version.rs:56 — crates/nono-cli/src/config/version.rs:56-74 | crates/nono-cli/src/update_check.rs:236-254 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) crates/nono/src/undo/exclusion.rs:142 — crates/nono/src/undo/exclusion.rs:142-162 | crates/nono/src/undo/exclusion.rs:179-197 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×4
  • Edited copy of a member (17 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3820 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3820-3837 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3353-3369 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3010 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3010-3026 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5649-5666 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) crates/nono-cli/src/pty_proxy.rs:2375 — crates/nono-cli/src/pty_proxy.rs:2375-2393 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:5231-5247 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) crates/nono-cli/src/proxy_runtime.rs:2047 — crates/nono-cli/src/proxy_runtime.rs:2047-2063 | crates/nono-cli/src/tool-sandbox/policy.rs:416-432 — 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 (11 corresponding lines) · ×4
  • Edited copy of a member (11 corresponding lines) crates/nono-cli/src/wiring.rs:1123 — crates/nono-cli/src/wiring.rs:1123-1133 | crates/nono-cli/src/wiring.rs:1419-1430 — 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) crates/nono-cli/src/query_ext.rs:557 — crates/nono-cli/src/query_ext.rs:557-567 | crates/nono-proxy/src/config.rs:1728-1757 — 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) crates/nono-cli/src/profile/mod.rs:3623 — crates/nono-cli/src/profile/mod.rs:3623-3633 | crates/nono-cli/src/profile/mod.rs:3636-3646 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3440 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3440-3450 | crates/nono/src/sandbox/linux.rs:1638-1648 — 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 (21 corresponding lines) · ×4
  • Edited copy of a member (21 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2975 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2975-2995 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5538-5558 — 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.
  • Edited copy of a member (21 corresponding lines) crates/nono-cli/src/output.rs:753 — crates/nono-cli/src/output.rs:753-782 | crates/nono-cli/src/output.rs:786-806 — 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.
  • Edited copy of a member (21 corresponding lines) crates/nono-proxy/src/reverse.rs:2442 — crates/nono-proxy/src/reverse.rs:2442-2463 | crates/nono-proxy/src/reverse.rs:2554-2574 — 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.
  • Edited copy of a member (21 corresponding lines) crates/nono/src/capability.rs:1237 — crates/nono/src/capability.rs:1237-1257 | crates/nono/src/capability.rs:1434-1454 — 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 (6 corresponding lines) · ×4
  • Edited copy of a member (6 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:6089 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:6089-6094 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:6096-6103 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5024 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5024-5029 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4520-4531 — 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) crates/nono-proxy/src/connect.rs:732 — crates/nono-proxy/src/connect.rs:732-738 | crates/nono-proxy/src/external.rs:381-386 — 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) crates/nono-cli/src/launch_runtime.rs:16 — crates/nono-cli/src/launch_runtime.rs:16-30 | crates/nono-cli/src/rollback_runtime.rs:67-72 — 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 · Duplicated block (27 lines × 2) · ×4
  • Duplicated block (27 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1933 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1933-1959 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2012-2038 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1933` 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 (27 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1676 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:1676-1702 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1762-1788 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/macos.rs:1676` 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 (27 lines × 2) tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:33 — tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:33-59 | tool-sandbox-examples/kubernetes/https-front-proxy.py:33-59 — `tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py` and `tool-sandbox-examples/kubernetes/https-front-proxy.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 102 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (27 lines × 2) tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:90 — tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:90-116 | tool-sandbox-examples/kubernetes/https-front-proxy.py:90-116 — `tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py` and `tool-sandbox-examples/kubernetes/https-front-proxy.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 102 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×4
  • Duplicated block (21 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2523 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2523-2543 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5048-5068 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 2) crates/nono-proxy/src/reverse.rs:748 — crates/nono-proxy/src/reverse.rs:748-768 | crates/nono-proxy/src/reverse.rs:770-790 — 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 (21 lines × 2) crates/nono/src/undo/snapshot.rs:733 — crates/nono/src/undo/snapshot.rs:733-753 | crates/nono/src/undo/snapshot.rs:840-860 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:733` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (21 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3409 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3409-3429 | crates/nono/src/sandbox/linux.rs:1599-1619 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:3409` 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 (20 lines × 2) · ×4
  • Duplicated block (20 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2747 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2747-2766 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5310-5329 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2829 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2829-2848 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5364-5383 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) crates/nono-cli/src/trust_cmd.rs:289 — crates/nono-cli/src/trust_cmd.rs:289-308 | crates/nono-cli/src/trust_cmd.rs:417-436 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_cmd.rs:289` 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 (20 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1498 — crates/nono-proxy/src/tls_intercept/handle.rs:1498-1517 | crates/nono-proxy/src/tls_intercept/handle.rs:2032-2051 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:1498` 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 (17–18 lines × 2) · ×4
  • Duplicated block (17–18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:550 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:550-566 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:496-513 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/nono-cli/src/tool-sandbox/platform/linux.rs:567` calls `file_id` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs:514` 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–18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3606 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3606-3623 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3096-3112 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (17–18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4508 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4508-4524 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4038-4055 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:4508` 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 (17–18 lines × 2) crates/nono/src/undo/snapshot.rs:785 — crates/nono/src/undo/snapshot.rs:785-802 | crates/nono/src/undo/snapshot.rs:871-887 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:785` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4
  • Duplicated block (17 lines × 2) crates/nono-cli/src/audit_session.rs:60 — crates/nono-cli/src/audit_session.rs:60-76 | crates/nono-cli/src/rollback_session.rs:55-71 — before extracting anything, compare `crates/nono-cli/src/audit_session.rs` and `crates/nono-cli/src/rollback_session.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_session.rs:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1375 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1375-1391 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1394-1410 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1394` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4882 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4882-4898 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4420-4436 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 2) crates/nono-cli/src/trust_cmd.rs:310 — crates/nono-cli/src/trust_cmd.rs:310-326 | crates/nono-cli/src/trust_cmd.rs:438-454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_cmd.rs:310` 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) · ×4
  • Duplicated block (16–17 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4192 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4192-4207 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3836-3852 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16–17 lines × 2) crates/nono-proxy/src/connect.rs:695 — crates/nono-proxy/src/connect.rs:695-711 | crates/nono-proxy/src/external.rs:336-351 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/connect.rs:695` 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 (16–17 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1376 — crates/nono-proxy/src/tls_intercept/handle.rs:1376-1392 | crates/nono-proxy/src/tls_intercept/handle.rs:2127-2142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:1376` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (16–17 lines × 2) crates/nono/src/undo/snapshot.rs:756 — crates/nono/src/undo/snapshot.rs:756-771 | crates/nono/src/undo/snapshot.rs:805-821 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/snapshot.rs:756` 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.
D1 · Cyclomatic Complexity · DiagnosticFormatter · ×3
  • DiagnosticFormatter::format_supervised_footer_with_diagnostics (cyclomatic 26) crates/nono-cli/src/diagnostic/formatter.rs:1313 — DiagnosticFormatter::format_supervised_footer_with_diagnostics 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.
  • DiagnosticFormatter::format_consolidated_denial_guidance (cyclomatic 25) crates/nono-cli/src/diagnostic/formatter.rs:1824 — DiagnosticFormatter::format_consolidated_denial_guidance 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.
  • DiagnosticFormatter::format_exit_explanation (cyclomatic 23) crates/nono-cli/src/diagnostic/formatter.rs:1035 — DiagnosticFormatter::format_exit_explanation has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · PtyProxy · ×3
  • PtyProxy::try_accept (cognitive 36) crates/nono-cli/src/pty_proxy.rs:639 — PtyProxy::try_accept has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (25 pts), match/switch 5 (10 pts), boolean chains 1 (nesting depth added 19). 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.
  • PtyProxy::filter_client_input (cognitive 31) crates/nono-cli/src/pty_proxy.rs:1423 — PtyProxy::filter_client_input has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 3, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • PtyProxy::drain_master_output (cognitive 25) crates/nono-cli/src/pty_proxy.rs:904 — PtyProxy::drain_master_output has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 1 (4 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: DiagnosticFormatter crates/nono-cli/src/diagnostic/formatter.rs:651 — TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CapabilitySet crates/nono/src/capability.rs:952 — TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PtyProxy crates/nono-cli/src/pty_proxy.rs:333 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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 · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (4 members, 50+ identical tokens) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2828 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2828-2848 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2855-2912 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5363-5383 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5390-5447 — 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) crates/nono-cli/src/trust_keystore.rs:198 — crates/nono-cli/src/trust_keystore.rs:198-227 | crates/nono-cli/src/trust_keystore.rs:229-282 | crates/nono-cli/src/trust_keystore.rs:286-331 | crates/nono-cli/src/trust_keystore.rs:333-372 — 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) crates/nono/src/sandbox/linux.rs:2593 — crates/nono/src/sandbox/linux.rs:2593-2623 | crates/nono/src/sandbox/linux.rs:2704-2727 | crates/nono/src/sandbox/linux.rs:3826-3959 | crates/nono/src/sandbox/linux.rs:3978-4014 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×3
  • Edited copy of a member (39 corresponding lines) crates/nono-cli/src/profile/mod.rs:508 — crates/nono-cli/src/profile/mod.rs:508-578 | crates/nono-cli/src/profile/mod.rs:1769-1807 — 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.
  • Edited copy of a member (39 corresponding lines) crates/nono/src/keystore.rs:320 — crates/nono/src/keystore.rs:320-362 | crates/nono/src/keystore.rs:474-512 — 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.
  • Edited copy of a member (39 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:219 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:219-257 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:237-275 — 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 (32 corresponding lines) · ×3
  • Edited copy of a member (32 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5814 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5814-5845 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:5847-5878 — These two members are one piece of code written twice and then edited apart: 32 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 (32 corresponding lines) crates/nono/src/keystore.rs:1115 — crates/nono/src/keystore.rs:1115-1146 | crates/nono/src/keystore.rs:1577-1619 — These two members are one piece of code written twice and then edited apart: 32 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 (32 corresponding lines) bindings/c/src/capability_set.rs:67 — bindings/c/src/capability_set.rs:67-99 | bindings/c/src/capability_set.rs:114-145 — These two members are one piece of code written twice and then edited apart: 32 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 (38 corresponding lines) · ×3
  • Edited copy of a member (38 corresponding lines) crates/nono-cli/src/exec_strategy.rs:4187 — crates/nono-cli/src/exec_strategy.rs:4187-4224 | crates/nono-cli/src/exec_strategy.rs:4230-4289 — These two members are one piece of code written twice and then edited apart: 38 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 (38 corresponding lines) crates/nono-cli/src/pty_proxy.rs:2518 — crates/nono-cli/src/pty_proxy.rs:2518-2558 | crates/nono-cli/src/pty_proxy.rs:2560-2597 — These two members are one piece of code written twice and then edited apart: 38 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 (38 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/macos.rs:531 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:531-576 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:584-621 — These two members are one piece of code written twice and then edited apart: 38 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 (23 corresponding lines) · ×3
  • Edited copy of a member (23 corresponding lines) crates/nono-cli/src/trust_cmd.rs:1242 — crates/nono-cli/src/trust_cmd.rs:1242-1264 | crates/nono-cli/src/trust_cmd.rs:1267-1292 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) crates/nono-cli/src/diagnostic/formatter.rs:124 — crates/nono-cli/src/diagnostic/formatter.rs:124-146 | crates/nono-cli/src/output.rs:1318-1342 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) crates/nono-cli/src/timeouts.rs:87 — crates/nono-cli/src/timeouts.rs:87-109 | crates/nono-cli/src/timeouts.rs:111-133 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×3
  • Edited copy of a member (18 corresponding lines) crates/nono-proxy/src/forward.rs:165 — crates/nono-proxy/src/forward.rs:165-182 | crates/nono-proxy/src/tls_intercept/h2_forward.rs:205-228 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:594 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:594-617 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:628-645 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) crates/nono-proxy/src/server.rs:777 — crates/nono-proxy/src/server.rs:777-802 | crates/nono-proxy/src/server.rs:808-825 — 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 · Duplicated block (22–23 lines × 2) · ×3
  • Duplicated block (22–23 lines × 2) bindings/c/src/capability_set.rs:68 — bindings/c/src/capability_set.rs:68-90 | bindings/c/src/capability_set.rs:115-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (22–23 lines × 2) crates/nono-cli/src/proxy_command.rs:108 — crates/nono-cli/src/proxy_command.rs:108-129 | crates/nono-cli/src/proxy_runtime.rs:3101-3123 — before extracting anything, compare `crates/nono-cli/src/proxy_command.rs` and `crates/nono-cli/src/proxy_runtime.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 `crates/nono-cli/src/proxy_command.rs:108` 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 (22–23 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4959 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4959-4980 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4490-4512 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:4959` 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 (11–13 lines × 2) · ×3
  • Duplicated block (11–13 lines × 2) crates/nono-cli/src/profile/mod.rs:3657 — crates/nono-cli/src/profile/mod.rs:3657-3667 | crates/nono-cli/src/profile/mod.rs:3800-3812 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11–13 lines × 2) crates/nono-cli/src/sandbox_log.rs:388 — crates/nono-cli/src/sandbox_log.rs:388-398 | crates/nono-cli/src/sandbox_log.rs:404-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/sandbox_log.rs:388` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4763 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4763-4775 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4303-4313 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×3
  • Duplicated block (12 lines × 3) crates/nono-cli/src/tool-sandbox/launch.rs:80 — crates/nono-cli/src/tool-sandbox/launch.rs:80-91 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2962-2973 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5612-5623 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 3) crates/nono-proxy/src/tls_intercept/handle.rs:1554 — crates/nono-proxy/src/tls_intercept/handle.rs:1554-1565 | crates/nono-proxy/src/tls_intercept/handle.rs:1579-1590 | crates/nono-proxy/src/tls_intercept/handle.rs:1976-1988 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:1554` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (12 lines × 3) bindings/c/src/capability_set.rs:315 — bindings/c/src/capability_set.rs:315-326 | bindings/c/src/capability_set.rs:344-355 | bindings/c/src/capability_set.rs:377-388 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/c/src/capability_set.rs:315` 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 (8–10 lines × 2) · ×3
  • Duplicated block (8–10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1015 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1015-1024 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:811-818 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1015` 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. 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 (8–10 lines × 2) crates/nono-proxy/src/credential.rs:101 — crates/nono-proxy/src/credential.rs:101-108 | crates/nono-proxy/src/credential.rs:392-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/nono-proxy/src/credential.rs:99` calls `REDACTED` and `crates/nono-proxy/src/credential.rs:389` 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 (8–10 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1811 — crates/nono-proxy/src/tls_intercept/handle.rs:1811-1818 | crates/nono-proxy/src/tls_intercept/handle.rs:1964-1973 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:1811` 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.
D1 · Cyclomatic Complexity · PtyProxy · ×2
  • PtyProxy::try_accept (cyclomatic 19) crates/nono-cli/src/pty_proxy.rs:639 — PtyProxy::try_accept 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.
  • PtyProxy::filter_client_input (cyclomatic 17) crates/nono-cli/src/pty_proxy.rs:1423 — PtyProxy::filter_client_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 · SnapshotManager · ×2
  • SnapshotManager::restore_to (cyclomatic 17) crates/nono/src/undo/snapshot.rs:288 — SnapshotManager::restore_to 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.
  • SnapshotManager::walk_and_store (cyclomatic 17) crates/nono/src/undo/snapshot.rs:732 — SnapshotManager::walk_and_store 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.
D17 · Explicit Debt · TodoComment · ×2
  • TodoComment crates/nono-cli/src/exec_strategy.rs:4079 — /// TODO: Refactor `crate::url_open::validate_url` to return `UrlDenial` directly — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment crates/nono-cli/src/trust_cmd.rs:1520 — // TODO: Refactor to return build_config_uri extension if the same as workflow. — 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 · Predicate · ×2
  • Predicate::matches_linux (cognitive 17) crates/nono-cli/src/platform.rs:417 — Predicate::matches_linux has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Predicate::parse (cognitive 16) crates/nono-cli/src/platform.rs:307 — Predicate::parse has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (8 pts), if/else 4 (5 pts), loops 1 (3 pts) (nesting depth added 6). 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 · OAuthCaptureStore · ×2
  • OAuthCaptureStore::rewrite_response_body (cognitive 17) crates/nono-proxy/src/oauth_capture/rewrite.rs:238 — OAuthCaptureStore::rewrite_response_body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • OAuthCaptureStore::rewrite_form_response_body (cognitive 17) crates/nono-proxy/src/oauth_capture/rewrite.rs:385 — OAuthCaptureStore::rewrite_form_response_body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 4, boolean chains 2, match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×2
  • Edited copy of a member (34 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2426 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2426-2459 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4951-4984 — 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.
  • Edited copy of a member (34 corresponding lines) crates/nono-proxy/src/reverse.rs:1954 — crates/nono-proxy/src/reverse.rs:1954-1990 | crates/nono-proxy/src/reverse.rs:2000-2033 — 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 (45 corresponding lines) · ×2
  • Edited copy of a member (45 corresponding lines) crates/nono-cli/src/profile/mod.rs:85 — crates/nono-cli/src/profile/mod.rs:85-130 | crates/nono-cli/src/profile/mod.rs:2144-2188 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) crates/nono-cli/src/audit_session.rs:41 — crates/nono-cli/src/audit_session.rs:41-94 | crates/nono-cli/src/rollback_session.rs:40-84 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×2
  • Edited copy of a member (41 corresponding lines) crates/nono-proxy/src/audit.rs:218 — crates/nono-proxy/src/audit.rs:218-258 | crates/nono-proxy/src/audit.rs:375-427 — 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.
  • Edited copy of a member (41 corresponding lines) crates/nono-cli/src/proxy_runtime.rs:933 — crates/nono-cli/src/proxy_runtime.rs:933-973 | crates/nono-cli/src/url_open.rs:29-71 — 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 (26 corresponding lines) · ×2
  • Edited copy of a member (26 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3028 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3028-3055 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5668-5693 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) crates/nono-cli/src/profile/credential_provider.rs:451 — crates/nono-cli/src/profile/credential_provider.rs:451-478 | crates/nono-cli/src/profile/mod.rs:1500-1525 — 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 (24 corresponding lines) · ×2
  • Edited copy of a member (24 corresponding lines) crates/nono-cli/src/audit_commands.rs:312 — crates/nono-cli/src/audit_commands.rs:312-342 | crates/nono-cli/src/rollback_commands.rs:265-288 — 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) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1244 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1244-1267 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:967-990 — 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 copy of a member (29 corresponding lines) · ×2
  • Edited copy of a member (29 corresponding lines) crates/nono-cli/src/profile_cmd.rs:545 — crates/nono-cli/src/profile_cmd.rs:545-579 | crates/nono-cli/src/profile_cmd.rs:1289-1317 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) crates/nono/src/keystore.rs:800 — crates/nono/src/keystore.rs:800-835 | crates/nono/src/keystore.rs:897-925 — These two members are one piece of code written twice and then edited apart: 29 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 (25 corresponding lines) · ×2
  • Edited copy of a member (25 corresponding lines) crates/nono-cli/src/package_cmd.rs:430 — crates/nono-cli/src/package_cmd.rs:430-457 | crates/nono-cli/src/package_cmd.rs:459-483 — These two members are one piece of code written twice and then edited apart: 25 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 (25 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4191 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4191-4215 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3835-3861 — These two members are one piece of code written twice and then edited apart: 25 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 (38 lines × 2) · ×2
  • Duplicated block (38 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4280 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4280-4317 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3937-3974 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (38 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5369 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5369-5406 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4618-4655 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×2
  • Duplicated block (30 lines × 2) crates/nono-cli/src/audit_commands.rs:849 — crates/nono-cli/src/audit_commands.rs:849-878 | crates/nono-cli/src/rollback_commands.rs:879-908 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_commands.rs:849` 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: `crates/nono-cli/src/rollback_commands.rs:879` is reached only past a guard at line 802 that tests `args.all` and leaves the function early, and `crates/nono-cli/src/audit_commands.rs:849` reads `args.all` with no such check. What separates these copies is not which lines they run but which PRECONDITION they enforce, so one of them is operating on state the other one refuses. Decide which is intended BEFORE unifying them — extract the shared part and whichever copy is missing the check keeps running unchecked, and if the guard is the correct behaviour then that hole is already live.
  • Duplicated block (30 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4703 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4703-4732 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4243-4272 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:4703` 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 (25 lines × 2) · ×2
  • Duplicated block (25 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4108 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4108-4132 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3787-3811 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:4108` 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 (25 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5330 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5330-5354 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5487-5511 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (21–24 lines × 2) · ×2
  • Duplicated block (21–24 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5535 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5535-5558 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5571-5591 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:5535` 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 (21–24 lines × 2) crates/nono/src/sandbox/macos.rs:759 — crates/nono/src/sandbox/macos.rs:759-782 | crates/nono/src/sandbox/macos.rs:795-815 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/sandbox/macos.rs:759` 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 (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2684 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2684-2706 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5213-5235 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1459 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:1459-1481 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1563-1585 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/macos.rs:1459` 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 (17 lines × 3) · ×2
  • Duplicated block (17 lines × 3) crates/nono-cli/src/audit_commands.rs:867 — crates/nono-cli/src/audit_commands.rs:867-883 | crates/nono-cli/src/rollback_commands.rs:897-913 | crates/nono-cli/src/rollback_commands.rs:958-974 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/audit_commands.rs:867` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 3) crates/nono-proxy/src/tls_intercept/handle.rs:1505 — crates/nono-proxy/src/tls_intercept/handle.rs:1505-1521 | crates/nono-proxy/src/tls_intercept/handle.rs:1696-1712 | crates/nono-proxy/src/tls_intercept/handle.rs:2039-2055 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/tls_intercept/handle.rs:1505` 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 (15–17 lines × 2) · ×2
  • Duplicated block (15–17 lines × 2) crates/nono-cli/src/exec_strategy.rs:444 — crates/nono-cli/src/exec_strategy.rs:444-460 | crates/nono-cli/src/exec_strategy.rs:654-668 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:444` 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 (15–17 lines × 2) crates/nono-proxy/src/reverse.rs:2482 — crates/nono-proxy/src/reverse.rs:2482-2496 | crates/nono-proxy/src/reverse.rs:2603-2619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:2482` 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 (16 lines × 3) · ×2
  • Duplicated block (16 lines × 3) crates/nono-cli/src/registry_client.rs:175 — crates/nono-cli/src/registry_client.rs:175-190 | crates/nono-cli/src/registry_client.rs:231-246 | crates/nono-cli/src/registry_client.rs:352-367 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (16 lines × 3) crates/nono-cli/src/profile_cmd.rs:1528 — crates/nono-cli/src/profile_cmd.rs:1528-1552 | crates/nono-cli/src/profile_cmd.rs:1567-1586 | crates/nono-cli/src/profile_cmd.rs:1771-1786 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/profile_cmd.rs:1528` 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 (15–16 lines × 2) · ×2
  • Duplicated block (15–16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2592 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2592-2607 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5106-5120 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2592` 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 (15–16 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:703 — crates/nono-proxy/src/tls_intercept/handle.rs:703-717 | crates/nono-proxy/src/tls_intercept/handle.rs:734-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 `crates/nono-proxy/src/tls_intercept/handle.rs:703` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×2
  • Duplicated block (14–16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4688 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4688-4701 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4226-4241 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:4688` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–16 lines × 2) crates/nono-cli/src/wiring.rs:1190 — crates/nono-cli/src/wiring.rs:1190-1203 | crates/nono-cli/src/wiring.rs:1224-1239 — 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.
D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×2
  • Duplicated block (13–15 lines × 2) crates/nono-cli/src/rollback_commands.rs:416 — crates/nono-cli/src/rollback_commands.rs:416-428 | crates/nono-cli/src/rollback_commands.rs:473-487 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/rollback_commands.rs:473` 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–15 lines × 2) crates/nono/src/sandbox/linux.rs:1032 — crates/nono/src/sandbox/linux.rs:1032-1044 | crates/nono/src/sandbox/linux.rs:1192-1206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/sandbox/linux.rs:1192` 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 (11–14 lines × 2) · ×2
  • Duplicated block (11–14 lines × 2) crates/nono-cli/src/exec_strategy.rs:4192 — crates/nono-cli/src/exec_strategy.rs:4192-4202 | crates/nono-cli/src/exec_strategy.rs:4235-4248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:4192` 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. 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–14 lines × 2) crates/nono-proxy/src/oauth2.rs:256 — crates/nono-proxy/src/oauth2.rs:256-269 | crates/nono-proxy/src/oauth2.rs:626-636 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/oauth2.rs:256` 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 (13 lines × 3) · ×2
  • Duplicated block (13 lines × 3) crates/nono-cli/src/trust_keystore.rs:199 — crates/nono-cli/src/trust_keystore.rs:199-211 | crates/nono-cli/src/trust_keystore.rs:230-242 | crates/nono-cli/src/trust_keystore.rs:287-299 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_keystore.rs:199` 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 (13 lines × 3) crates/nono-proxy/src/reverse.rs:727 — crates/nono-proxy/src/reverse.rs:727-739 | crates/nono-proxy/src/reverse.rs:755-768 | crates/nono-proxy/src/reverse.rs:777-790 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:727` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2
  • Duplicated block (11–12 lines × 2) crates/nono-cli/src/profile_cmd.rs:1588 — crates/nono-cli/src/profile_cmd.rs:1588-1599 | crates/nono-cli/src/profile_cmd.rs:1720-1730 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/profile_cmd.rs:1588` 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–12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4926 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4926-4937 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4462-4472 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×2
  • Duplicated block (11 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2831 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2831-2841 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2869-2879 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5366-5376 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5404-5414 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 4) crates/nono-proxy/src/tls_intercept/handle.rs:2166 — crates/nono-proxy/src/tls_intercept/handle.rs:2166-2176 | crates/nono-proxy/src/tls_intercept/handle.rs:2226-2236 | crates/nono-proxy/src/tls_intercept/handle.rs:2247-2259 | crates/nono-proxy/src/tls_intercept/handle.rs:2273-2283 — 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 `crates/nono-proxy/src/tls_intercept/handle.rs:2166` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) crates/nono-proxy/src/tls_intercept/handle.rs:1404 — crates/nono-proxy/src/tls_intercept/handle.rs:1404-1414 | crates/nono-proxy/src/tls_intercept/handle.rs:2000-2010 | crates/nono-proxy/src/tls_intercept/handle.rs:2145-2155 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (11 lines × 3) crates/nono-cli/src/exec_strategy.rs:1188 — crates/nono-cli/src/exec_strategy.rs:1188-1199 | crates/nono-cli/src/exec_strategy.rs:1268-1278 | crates/nono-cli/src/exec_strategy.rs:1299-1313 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:1188` 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 (9–10 lines × 2) · ×2
  • Duplicated block (9–10 lines × 2) crates/nono-cli/src/query_ext.rs:445 — crates/nono-cli/src/query_ext.rs:445-454 | crates/nono-cli/src/query_ext.rs:513-521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/query_ext.rs:445` 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–10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4676 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4676-4685 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:4999-5007 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) crates/nono-cli/src/profile_cmd.rs:1553 — crates/nono-cli/src/profile_cmd.rs:1553-1561 | crates/nono-cli/src/profile_cmd.rs:1587-1595 | crates/nono-cli/src/profile_cmd.rs:1787-1795 | crates/nono-cli/src/profile_cmd.rs:1817-1825 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1507 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1507-1515 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1636-1644 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1237-1245 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1360-1368 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1507` 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 (11 lines × 5) · ×2
  • Duplicated block (11 lines × 5) crates/nono-cli/src/exec_strategy.rs:1188 — crates/nono-cli/src/exec_strategy.rs:1188-1198 | crates/nono-cli/src/exec_strategy.rs:1206-1216 | crates/nono-cli/src/exec_strategy.rs:1251-1264 | crates/nono-cli/src/exec_strategy.rs:1268-1278 | crates/nono-cli/src/exec_strategy.rs:1299-1312 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:1188` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 5) crates/nono-cli/src/trust_scan.rs:905 — crates/nono-cli/src/trust_scan.rs:905-915 | crates/nono-cli/src/trust_scan.rs:919-929 | crates/nono-cli/src/trust_scan.rs:944-954 | crates/nono-cli/src/trust_scan.rs:966-976 | crates/nono-cli/src/trust_scan.rs:997-1007 — all 5 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D1 · Cyclomatic Complexity · CredentialStore · ×1
  • CredentialStore::load_with_registry (cyclomatic 26) crates/nono-proxy/src/credential.rs:286 — CredentialStore::load_with_registry 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 · RouteStore · ×1
  • RouteStore::load_with_registry (cyclomatic 22) crates/nono-proxy/src/route.rs:252 — RouteStore::load_with_registry has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TerminalApproval · ×1
  • TerminalApproval::prompt (cyclomatic 21) crates/nono-cli/src/terminal_approval.rs:92 — TerminalApproval::prompt 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.
D1 · Cyclomatic Complexity · Predicate · ×1
  • Predicate::parse (cyclomatic 20) crates/nono-cli/src/platform.rs:307 — Predicate::parse 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 · ProxyCredentialCaptureBackend · ×1
  • ProxyCredentialCaptureBackend::run_capture_command (cyclomatic 20) crates/nono-cli/src/proxy_runtime.rs:390 — ProxyCredentialCaptureBackend::run_capture_command has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DetachMatcher · ×1
  • DetachMatcher::push (cyclomatic 16) crates/nono-cli/src/connect_client.rs:1718 — DetachMatcher::push 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 · EffectiveDenyPolicy · ×1
  • EffectiveDenyPolicy::keychain_child_deny_rules (cyclomatic 16) crates/nono-cli/src/policy.rs:1232 — EffectiveDenyPolicy::keychain_child_deny_rules 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 · DaemonPidLineage · ×1
  • DaemonPidLineage::attribute_with_negative_ttl (cyclomatic 16) crates/nono-cli/src/tool-sandbox/platform/macos.rs:2189 — DaemonPidLineage::attribute_with_negative_ttl 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.
D2 · Cognitive Complexity · CredentialStore · ×1
  • CredentialStore::load_with_registry (cognitive 65) crates/nono-proxy/src/credential.rs:286 — CredentialStore::load_with_registry has cognitive complexity 65 (threshold 15). Drivers by points: match/switch 11 (34 pts), if/else 11 (30 pts), loops 1 (nesting depth added 42). 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 · DetachMatcher · ×1
  • DetachMatcher::push (cognitive 37) crates/nono-cli/src/connect_client.rs:1718 — DetachMatcher::push has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (32 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RouteStore · ×1
  • RouteStore::load_with_registry (cognitive 37) crates/nono-proxy/src/route.rs:252 — RouteStore::load_with_registry has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 4 (9 pts), boolean chains 7, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EffectiveDenyPolicy · ×1
  • EffectiveDenyPolicy::keychain_child_deny_rules (cognitive 29) crates/nono-cli/src/policy.rs:1232 — EffectiveDenyPolicy::keychain_child_deny_rules has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 6 (10 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · TerminalApproval · ×1
  • TerminalApproval::prompt (cognitive 25) crates/nono-cli/src/terminal_approval.rs:92 — TerminalApproval::prompt has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (20 pts), match/switch 2 (3 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProxyCredentialCaptureBackend · ×1
  • ProxyCredentialCaptureBackend::run_capture_command (cognitive 22) crates/nono-cli/src/proxy_runtime.rs:390 — ProxyCredentialCaptureBackend::run_capture_command has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (14 pts), match/switch 2 (4 pts), loops 3, boolean chains 1 (nesting depth added 3). 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 · DaemonPidLineage · ×1
  • DaemonPidLineage::attribute_with_negative_ttl (cognitive 21) crates/nono-cli/src/tool-sandbox/platform/macos.rs:2189 — DaemonPidLineage::attribute_with_negative_ttl has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 5, 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 · ProxyHandle · ×1
  • ProxyHandle::route_diagnostics (cognitive 19) crates/nono-proxy/src/server.rs:481 — ProxyHandle::route_diagnostics has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, loops 2, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SandboxState · ×1
  • SandboxState::to_caps (cognitive 18) crates/nono/src/state.rs:103 — SandboxState::to_caps has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 3 (6 pts), loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Renderer · ×1
  • Renderer::sample (cognitive 18) crates/nono-cli/src/terminal_capture/transcript.rs:103 — Renderer::sample has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TokenBroker · ×1
  • TokenBroker::scan_and_reissue (cognitive 18) crates/nono-cli/src/tool-sandbox/token_broker.rs:273 — TokenBroker::scan_and_reissue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SetupRunner · ×1
  • SetupRunner::test_linux_landlock (cognitive 16) crates/nono-cli/src/setup.rs:164 — SetupRunner::test_linux_landlock has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 1 (2 pts), boolean chains 1, loops 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.
D2 · Cognitive Complexity · Writer · ×1
  • Writer::run (cognitive 16) crates/nono-cli/src/terminal_capture/writer.rs:261 — Writer::run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), match/switch 3 (7 pts), loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×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 (597 shared lines) · ×1
  • Near-duplicate member pair (597 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1275 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1275-2062 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:998-1812 — These two members are variants of one another: 597 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 · Near-duplicate member pair (54 shared lines) · ×1
  • Near-duplicate member pair (54 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4664 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4664-4732 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4200-4272 — These two members are variants of one another: 54 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 · Near-duplicate member pair (38 shared lines) · ×1
  • Near-duplicate member pair (38 shared lines) crates/nono-proxy/src/oauth2.rs:251 — crates/nono-proxy/src/oauth2.rs:251-395 | crates/nono-proxy/src/oauth2.rs:606-731 — These two members are variants of one another: 38 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 · Near-duplicate member pair (37 shared lines) · ×1
  • Near-duplicate member pair (37 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:268 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:268-435 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:286-407 — These two members are variants of one another: 37 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 · Near-duplicate member pair (27 shared lines) · ×1
  • Near-duplicate member pair (27 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2265 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2265-2317 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4785-4829 — These two members are variants of one another: 27 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 (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) crates/nono-cli/src/command_policy.rs:1174 — crates/nono-cli/src/command_policy.rs:1174-1190 | crates/nono-cli/src/command_policy.rs:3763-3770 | crates/nono-cli/src/command_policy.rs:3775-3782 | crates/nono-cli/src/command_policy.rs:3787-3794 | crates/nono-cli/src/profile/mod.rs:4126-4413 | crates/nono-cli/src/profile/mod.rs:4418-4425 — These 6 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 6 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 6 times.
D4 · Code Duplication · Edited copy of a member (104 corresponding lines) · ×1
  • Edited copy of a member (104 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4455 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4455-4561 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3993-4096 — These two members are one piece of code written twice and then edited apart: 104 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 (86 corresponding lines) · ×1
  • Edited copy of a member (86 corresponding lines) crates/nono-cli/src/capability_ext.rs:586 — crates/nono-cli/src/capability_ext.rs:586-690 | crates/nono-cli/src/capability_ext.rs:1233-1318 — These two members are one piece of code written twice and then edited apart: 86 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 (77 corresponding lines) · ×1
  • Edited copy of a member (77 corresponding lines) crates/nono/src/capability.rs:1792 — crates/nono/src/capability.rs:1792-1930 | crates/nono/src/capability.rs:1949-2025 — These two members are one piece of code written twice and then edited apart: 77 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 (67 corresponding lines) · ×1
  • Edited copy of a member (67 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:779 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:779-859 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:667-733 — These two members are one piece of code written twice and then edited apart: 67 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 (75 corresponding lines) · ×1
  • Edited copy of a member (75 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1133 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1133-1208 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:841-915 — These two members are one piece of code written twice and then edited apart: 75 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 (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4922 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4922-4980 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4461-4512 — These two members are one piece of code written twice and then edited apart: 52 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 (74 corresponding lines) · ×1
  • Edited copy of a member (74 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3357 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:3357-3438 | crates/nono/src/sandbox/linux.rs:1563-1636 — These two members are one piece of code written twice and then edited apart: 74 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 (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) crates/nono-cli/src/profile_cmd.rs:2908 — crates/nono-cli/src/profile_cmd.rs:2908-2958 | crates/nono-cli/src/profile_save_runtime.rs:750-798 — These two members are one piece of code written twice and then edited apart: 49 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 (51 corresponding lines) · ×1
  • Edited copy of a member (51 corresponding lines) crates/nono/src/keystore.rs:1253 — crates/nono/src/keystore.rs:1253-1303 | crates/nono/src/keystore.rs:1505-1566 — These two members are one piece of code written twice and then edited apart: 51 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 (54 corresponding lines) · ×1
  • Edited copy of a member (54 corresponding lines) crates/nono/src/undo/object_store.rs:184 — crates/nono/src/undo/object_store.rs:184-237 | crates/nono/src/undo/object_store.rs:246-310 — These two members are one piece of code written twice and then edited apart: 54 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) crates/nono-proxy/src/tls_intercept/h2_forward.rs:625 — crates/nono-proxy/src/tls_intercept/h2_forward.rs:625-659 | crates/nono-proxy/src/tls_intercept/h2_forward.rs:662-696 — 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 copy of a member (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) crates/nono/src/trust/bundle.rs:308 — crates/nono/src/trust/bundle.rs:308-350 | crates/nono/src/trust/bundle.rs:542-598 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) crates/nono-cli/src/output.rs:917 — crates/nono-cli/src/output.rs:917-972 | crates/nono-cli/src/output.rs:983-1026 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5530 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5530-5562 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5560-5596 — 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 copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) crates/nono-proxy/src/oauth2.rs:188 — crates/nono-proxy/src/oauth2.rs:188-224 | crates/nono-proxy/src/oauth2.rs:552-597 — These two members are one piece of code written twice and then edited apart: 37 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 (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) crates/nono/src/trust/signing.rs:102 — crates/nono/src/trust/signing.rs:102-123 | crates/nono/src/trust/signing.rs:190-211 — 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 (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) crates/nono-cli/src/wiring.rs:925 — crates/nono-cli/src/wiring.rs:925-954 | crates/nono-cli/src/wiring.rs:1432-1461 — These two members are one piece of code written twice and then edited apart: 30 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, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) crates/nono-cli/src/connect_client.rs:667 — crates/nono-cli/src/connect_client.rs:667-690 | crates/nono-cli/src/platform_oauth/client.rs:184-205 | crates/nono-cli/src/platform_oauth/client.rs:670-686 — 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 (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) crates/nono-cli/src/tool-sandbox/platform/macos.rs:3547 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:3547-3566 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3571-3592 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 28+ corresponding lines) crates/nono-cli/src/capability_ext.rs:363 — crates/nono-cli/src/capability_ext.rs:363-390 | crates/nono/src/capability.rs:157-185 | crates/nono/src/capability.rs:195-223 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 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) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:480 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:480-498 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3994-4011 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3406-3420 — 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 · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) crates/nono-cli/src/config/user.rs:323 — crates/nono-cli/src/config/user.rs:323-339 | crates/nono-cli/src/config/version.rs:39-53 | crates/nono-cli/src/package.rs:331-344 — 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 copies of one member (4 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 11+ corresponding lines) crates/nono/src/undo/snapshot.rs:469 — crates/nono/src/undo/snapshot.rs:469-480 | crates/nono/src/undo/snapshot.rs:528-542 | crates/nono/src/undo/snapshot.rs:547-557 | crates/nono/src/undo/snapshot.rs:562-575 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) bindings/c/src/capability_set.rs:313 — bindings/c/src/capability_set.rs:313-330 | bindings/c/src/capability_set.rs:342-359 | bindings/c/src/capability_set.rs:375-394 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 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) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) crates/nono-cli/src/session.rs:193 — crates/nono-cli/src/session.rs:193-208 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:2614-2635 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:2687-2704 — 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, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) bindings/c/src/fs_capability.rs:37 — bindings/c/src/fs_capability.rs:37-46 | bindings/c/src/fs_capability.rs:60-69 | bindings/c/src/fs_capability.rs:168-180 — 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, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) crates/nono-cli/src/exec_strategy/clone_files.rs:170 — crates/nono-cli/src/exec_strategy/clone_files.rs:170-181 | crates/nono-cli/src/exec_strategy/clone_files.rs:185-197 | crates/nono/src/sandbox/linux.rs:99-117 — 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 (5 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 14+ corresponding lines) crates/nono-cli/src/platform_client.rs:753 — crates/nono-cli/src/platform_client.rs:753-766 | crates/nono-cli/src/platform_oauth/client.rs:766-779 | crates/nono-cli/src/rollback_runtime.rs:225-238 | crates/nono-cli/src/session.rs:606-620 | crates/nono/src/audit.rs:1019-1032 — 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 copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) crates/nono-cli/src/tool-sandbox/env.rs:229 — crates/nono-cli/src/tool-sandbox/env.rs:229-232 | crates/nono-cli/src/tool-sandbox/policy.rs:380-383 — 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 · Edited copy of a member (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) crates/nono-cli/src/terminal_capture/recording.rs:328 — crates/nono-cli/src/terminal_capture/recording.rs:328-332 | crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:25-29 — These two members are one piece of code written twice and then edited apart: 5 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 (61 lines × 2) · ×1
  • Duplicated block (61 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1148 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1148-1208 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:855-915 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1148` 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 (57 lines × 2) · ×1
  • Duplicated block (57 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2856 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2856-2912 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5391-5447 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (64–65 lines × 2) · ×1
  • Duplicated block (64–65 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1748 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1748-1811 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1477-1541 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1748` 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 (47 lines × 2) · ×1
  • Duplicated block (47 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4784 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4784-4830 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4322-4368 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (44 lines × 2) · ×1
  • Duplicated block (44 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4021 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4021-4064 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3700-3743 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (38–40 lines × 2) · ×1
  • Duplicated block (38–40 lines × 2) crates/nono-cli/src/audit_commands.rs:1149 — crates/nono-cli/src/audit_commands.rs:1149-1186 | crates/nono-cli/src/terminal_approval.rs:321-360 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (39–40 lines × 2) · ×1
  • Duplicated block (39–40 lines × 2) crates/nono-cli/src/exec_strategy.rs:3672 — crates/nono-cli/src/exec_strategy.rs:3672-3711 | crates/nono-cli/src/exec_strategy.rs:3738-3776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:3672` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (33–36 lines × 2) · ×1
  • Duplicated block (33–36 lines × 2) crates/nono-cli/src/audit_commands.rs:246 — crates/nono-cli/src/audit_commands.rs:246-278 | crates/nono-cli/src/rollback_commands.rs:1000-1035 — before extracting anything, compare `crates/nono-cli/src/audit_commands.rs` and `crates/nono-cli/src/rollback_commands.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (34–35 lines × 2) · ×1
  • Duplicated block (34–35 lines × 2) crates/nono-cli/src/query_ext.rs:378 — crates/nono-cli/src/query_ext.rs:378-412 | crates/nono-cli/src/query_ext.rs:459-492 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/query_ext.rs:378` 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 (30–34 lines × 2) · ×1
  • Duplicated block (30–34 lines × 2) crates/nono-cli/src/profile_save_runtime.rs:1077 — crates/nono-cli/src/profile_save_runtime.rs:1077-1110 | crates/nono-cli/src/terminal_prompt.rs:155-184 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5440 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5440-5473 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4689-4722 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (31–34 lines × 2) · ×1
  • Duplicated block (31–34 lines × 2) crates/nono-proxy/src/server.rs:1723 — crates/nono-proxy/src/server.rs:1723-1756 | crates/nono-proxy/src/server.rs:1875-1905 — 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.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5476 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5476-5507 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4725-4756 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (3–30 lines × 4) · ×1
  • Duplicated block (3–30 lines × 4) crates/nono-cli/src/profile_cmd.rs:1522 — crates/nono-cli/src/profile_cmd.rs:1522-1551 | crates/nono-cli/src/profile_cmd.rs:1765-1785 | crates/nono-cli/src/profile_cmd.rs:1900-1902 | crates/nono-cli/src/profile_cmd.rs:1929-1931 — 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 `crates/nono-cli/src/profile_cmd.rs:1522` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (182 lines × 2) · ×1
  • Duplicated block (182 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1322 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1322-1503 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1052-1233 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1322` 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 (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5409 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:5409-5437 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4658-4686 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) crates/nono-proxy/src/reverse.rs:346 — crates/nono-proxy/src/reverse.rs:346-373 | crates/nono-proxy/src/reverse.rs:375-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:346` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×1
  • Duplicated block (24–25 lines × 2) crates/nono-cli/src/session.rs:355 — crates/nono-cli/src/session.rs:355-379 | crates/nono-cli/src/session.rs:407-430 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/session.rs:355` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (52–58 lines × 2) · ×1
  • Duplicated block (52–58 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1505 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1505-1556 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1235-1292 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1505` 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.
D4 · Code Duplication · Duplicated block (19–24 lines × 2) · ×1
  • Duplicated block (19–24 lines × 2) crates/nono-cli/src/wiring.rs:1156 — crates/nono-cli/src/wiring.rs:1156-1179 | crates/nono-cli/src/wiring.rs:1474-1492 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/wiring.rs:1156` 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 (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1542 — crates/nono-proxy/src/tls_intercept/handle.rs:1542-1565 | crates/nono-proxy/src/tls_intercept/handle.rs:1567-1590 — 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.
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1697 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1697-1733 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1420-1456 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1697` 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 (17–21 lines × 2) · ×1
  • Duplicated block (17–21 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1911 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1911-1927 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1647-1667 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1911` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18–21 lines × 2) · ×1
  • Duplicated block (18–21 lines × 2) crates/nono-cli/src/trust_cmd.rs:917 — crates/nono-cli/src/trust_cmd.rs:917-937 | crates/nono-cli/src/trust_cmd.rs:1043-1060 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_cmd.rs:917` 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–21 lines × 2) · ×1
  • Duplicated block (12–21 lines × 2) crates/nono-proxy/src/oauth2.rs:299 — crates/nono-proxy/src/oauth2.rs:299-319 | crates/nono-proxy/src/oauth2.rs:658-669 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/oauth2.rs:299` 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 (18–19 lines × 4) · ×1
  • Duplicated block (18–19 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1727 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1727-1744 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1826-1843 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1899-1916 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1987-2005 — 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 `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1727` 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 (18–19 lines × 2) · ×1
  • Duplicated block (18–19 lines × 2) crates/nono-proxy/src/reverse.rs:540 — crates/nono-proxy/src/reverse.rs:540-557 | crates/nono-proxy/src/reverse.rs:831-849 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:540` 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 (17–19 lines × 2) · ×1
  • Duplicated block (17–19 lines × 2) crates/nono/src/undo/exclusion.rs:144 — crates/nono/src/undo/exclusion.rs:144-162 | crates/nono/src/undo/exclusion.rs:181-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/undo/exclusion.rs:144` 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 lines × 4) · ×1
  • Duplicated block (18 lines × 4) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1450 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:1450-1467 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1554-1571 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1635-1652 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1731-1748 — 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 `crates/nono-cli/src/tool-sandbox/platform/macos.rs:1450` 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–17 lines × 3) · ×1
  • Duplicated block (15–17 lines × 3) crates/nono-proxy/src/server.rs:1737 — crates/nono-proxy/src/server.rs:1737-1751 | crates/nono-proxy/src/server.rs:1886-1900 | crates/nono-proxy/src/tls_intercept/handle.rs:410-426 — there are 3 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 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/server.rs:1737` 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 (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1962 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1962-1977 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2041-2056 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1705-1720 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1791-1806 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1962` 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 (15–16 lines × 4) · ×1
  • Duplicated block (15–16 lines × 4) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1532 — crates/nono-cli/src/tool-sandbox/platform/macos.rs:1532-1546 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1613-1627 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1710-1724 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1796-1811 — 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 `crates/nono-cli/src/tool-sandbox/platform/macos.rs:1796` 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–16 lines × 3) · ×1
  • Duplicated block (15–16 lines × 3) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1802 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1802-1816 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1967-1981 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2046-2061 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2046` 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 (50–52 lines × 2) · ×1
  • Duplicated block (50–52 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1634 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1634-1685 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1358-1407 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1634` 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 (65–67 lines × 2) · ×1
  • Duplicated block (65–67 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1929 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1929-1993 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1671-1737 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1929` 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 (32–33 lines × 2) · ×1
  • Duplicated block (32–33 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2008 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:2008-2039 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1757-1789 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:2008` 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–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) crates/nono-proxy/src/reverse.rs:500 — crates/nono-proxy/src/reverse.rs:500-511 | crates/nono-proxy/src/reverse.rs:2857-2870 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:500` 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. 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 (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) crates/nono/src/capability.rs:163 — crates/nono/src/capability.rs:163-176 | crates/nono/src/capability.rs:535-547 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/capability.rs:163` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (13 lines × 8) · ×1
  • Duplicated block (13 lines × 8) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1725 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1725-1737 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1824-1836 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1897-1909 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1985-1997 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1448-1460 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1552-1564 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1633-1645 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1729-1741 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1725` 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 (12–13 lines × 4) · ×1
  • Duplicated block (12–13 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1932 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1932-1943 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2010-2022 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1675-1686 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1760-1772 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1932` 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 (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) crates/nono/src/keystore.rs:1135 — crates/nono/src/keystore.rs:1135-1146 | crates/nono/src/keystore.rs:1607-1619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:1135` 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 (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1375 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1375-1386 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1394-1405 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1105-1116 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1124-1135 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1375` 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–12 lines × 3) · ×1
  • Duplicated block (8–12 lines × 3) crates/nono-proxy/src/reverse.rs:2486 — crates/nono-proxy/src/reverse.rs:2486-2495 | crates/nono-proxy/src/reverse.rs:2607-2618 | crates/nono-proxy/src/reverse.rs:2751-2758 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-proxy/src/reverse.rs:2486` 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 (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) crates/nono-cli/src/package_cmd.rs:435 — crates/nono-cli/src/package_cmd.rs:435-445 | crates/nono-cli/src/package_cmd.rs:464-473 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/package_cmd.rs:435` 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, `crates/nono-cli/src/package_cmd.rs:447` calls `clone` and `crates/nono-cli/src/package_cmd.rs:475` 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.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) crates/nono-cli/src/trust_keystore.rs:204 — crates/nono-cli/src/trust_keystore.rs:204-213 | crates/nono-cli/src/trust_keystore.rs:235-244 | crates/nono-cli/src/trust_keystore.rs:292-301 | crates/nono-cli/src/trust_keystore.rs:339-348 — 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 `crates/nono-cli/src/trust_keystore.rs:204` 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 (6–10 lines × 2) · ×1
  • Duplicated block (6–10 lines × 2) crates/nono/src/keystore.rs:1067 — crates/nono/src/keystore.rs:1067-1076 | crates/nono/src/keystore.rs:1096-1101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono/src/keystore.rs:1067` 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 (8–9 lines × 4) · ×1
  • Duplicated block (8–9 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1521 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:1521-1528 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1660-1668 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1251-1258 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1383-1390 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:1521` 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 (7–9 lines × 2) · ×1
  • Duplicated block (7–9 lines × 2) crates/nono-cli/src/trust_cmd.rs:1187 — crates/nono-cli/src/trust_cmd.rs:1187-1193 | crates/nono-cli/src/trust_cmd.rs:1248-1256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/trust_cmd.rs:1248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:959 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:959-965 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:971-977 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:788-794 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:800-806 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:959` 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 (3–5 lines × 6) · ×1
  • Duplicated block (3–5 lines × 6) crates/nono-cli/src/command_policy.rs:1183 — crates/nono-cli/src/command_policy.rs:1183-1185 | crates/nono-cli/src/command_policy.rs:3766-3770 | crates/nono-cli/src/command_policy.rs:3778-3782 | crates/nono-cli/src/command_policy.rs:3790-3794 | crates/nono-cli/src/profile/mod.rs:4324-4326 | crates/nono-cli/src/profile/mod.rs:4421-4425 — there are 6 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/command_policy.rs:3766` 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.
D4 · Code Duplication · Duplicated block (30–31 lines × 2) · ×1
  • Duplicated block (30–31 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4528 — crates/nono-cli/src/tool-sandbox/platform/linux.rs:4528-4557 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4061-4091 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono-cli/src/tool-sandbox/platform/macos.rs` as WHOLE FILES: this scan already matched 106 separate duplicated blocks between them, totalling at least 2088 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/tool-sandbox/platform/linux.rs:4528` 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 (11 lines × 7) · ×1
  • Duplicated block (11 lines × 7) crates/nono-cli/src/exec_strategy.rs:1067 — crates/nono-cli/src/exec_strategy.rs:1067-1079 | crates/nono-cli/src/exec_strategy.rs:1149-1161 | crates/nono-cli/src/exec_strategy.rs:1187-1197 | crates/nono-cli/src/exec_strategy.rs:1205-1215 | crates/nono-cli/src/exec_strategy.rs:1251-1263 | crates/nono-cli/src/exec_strategy.rs:1267-1277 | crates/nono-cli/src/exec_strategy.rs:1299-1311 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/nono-cli/src/exec_strategy.rs:1067` 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 × 3) · ×1
  • Duplicated block (9 lines × 3) crates/nono-cli/src/connect_client.rs:680 — crates/nono-cli/src/connect_client.rs:680-688 | crates/nono-cli/src/connect_client.rs:778-786 | crates/nono-cli/src/platform_oauth/client.rs:194-203 — there are 3 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 3 sites; resolving a subset leaves the remainder to drift apart. 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.
D4 · Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 25+ corresponding lines) crates/nono/src/sandbox/linux.rs:2779 — crates/nono/src/sandbox/linux.rs:2779-2807 | crates/nono/src/sandbox/linux.rs:2817-2843 | crates/nono/src/sandbox/linux.rs:2850-2874 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 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 (3–5 lines × 4) · ×1
  • Duplicated block (3–5 lines × 4) crates/nono/src/sandbox/linux.rs:2594 — crates/nono/src/sandbox/linux.rs:2594-2598 | crates/nono/src/sandbox/linux.rs:2705-2709 | crates/nono/src/sandbox/linux.rs:3837-3839 | crates/nono/src/sandbox/linux.rs:3988-3990 — 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.
D4 · Code Duplication · Duplicated block (88 lines × 2) · ×1
  • Duplicated block (88 lines × 2) tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:46 — tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:46-133 | tool-sandbox-examples/kubernetes/make-proxy-kubeconfig.py:46-133 — `tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py` and `tool-sandbox-examples/kubernetes/make-proxy-kubeconfig.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 98 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: nono — nono: abstractness 0.01, instability 0.00, distance 0.99 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: CapabilitySet (LCOM4 12) crates/nono/src/capability.rs:952 — CapabilitySet's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
S1 · Web-Security Posture · Weak hash algorithm · ×1
  • Weak hash algorithm crates/nono-proxy/src/tls_intercept/websocket.rs:22 — 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.
Minor — 104 finding(s)
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:148 — `warn!` at line 148 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:172 — `warn!` at line 172 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:193 — `warn!` 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: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:276 — `warn!` at line 276 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:304 — `warn!` at line 304 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:321 — `info!` at line 321 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:341 — `info!` at line 341 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:441 — `info!` at line 441 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:470 — `info!` at line 470 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/audit.rs:531 — `info!` at line 531 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:232 — `debug!` at line 232 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:240 — `debug!` at line 240 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:244 — `debug!` at line 244 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:338 — `debug!` at line 338 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:576 — `warn!` at line 576 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:582 — `warn!` at line 582 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:591 — `warn!` at line 591 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:630 — `warn!` at line 630 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:674 — `debug!` at line 674 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/connect.rs:678 — `debug!` at line 678 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/credential.rs:343 — `debug!` at line 343 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/credential.rs:359 — `warn!` at line 359 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/credential.rs:450 — `debug!` at line 450 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/credential.rs:473 — `warn!` at line 473 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
  • Interpolated log message defeats structured logging crates/nono-proxy/src/credential.rs:520 — `warn!` at line 520 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`.
  • + 15 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×33
  • Duplicated predicate tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:33 — `self.headers.get("Content-Length", "0") or "0"` appears character-identically in 2 files — tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py, tool-sandbox-examples/kubernetes/https-front-proxy.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:2747 — `!allow_writable_path && outer_caps_grant_file_write(outer_caps, path)` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:2759 — `!allow_writable_path && outer_caps_grant_write(outer_caps, parent)` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/isolation.rs:63 — `!caps.localhost_ports().is_empty() || !caps.localhost_port_ranges().is_empty()` appears character-identically in 2 files — crates/nono-cli/src/isolation.rs, crates/nono-cli/src/output.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/network_policy.rs:462 — `!endpoints.is_empty() && endpoint_policy.is_some()` appears character-identically in 2 files — crates/nono-cli/src/network_policy.rs, crates/nono-cli/src/profile/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/connect_client.rs:155 — `!io::stdin().is_terminal() || !io::stdout().is_terminal()` appears character-identically in 3 files — crates/nono-cli/src/connect_client.rs, crates/nono-cli/src/tenant_selector.rs, crates/nono-cli/src/terminal_selector.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/command_policy.rs:3194 — `!network.tcp_connect_ports.is_empty() || !network.tcp_bind_ports.is_empty()` appears character-identically in 3 files — crates/nono-cli/src/command_policy.rs, crates/nono-cli/src/profile_runtime.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:550 — `!original_program.contains('/') && self.inner.shims_by_command.contains_key(original_program)` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/connect_client.rs:680 — `!url.username().is_empty() || url.password().is_some() || url.query().is_some() || url.fragment().is_some()` appears character-identically in 2 files — crates/nono-cli/src/connect_client.rs, crates/nono-cli/src/platform_oauth/client.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:2658 — `allowed.contains(name) || config.commands.contains_key(name)` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/proxy_runtime.rs:1525 — `args.block_net || (prepared.profile_network_block && !args.allow_net)` appears character-identically in 2 files — crates/nono-cli/src/proxy_runtime.rs, crates/nono-cli/src/sandbox_prepare.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/command_policy.rs:2934 — `aws.profile && (profile.is_empty() || profile.contains(char::is_whitespace))` appears character-identically in 2 files — crates/nono-cli/src/command_policy.rs, crates/nono-cli/src/profile/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:5375 — `cap.original.is_absolute() && cap.original != cap.resolved` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:5334 — `command.dev == id.dev && command.ino == id.ino` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:2685 — `config.allow_writable_executables || config .commands .get(command_name) .is_some_and(command_allows_writable_executable)` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:2595 — `dir.as_os_str().is_empty() || !dir.exists()` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/command_runtime.rs:494 — `err.to_string().contains("--block-net") && err.to_string().contains("--upstream-proxy")` appears character-identically in 3 files — crates/nono-cli/src/command_runtime.rs, crates/nono-cli/src/launch_runtime.rs, crates/nono-cli/src/sandbox_prepare.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-proxy/src/route.rs:788 — `has_endpoint_only_route && !endpoint_authorized` appears character-identically in 3 files — crates/nono-proxy/src/route.rs, crates/nono-proxy/src/server.rs, crates/nono-proxy/src/tls_intercept/handle.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/exec_strategy.rs:4096 — `host == "localhost" || host == "127.0.0.1" || host == "::1"` appears character-identically in 2 files — crates/nono-cli/src/exec_strategy.rs, crates/nono-cli/src/url_open.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/exec_strategy/clone_files/tests.rs:1060 — `libc::WIFEXITED(status) && libc::WEXITSTATUS(status) == 0` appears character-identically in 2 files — crates/nono-cli/src/exec_strategy/clone_files/tests.rs, crates/nono-cli/src/setup.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:5290 — `metadata.dev() != binary.dev || metadata.ino() != binary.ino` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/proxy_command.rs:335 — `network_profile.is_some() || !plain_entries.is_empty() || !deny_domain.is_empty()` appears character-identically in 2 files — crates/nono-cli/src/proxy_command.rs, crates/nono-cli/src/proxy_runtime.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-proxy/src/server.rs:7369 — `nonce == self.nonce && consumer == self.admitted_consumer` appears character-identically in 2 files — crates/nono-proxy/src/server.rs, crates/nono-proxy/src/tls_intercept/handle.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/profile/credential_provider.rs:452 — `origin.trim().is_empty() || origin.contains('\0')` appears character-identically in 2 files — crates/nono-cli/src/profile/credential_provider.rs, crates/nono-cli/src/profile/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/nono-cli/src/tool-sandbox/platform/linux.rs:4122 — `path.parent() && !crate::query_ext::is_sensitive_root(parent)` appears character-identically in 2 files — crates/nono-cli/src/tool-sandbox/platform/linux.rs, crates/nono-cli/src/tool-sandbox/platform/macos.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.
  • + 8 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default on Err · ×10
  • Silent fallback default on Err crates/nono-cli/src/pack_update_hint.rs:143 — `collect_profile_packs` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/platform.rs:100 — `detect_linux` turns every `Err` into `LinuxInfo::default()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/sandbox_prepare.rs:305 — `claude_keychain_account_name` turns every `Err` into `"claude-code-user".to_string()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/session_commands.rs:227 — `format_uptime` turns every `Err` into `"-".to_string()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:259 — `run_fsmonitor_socket` turns every `Err` into `Ok(vec![])` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:310 — `run_toplevel` turns every `Err` into `Ok(vec![])` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:355 — `run_common_dir` turns every `Err` into `Ok(vec![])` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/tool-sandbox/dynamic_providers.rs:468 — `run_with_path` turns every `Err` into `Ok(GitConfigPaths::default())` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/tool-sandbox/platform/macos.rs:2838 — `signal_children_in_pgroup_for_state` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/nono-cli/src/update_check.rs:354 — `detect_install_source` turns every `Err` into `"unknown".to_string()` — 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.
X9 · Subsumed condition operand · Subsumed condition operand · ×4
  • Subsumed condition operand crates/nono-proxy/src/route.rs:2459 — `msg.contains("invalid CA certificate")` can never decide this `||` — every value satisfying `msg.contains("invalid CA certificate")` also satisfies `msg.contains("CA certificate")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
  • Subsumed condition operand crates/nono-cli/src/profile/mod.rs:12365 — `msg.contains("aws_auth")` can never decide this `||` — every value satisfying `msg.contains("aws_auth")` also satisfies `msg.contains("auth")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
  • Subsumed condition operand crates/nono-cli/src/profile/mod.rs:12408 — `msg.contains("profile")` can never decide this `&&` — every value satisfying `msg.contains("profiles")` also satisfies `msg.contains("profile")`, so the `&&` chain is already decided by the former. The expression is equivalent to the chain without it, which means it is narrower than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
  • Subsumed condition operand crates/nono-cli/src/diagnostic/formatter.rs:268 — `lower.contains("file already exists")` can never decide this `||` — every value satisfying `lower.contains("file already exists")` also satisfies `lower.contains("already exists")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
D41 · Kernel & Syscall Confinement · No seccomp profile · ×2
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 7 significant file(s) lose their only recent owner: crates/nono-cli/src/connect_client.rs, crates/nono-cli/src/platform.rs, crates/nono/src/undo/object_store.rs, crates/nono/src/undo/merkle.rs, crates/nono-proxy/src/oauth_capture/persist.rs, crates/nono-cli/src/owned_children.rs, crates/nono-cli/src/config/embedded.rs. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 5 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (12 single-owned of 221 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; 221 of the 236 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: crates/nono/src/resource/mod.rs, crates/nono-test-support/src/cli.rs, crates/nono-proxy/src/capture.rs, crates/nono-proxy/src/line_reader.rs, crates/nono-cli/src/tool-sandbox/shim.rs.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 3 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `crates/nono-cli` (156776 LoC, 427 module-visible types across 9 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 1 of 221 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; 221 of the 236 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: crates/nono-proxy/src/rate_limit.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.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file crates/nono-proxy/src/rate_limit.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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
D42 · Runtime Threat Enforcement · No runtime threat detection · ×1
  • No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.
P10 · Library API & versioning · Implementation type on the public API · ×1
  • Implementation type on the public API crates/nono/src/diagnostic/detail.rs:9 — 2 public types in `nono.diagnostic.detail` are marked as implementation by their own namespace, folder or name: `NonoDiagnosticDetail` (crates/nono/src/diagnostic/detail.rs:9, `detail`), `StderrObservationKind` (crates/nono/src/diagnostic/detail.rs:32, `detail`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 3/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`.
P3 · Security & performance tooling · Dependabot does not watch npm · ×1
  • Dependabot does not watch npm REDACTED:5 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
Minor — 10 finding(s)
D12 · Dependency Hygiene · Outdated · ×10
  • Outdated: aho-corasick — `aho-corasick` is locked at 1.1.4 but 1.1.5 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/nono-cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aho-corasick` and commit the updated REDACTED.
  • Outdated: aws-config — `aws-config` is locked at 1.13.1 but 1.13.2 is the current stable release on crates.io, and it already satisfies the `"1.13.1"` requirement declared in crates/nono-proxy/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-runtime — `aws-runtime` is locked at 1.10.3 but 1.10.4 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/nono-proxy/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-runtime` and commit the updated REDACTED.
  • Outdated: itoa — `itoa` is locked at 1.0.18 but 1.0.19 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/nono-cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p itoa` and commit the updated REDACTED.
  • Outdated: syn — `syn` is locked at 3.0.9 but 3.0.10 is the current stable release on crates.io, and it already satisfies the `"3"` requirement declared in crates/nono/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p syn` and commit the updated REDACTED.
  • Outdated: toml — `toml` is locked at 1.1.3+spec-1.1.0 but 1.2.1+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in crates/nono-cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml` and commit the updated REDACTED.
  • Outdated: ureq — `ureq` is locked at 3.5.1 but 3.5.2 is the current stable release on crates.io, and it already satisfies the `"~3.5"` requirement declared in crates/nono-cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ureq` and commit the updated REDACTED.
  • Outdated: uuid — `uuid` is locked at 1.29.0 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/nono-cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.
  • Outdated: webpki-roots — `webpki-roots` is locked at 1.0.11 but 1.0.12 is the current stable release on crates.io, and it already satisfies the `"1.0.10"` requirement declared in crates/nono-proxy/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p webpki-roots` and commit the updated REDACTED.
  • Outdated: zstd — `zstd` is locked at 0.14.3 but 0.14.4 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in crates/nono-cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zstd` and commit the updated REDACTED.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

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-5bc41e5992d84b99b49d2dc19bac7854/history.json --exit-code 0 --source .7artifacts/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-5bc41e5992d84b99b49d2dc19bac7854/tree.json --exit-code 0 --source .5artifacts/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 --exclude bindings/c/include .11artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .4artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .38artifacts/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.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 01a1dbf5-a618-70c9-bc3e-6ff5d3c95718 · 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