Public report — nono, published 30 Sep 2026.
Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches,
dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.18 (frozen) · verify this surveyFiledcd_c7e654b87a8442678ff920ed4c6e7461
Filed 30 September 2026, 17:33 UTC
Public
Large · 202,626 LoC · 6 projects · rebuild ~2.0 person-years · weakest lens: Maturity (66%)
Findings by grade
14 critical885 serious41 minor36 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
30 September 2026, 17:29 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
918findings with an exact file:lineof 940 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
50/120dimensions across the health lenses202626 LoC · 6 projects — wide & deep
Preview (pre-1.0). This repo hasn't declared a stable release, so it's judged against a relaxed, pre-production bar.
The system holds a strong overall standing with a health score of 72%, indicating a robust asset that delivers value but carries manageable risks. This is a large-scale operation, encompassing over 200,000 lines of production code, where the logic is deeply integrated rather than boilerplate. Rebuilding this from scratch would require approximately two person-years and nearly €290,000, highlighting the significant capital tied up in the current architecture. The high architectural score of 94% suggests the structural foundation is solid, yet the lower maturity and code health scores reveal hidden costs in daily operations.
The most pressing issue is a velocity tax on every change. Code quality signals indicate that modifications in weaker areas cost 3–8% more effort than in clean code. This inefficiency compounds annually, costing the team roughly 36 to 215 engineer-days per year. This recurring drag on delivery speed is far more expensive than the one-time effort required to fix the underlying issues, meaning the cost of inaction quickly outweighs the investment in remediation.
A secondary risk lies in organizational memory and maturity. With only three architecture decision records, the team lacks the documented context needed for new members to navigate the system effectively. This gap slows onboarding and increases the risk of repeating past mistakes. While the production readiness score is healthy, the lack of measured domain modeling and event-driven patterns means we cannot fully assess the system’s adaptability to future business changes, leaving some strategic risks unquantified.
Despite these challenges, the system’s strong architectural integrity and high performance score are genuine strengths that ensure reliability and speed for end-users. To maximize leverage, the immediate focus should be on growing the architecture decision log to eight entries. This low-effort action raises the maturity tier, improves team alignment, and pays for itself by reducing future coordination overhead. Until more data is gathered on unmeasured areas, this targeted documentation effort offers the highest return on investment for sustained delivery health.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
1.1× (at 72% quality) — the last 20% of quality is most of the work
Size & shape
Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~2.0 person-years of build effort (about ~€290,000 to rebuild). Its weakest lens is Maturity at 66% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 1.1× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made.
The top-ranked fix costs roughly 3–10 engineer-days once. Not doing it costs about 35.8–214.9 engineer-days every year, paid as drag on the ~417,633 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 1–3 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 3–8% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.
Evidence: D15 churn: 102,978 line(s) changed over a 90-day window ⇒ ~417,633/year · D1/D2/D4/D6 code quality: averaging 6.6/10 ⇒ a 3–8% drag on each change · top-ranked remediation: Medium effort ⇒ about 3–10 engineer-day(s)
→ Do the top-ranked fix now if this code will still be yours in 3 months.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 6.6/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 3–8% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4/D6 code quality: averaging 6.6/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
202 modules, 414 dependencies. 4 dependency cycles across 16 modules, marked above the diagonal.
Showing the 40 most-connected modules; 162 more are not drawn.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
nono_cli.exec_strategy.supervisor_linux uses nono.capability. Changing nono.capability can break nono_cli.exec_strategy.supervisor_linux, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→17 nono_cli.exec_strategy.supervisor_linux depends on nono.sandbox.linux✕
Type pairs
2 distinct (type in nono_cli.exec_strategy.supervisor_linux → type in nono.sandbox.linux) references.
nono_cli.exec_strategy.supervisor_linux uses nono.sandbox.linux. Changing nono.sandbox.linux can break nono_cli.exec_strategy.supervisor_linux, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→28 nono_cli.exec_strategy.supervisor_linux depends on nono.diagnostic.records✕
Type pairs
3 distinct (type in nono_cli.exec_strategy.supervisor_linux → type in nono.diagnostic.records) references.
nono_cli.exec_strategy.supervisor_linux uses nono.diagnostic.records. Changing nono.diagnostic.records can break nono_cli.exec_strategy.supervisor_linux, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→33 nono_cli.exec_strategy.supervisor_linux depends on nono_cli.exec_strategycycle✕
Type pairs
2 distinct (type in nono_cli.exec_strategy.supervisor_linux → type in nono_cli.exec_strategy) references.
nono_cli.exec_strategy.supervisor_linux uses nono_cli.exec_strategy. Changing nono_cli.exec_strategy can break nono_cli.exec_strategy.supervisor_linux, not the reverse.
Position
Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.
nono_cli.exec_strategy uses nono_cli.exec_strategy.supervisor_linux. Changing nono_cli.exec_strategy.supervisor_linux can break nono_cli.exec_strategy, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→10 nono_cli.exec_strategy.clone_files depends on nono_cli.profile✕
Type pairs
1 distinct (type in nono_cli.exec_strategy.clone_files → type in nono_cli.profile) reference.
nono_cli.exec_strategy.clone_files uses nono_cli.exec_strategy. Changing nono_cli.exec_strategy can break nono_cli.exec_strategy.clone_files, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→2 nono_cli.launch_runtime depends on nono.scrub✕
Type pairs
1 distinct (type in nono_cli.launch_runtime → type in nono.scrub) reference.
nono_cli.tool-sandbox.platform.linux uses nono_proxy.approval. Changing nono_proxy.approval can break nono_cli.tool-sandbox.platform.linux, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→8 nono_cli.tool-sandbox.platform.linux depends on nono_cli.command_policy✕
Type pairs
9 distinct (type in nono_cli.tool-sandbox.platform.linux → type in nono_cli.command_policy) references.
nono_cli.tool-sandbox.platform.linux uses nono_cli.command_policy. Changing nono_cli.command_policy can break nono_cli.tool-sandbox.platform.linux, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→16 nono_cli.tool-sandbox.platform.linux depends on nono.capability✕
Type pairs
5 distinct (type in nono_cli.tool-sandbox.platform.linux → type in nono.capability) references.
nono_cli.tool-sandbox.platform.linux uses nono.sandbox.linux. Changing nono.sandbox.linux can break nono_cli.tool-sandbox.platform.linux, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→23 nono_cli.tool-sandbox.platform.linux depends on nono.audit✕
Type pairs
6 distinct (type in nono_cli.tool-sandbox.platform.linux → type in nono.audit) references.
nono_cli.tool-sandbox.platform.linux uses nono_cli.exec_strategy.clone_files. Changing nono_cli.exec_strategy.clone_files can break nono_cli.tool-sandbox.platform.linux, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→2 nono_cli.supervised_runtime depends on nono.scrub✕
Type pairs
2 distinct (type in nono_cli.supervised_runtime → type in nono.scrub) references.
nono_cli.tool-sandbox.platform.macos uses nono_proxy.approval. Changing nono_proxy.approval can break nono_cli.tool-sandbox.platform.macos, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→8 nono_cli.tool-sandbox.platform.macos depends on nono_cli.command_policy✕
Type pairs
11 distinct (type in nono_cli.tool-sandbox.platform.macos → type in nono_cli.command_policy) references.
nono_cli.tool-sandbox.platform.macos uses nono_cli.command_policy. Changing nono_cli.command_policy can break nono_cli.tool-sandbox.platform.macos, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→13 nono_cli.tool-sandbox.platform.macos depends on nono_cli.policy✕
Type pairs
1 distinct (type in nono_cli.tool-sandbox.platform.macos → type in nono_cli.policy) reference.
nono_cli.tool-sandbox.platform.macos uses nono_cli.exec_strategy.clone_files. Changing nono_cli.exec_strategy.clone_files can break nono_cli.tool-sandbox.platform.macos, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→38 nono_cli.tool-sandbox.platform.macos depends on nono_cli.tool-sandbox.platform.linux✕
Type pairs
14 distinct (type in nono_cli.tool-sandbox.platform.macos → type in nono_cli.tool-sandbox.platform.linux) references.
nono_cli.tool-sandbox.platform.macos uses nono_cli.tool-sandbox.platform.linux. Changing nono_cli.tool-sandbox.platform.linux can break nono_cli.tool-sandbox.platform.macos, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
At a glance — Code Health · 79% · Adequate · gated by D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2021 — Security Misconfiguration
38
High / Critical
A03:2021 — Injection
12
High / Critical
A02:2021 — Cryptographic Failures
2
High / Critical
Roadmap
Begin by expanding the architecture decision record log to eight entries and documenting significant decisions as they occur to elevate maturity. Simultaneously, correct the README to align with actual platform support and add a high-level architecture section for clarity. Ensure internal implementation types remain private to protect consumers from breaking changes, and extend structured logging across all runnable modules to guarantee full production observability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made.
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 — 14
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 — 885
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 — 41
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 36
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 45 of 50 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 50 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 918 of 940 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D22 Internal API Consistency — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
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.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript source only, and no C# was loaded and no JavaScript/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.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (5): D19, D20, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
103 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was nono_cli::exec_strategy::execute_supervised at 106. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being nono_cli::app_runtime::dispatch_command at 31 — 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 31), 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.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 73 nono_cli finding(s) in Cyclomatic Complexity — start with profile_cmd.rs (5), mod.rs (5), exec_strategy.rs (4). — One of this dimension's main actionable groups (73 warning-level).
Resolve the 9 nono_proxy finding(s) in Cyclomatic Complexity — start with server.rs (2), reverse.rs (2), handle.rs (2). — One of this dimension's main actionable groups (9 warning-level).
Resolve the 5 CapabilitySet finding(s) in Cyclomatic Complexity — start with capability_ext.rs (2), capability.rs (2), manifest_convert.rs. — One of this dimension's main actionable groups (5 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 122 nono_cli finding(s) in Cognitive Complexity — start with mod.rs (8), policy.rs (7), exec_strategy.rs (6). — One of this dimension's main actionable groups (122 warning-level).
Resolve the 16 nono_proxy finding(s) in Cognitive Complexity — start with server.rs (4), reverse.rs (4), handle.rs (2). — One of this dimension's main actionable groups (16 warning-level).
Resolve the 13 nono finding(s) in Cognitive Complexity — start with audit.rs (4), capability.rs (2), policy.rs (2). — One of this dimension's main actionable groups (13 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 54 FunctionTooLong finding(s) in God Classes — start with profile_cmd.rs (5), reverse.rs (5), handle.rs (5). — One of this dimension's main actionable groups (54 warning-level).
Resolve the 37 FileTooLong finding(s) in God Classes — start with exec_strategy.rs, proxy_runtime.rs, mod.rs. — One of this dimension's main actionable groups (37 warning-level).
Resolve the 6 MethodTooLong finding(s) in God Classes — start with capability_ext.rs, credential.rs, proxy_runtime.rs. — One of this dimension's main actionable groups (6 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
386 duplicated block group(s) detected. A further 14 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 16 of the 400 are in trees this repository does not ship — vendored, example/demo, 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.
+ 100 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 28 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with linux.rs (9), capability_ext.rs (2), exec_strategy.rs (2). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 28 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with linux.rs (8), snapshot.rs (2), pty_proxy.rs (2). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 25 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with linux.rs (11), exec_strategy.rs (2), connect_client.rs (2). — One of this dimension's main actionable groups (25 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
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
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.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with capability.rs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
All 2 mechanizable ADR(s) are enforced: 1 by analyzers, 1 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
4229 test methods: 3985 unit, 244 integration, 0 BDD, 0 e2e. The Rust suite contributes 4229 `#[test]` function(s) across 194 file(s) declaring at least one; its unit/integration split is Cargo's own — 26 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
5 outdated, 0 yanked direct Cargo dependencies. 57 of 58 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed Cargo.lock). 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 Cargo.lock there.
Outdated: aws-sigv4 · ×5
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 499 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock 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.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: crates/nono-cli/src/exec_strategy.rs (20×106=2120); crates/nono-cli/src/tool-sandbox/platform/linux.rs (36×39=1404); crates/nono-cli/src/tool-sandbox/platform/macos.rs (32×38=1216) Repeated repair below the complexity floor: crates/nono-cli/src/tool-sandbox/mod.rs (10 of 12 changes were fixes); crates/nono-cli/src/tool-sandbox/policy.rs (5 of 9 changes were fixes); crates/nono-cli/src/sandbox_state.rs (4 of 7 changes were fixes)
Resolve the 33 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 (33 warning-level).
Resolve the 10 Repeated repair finding(s) in Churn × Complexity Hotspots — start with mod.rs, policy.rs, sandbox_state.rs. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.2 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
16 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 192 of the 205 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.
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.
2 deducted task-comment markers across 202626 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.
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with trust_cmd.rs, exec_strategy.rs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README gives a strong overview (nono is the secure attestation standard used by PyPI/npm/brew/Maven Central, with links to license, CI, and docs), plus an important organization-migration note for the nono registry namespace. The neps/README documents NEPs as design records for security-consequential changes, while tool-sandbox-examples/README shows practical demos of nono policy enforcement on real tools like `gh`, `kubectl`, and `aws`. crates/nono-cli/README is a complete CLI reference with installation, usage, themes, profiles, and an exhaustive list of features. The packaging directories (aur/rpm) explain the binary-package workflow, credentials, and COPR submission steps. All visible documents are well-structured and cover their intended scope. The repository's READMEs and architecture/Docs markdown files are well written for their respective directories: each directory's README is clear on what it demonstrates (e.g. nono SSH-agent brokering, GitHub CLI command-policy demo, Kubernetes command-sandbox), with a descriptive author, an overview of the demo's six What This Shows bullet points, and a file list plus links to related profiles or notes. The architecture/Docs set documents the nono project as a whole (maintaining.md, releasing.md, security-response.md) with release runbooks, security response guidance, and protocol specs for approval webhooks v1; it is comprehensive but not yet visible in this summary. All visible documents are complete and well-structured. The project's protocol documentation is clear, complete, and well-structured for its intended audience. Each of the three open-client contracts (audit-delivery-v1.md, remote-attach-v1.md, remote-run-v1.md) describes a distinct service with an overview paragraph, concrete request examples, authentication headers, signed-body semantics, and failure modes; all sections in the outline exist and are visible within the clipped body. The documentation is focused on the open-contract API surface rather than installation or usage of the nono CLI tools.
Documentation: no project overview · ×2README.md
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR QualityExemplary◐ Sampled · advisory
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
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.
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
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
12 finding(s): 0 critical, 10 high, 2 medium, 0 low. semgrep hit a parse error in 7 file(s) — `crates/nono-cli/src/sandbox_prepare.rs` (line 1572, lines 1572–1608, lines 1608–1609), `crates/nono-cli/src/session.rs` (line 156, line 164), `crates/nono-cli/src/setup.rs` (line 131, line 160, line 435), `crates/nono-cli/src/tool-sandbox/platform/macos.rs` (line 64, line 73), `scripts/claude-auth-state.sh` (line 337), … (+2 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
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 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.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 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).
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).
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.
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.
1 of 192 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/nono-cli/src/deprecation_warnings.rs. Counted over 192 of the 205 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
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 5 Change coupling finding(s) in Change Coupling — start with app_runtime.rs, network_policy.rs, mod.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
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).
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).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No AppArmor/SELinux confinement finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 2 of 5 project(s) that lack one — worth up to 0.8 pts.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README claims nono runs on macOS, Linux, WSL2; the evidence has no such claim — reported by the model that read the README against this repository; no term search was run for this one, so nothing here has been checked against the tree. Treat it as a reading to confirm, not as a measured contradiction: verify it against the code before acting on it, and if the footprint it describes does exist, this row is wrong.
What to do
Reconcile the README with reality: README claims nono runs on macOS, Linux, WSL2; the evidence has no such claim.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
205/262 types (78%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
Do you agree with this assessment?
P2 · Observability5.8 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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.
Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) or inside a Java method returning a Reactor Mono/Flux — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. This is reported because `server.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — testdata/spire/server.conf:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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 — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 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.
AC7 A11y enforcement — 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 — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/bui…; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~7130 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.
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.
D22 Internal API Consistency — LLM evaluation failed
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. 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — none of 3 ADRs are conformance-checkable — unverifiable.
D27 Navigability — symbol resolution incomplete — navigability not assessed
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (27 value object(s))
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 — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. 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 Python, 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
X1 Async 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
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — 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
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — 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
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
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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.
nono_cli::exec_strategy::execute_supervised (cognitive 199) crates/nono-cli/src/exec_strategy.rs:550— nono_cli::exec_strategy::execute_supervised has cognitive complexity 199 (threshold 15). Drivers by points: if/else 83 (157 pts), boolean chains 23, match/switch 7 (17 pts), loops 2 (nesting depth added 84). To reduce it, split the body into named stages: move each independent 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 118) crates/nono-cli/src/profile_cmd.rs:1422— nono_cli::profile_cmd::cmd_diff has cognitive complexity 118 (threshold 15). Drivers by points: if/else 39 (74 pts), loops 18 (36 pts), boolean chains 8 (nesting depth added 53). To reduce it, split the body into named stages: move each independent 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 85) crates/nono-cli/src/execution_runtime.rs:203— nono_cli::execution_runtime::execute_sandboxed has cognitive complexity 85 (threshold 15). Drivers by points: if/else 41 (53 pts), match/switch 7 (13 pts), boolean chains 10, loops 5 (9 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 78) crates/nono-cli/src/profile_cmd.rs:855— nono_cli::profile_cmd::cmd_show has cognitive complexity 78 (threshold 15). Drivers by points: if/else 36 (49 pts), loops 10 (20 pts), boolean chains 6, match/switch 1 (3 pts) (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_cli::tool-sandbox::platform::linux::handle_shim_stream_inner (cognitive 72) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1265— 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::exec_strategy::supervisor_linux::handle_received_filesystem_notification (cognitive 71) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:195— nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification has cognitive complexity 71 (threshold 15). Drivers by points: if/else 29 (46 pts), match/switch 12 (19 pts), boolean chains 6 (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::macos::handle_shim_stream_inner (cognitive 69) crates/nono-cli/src/tool-sandbox/platform/macos.rs:972— 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::pty_proxy::run_attach_loop (cognitive 69) crates/nono-cli/src/pty_proxy.rs:2574— 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::profile::validate_credential_capture_entries (cognitive 64) crates/nono-cli/src/profile/mod.rs:1393— 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 (cognitive 61) crates/nono-cli/src/exec_strategy.rs:2848— nono_cli::exec_strategy::run_supervisor_loop 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 60) crates/nono-cli/src/sandbox_prepare.rs:1427— nono_cli::sandbox_prepare::prepare_sandbox has cognitive complexity 60 (threshold 15). Drivers by points: if/else 29 (41 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::policy::apply_deny_overrides (cognitive 56) crates/nono-cli/src/policy.rs:1687— nono_cli::policy::apply_deny_overrides has cognitive complexity 56 (threshold 15). Drivers by points: if/else 20 (43 pts), loops 3 (6 pts), match/switch 1 (4 pts), boolean chains 3 (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::output::print_capabilities (cognitive 51) crates/nono-cli/src/output.rs:73— 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::profile_cmd::cmd_validate (cognitive 49) crates/nono-cli/src/profile_cmd.rs:2402— 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::exec_strategy::handle_supervisor_message (cognitive 47) crates/nono-cli/src/exec_strategy.rs:3291— nono_cli::exec_strategy::handle_supervisor_message has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (31 pts), match/switch 6 (16 pts) (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::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:658— 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::exec_strategy::run_supervisor_loop (cognitive 44) crates/nono-cli/src/exec_strategy.rs:2603— 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::trust_scan::run_pre_exec_scan (cognitive 44) crates/nono-cli/src/trust_scan.rs:375— nono_cli::trust_scan::run_pre_exec_scan has cognitive complexity 44 (threshold 15). Drivers by points: if/else 22 (35 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nono_cli::exec_strategy::clone_files::child_exec (cognitive 43) crates/nono-cli/src/exec_strategy/clone_files.rs:314— nono_cli::exec_strategy::clone_files::child_exec has cognitive complexity 43 (threshold 15). Drivers by points: if/else 31 (35 pts), boolean chains 6, loops 1, match/switch 1 (nesting depth added 4). 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::proxy_runtime::build_proxy_config_from_flags (cognitive 43) crates/nono-cli/src/proxy_runtime.rs:2357— nono_cli::proxy_runtime::build_proxy_config_from_flags has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (33 pts), loops 5 (8 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::supervisor_linux::handle_received_network_notification (cognitive 43) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:1043— nono_cli::exec_strategy::supervisor_linux::handle_received_network_notification has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 8 (15 pts), loops 2 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nono_cli::profile::find_pack_store_profile (cognitive 43) crates/nono-cli/src/profile/mod.rs:2987— nono_cli::profile::find_pack_store_profile has cognitive complexity 43 (threshold 15). Drivers by points: if/else 9 (24 pts), match/switch 4 (12 pts), loops 3 (6 pts), boolean chains 1 (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::profile::list_pack_store_profiles (cognitive 43) crates/nono-cli/src/profile/mod.rs:4319— nono_cli::profile::list_pack_store_profiles has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 4 (12 pts), match/switch 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::exec_strategy::execute_supervised (cyclomatic 106) crates/nono-cli/src/exec_strategy.rs:550— nono_cli::exec_strategy::execute_supervised has cyclomatic complexity 106 (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 61) crates/nono-cli/src/profile_cmd.rs:1422— nono_cli::profile_cmd::cmd_diff has cyclomatic complexity 61 (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 54) crates/nono-cli/src/profile_cmd.rs:855— nono_cli::profile_cmd::cmd_show has cyclomatic complexity 54 (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 53) crates/nono-cli/src/execution_runtime.rs:203— nono_cli::execution_runtime::execute_sandboxed has cyclomatic complexity 53 (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::exec_strategy::supervisor_linux::handle_received_filesystem_notification (cyclomatic 44) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:195— nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification 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_cli::tool-sandbox::platform::linux::handle_shim_stream_inner (cyclomatic 39) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1265— 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::exec_strategy::clone_files::child_exec (cyclomatic 39) crates/nono-cli/src/exec_strategy/clone_files.rs:314— nono_cli::exec_strategy::clone_files::child_exec has cyclomatic complexity 39 (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 (cyclomatic 39) crates/nono-cli/src/exec_strategy.rs:2848— nono_cli::exec_strategy::run_supervisor_loop 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::macos::handle_shim_stream_inner (cyclomatic 38) crates/nono-cli/src/tool-sandbox/platform/macos.rs:972— 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::sandbox_prepare::prepare_sandbox (cyclomatic 37) crates/nono-cli/src/sandbox_prepare.rs:1427— nono_cli::sandbox_prepare::prepare_sandbox has cyclomatic complexity 37 (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 36) crates/nono-cli/src/profile_cmd.rs:2942— nono_cli::profile_cmd::resolve_to_manifest has cyclomatic complexity 36 (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.
nono_cli::pty_proxy::run_attach_loop (cyclomatic 34) crates/nono-cli/src/pty_proxy.rs:2574— 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::profile::validate_credential_capture_entries (cyclomatic 34) crates/nono-cli/src/profile/mod.rs:1393— 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::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::profile::validate_custom_credential (cyclomatic 33) crates/nono-cli/src/profile/mod.rs:607— nono_cli::profile::validate_custom_credential has cyclomatic complexity 33 (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::policy::apply_macos_keychain_db_exception (cyclomatic 32) crates/nono-cli/src/policy.rs:1435— nono_cli::policy::apply_macos_keychain_db_exception has cyclomatic complexity 32 (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::command_policy::validate_credential (cyclomatic 28) crates/nono-cli/src/command_policy.rs:2551— nono_cli::command_policy::validate_credential 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_cli::profile_cmd::cmd_validate (cyclomatic 27) crates/nono-cli/src/profile_cmd.rs:2402— 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::exec_strategy::supervisor_linux::handle_received_network_notification (cyclomatic 27) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:1043— nono_cli::exec_strategy::supervisor_linux::handle_received_network_notification 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:2603— 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:73— 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.
nono_cli::proxy_runtime::prepare_proxy_launch_options (cyclomatic 25) crates/nono-cli/src/proxy_runtime.rs:1430— nono_cli::proxy_runtime::prepare_proxy_launch_options 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_cli::pty_proxy::match_enhanced_key_sequence (cyclomatic 25) crates/nono-cli/src/pty_proxy.rs:1394— nono_cli::pty_proxy::match_enhanced_key_sequence 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_cli::policy::apply_deny_overrides (cyclomatic 24) crates/nono-cli/src/policy.rs:1687— nono_cli::policy::apply_deny_overrides has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FunctionTooLong: nono_cli::execution_runtime::execute_sandboxed crates/nono-cli/src/execution_runtime.rs:203— FunctionTooLong — nono_cli::execution_runtime::execute_sandboxed runs 477 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 377 over it, 4.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::profile_cmd::cmd_diff crates/nono-cli/src/profile_cmd.rs:1422— FunctionTooLong — nono_cli::profile_cmd::cmd_diff runs 413 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 313 over it, 4.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_cli::sandbox_prepare::prepare_sandbox crates/nono-cli/src/sandbox_prepare.rs:1427— FunctionTooLong — nono_cli::sandbox_prepare::prepare_sandbox runs 409 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 309 over it, 4.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_proxy::reverse::handle_reverse_proxy crates/nono-proxy/src/reverse.rs:128— FunctionTooLong — nono_proxy::reverse::handle_reverse_proxy runs 394 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 294 over it, 3.94× 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:397— FunctionTooLong — nono_proxy::tls_intercept::handle::select_intercept_route runs 365 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 265 over it, 3.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_proxy::server::handle_connection crates/nono-proxy/src/server.rs:1477— FunctionTooLong — nono_proxy::server::handle_connection runs 318 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 218 over it, 3.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification crates/nono-cli/src/exec_strategy/supervisor_linux.rs:195— FunctionTooLong — nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification runs 304 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 204 over it, 3.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_cli::profile_cmd::resolve_to_manifest crates/nono-cli/src/profile_cmd.rs:2942— FunctionTooLong — nono_cli::profile_cmd::resolve_to_manifest runs 266 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 166 over it, 2.66× 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::enforce_endpoint_policy crates/nono-proxy/src/reverse.rs:1058— FunctionTooLong — nono_proxy::reverse::enforce_endpoint_policy runs 259 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 159 over it, 2.59× 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:1030— FunctionTooLong — nono_proxy::tls_intercept::handle::handle_inner_request runs 258 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 158 over it, 2.58× 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:855— FunctionTooLong — nono_cli::profile_cmd::cmd_show runs 253 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 153 over it, 2.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_cli::profile_runtime::prepare_profile_with_options crates/nono-cli/src/profile_runtime.rs:658— FunctionTooLong — nono_cli::profile_runtime::prepare_profile_with_options runs 242 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 142 over it, 2.42× 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_nonce_resolver crates/nono-proxy/src/server.rs:1054— FunctionTooLong — nono_proxy::server::start_with_nonce_resolver runs 230 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 130 over it, 2.30× 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 228 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 128 over it, 2.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_cli::supervised_runtime::execute_supervised_runtime crates/nono-cli/src/supervised_runtime.rs:210— FunctionTooLong — nono_cli::supervised_runtime::execute_supervised_runtime runs 207 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 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_cli::profile::merge_profiles crates/nono-cli/src/profile/mod.rs:3719— FunctionTooLong — nono_cli::profile::merge_profiles runs 190 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 90 over it, 1.90× 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::query_ext::query_network crates/nono-cli/src/query_ext.rs:240— FunctionTooLong — nono_cli::query_ext::query_network runs 189 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 89 over it, 1.89× 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:696— 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:1123— 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:117— FunctionTooLong — nono_cli::why_runtime::run_why runs 166 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 66 over it, 1.66× 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:1430— FunctionTooLong — nono_cli::proxy_runtime::prepare_proxy_launch_options 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_proxy::server::handle_forward_http crates/nono-proxy/src/server.rs:1987— FunctionTooLong — nono_proxy::server::handle_forward_http runs 161 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 61 over it, 1.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::handle_spiffe_intercept_request crates/nono-proxy/src/tls_intercept/handle.rs:1407— FunctionTooLong — nono_proxy::tls_intercept::handle::handle_spiffe_intercept_request runs 150 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 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: nono_cli::output::print_capabilities crates/nono-cli/src/output.rs:73— FunctionTooLong — nono_cli::output::print_capabilities runs 149 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 49 over it, 1.49× 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:1435— FunctionTooLong — nono_cli::policy::apply_macos_keychain_db_exception runs 142 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 42 over it, 1.42× 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.
FileTooLong: src/exec_strategy.rs crates/nono-cli/src/exec_strategy.rs— FileTooLong — 2615 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 2115 over it, 5.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/proxy_runtime.rs crates/nono-cli/src/proxy_runtime.rs— FileTooLong — 2553 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 72 free functions. The bar is 500 significant lines; this is 2053 over it, 5.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: profile/mod.rs crates/nono-cli/src/profile/mod.rs— FileTooLong — 2413 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 84 free functions. The bar is 500 significant lines; this is 1913 over it, 4.83× 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 — 2286 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 55 free functions. The bar is 500 significant lines; this is 1786 over it, 4.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: src/profile_cmd.rs crates/nono-cli/src/profile_cmd.rs— FileTooLong — 2238 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 1738 over it, 4.48× 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 — 1978 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 50 free functions. The bar is 500 significant lines; this is 1478 over it, 3.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/cli.rs crates/nono-cli/src/cli.rs— FileTooLong — 1777 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 1277 over it, 3.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: diagnostic/formatter.rs crates/nono-cli/src/diagnostic/formatter.rs— FileTooLong — 1756 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 62% of them inside a single declaration: DiagnosticFormatter (2 blocks, 634-2330), declaring 39 free functions. The bar is 500 significant lines; this is 1256 over it, 3.51× 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 — 1632 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 59 free functions. 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: tls_intercept/handle.rs crates/nono-proxy/src/tls_intercept/handle.rs— FileTooLong — 1520 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 1020 over it, 3.04× 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 — 1374 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 874 over it, 2.75× 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/server.rs crates/nono-proxy/src/server.rs— FileTooLong — 1315 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 815 over it, 2.63× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/sandbox_prepare.rs crates/nono-cli/src/sandbox_prepare.rs— FileTooLong — 1267 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 767 over it, 2.53× 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 — 1182 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 682 over it, 2.36× 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/audit.rs crates/nono/src/audit.rs— FileTooLong — 1038 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 538 over it, 2.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/trust_cmd.rs crates/nono-cli/src/trust_cmd.rs— FileTooLong — 975 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 475 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 — 964 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 464 over it, 1.93× 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 — 944 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 444 over it, 1.89× 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 — 860 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 40 free functions. The bar is 500 significant lines; this is 360 over it, 1.72× 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 — 847 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 347 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.
FileTooLong: src/profile_runtime.rs crates/nono-cli/src/profile_runtime.rs— FileTooLong — 818 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 318 over it, 1.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/capability_ext.rs crates/nono-cli/src/capability_ext.rs— FileTooLong — 805 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 305 over it, 1.61× 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.
Hotspot: crates/nono-cli/src/exec_strategy.rs crates/nono-cli/src/exec_strategy.rs:550— crates/nono-cli/src/exec_strategy.rs changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 106 in nono_cli::exec_strategy::execute_supervised at line 550. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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-cli/src/tool-sandbox/platform/linux.rs crates/nono-cli/src/tool-sandbox/platform/linux.rs:1265— crates/nono-cli/src/tool-sandbox/platform/linux.rs changed 36 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 1265. 20 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/tool-sandbox/platform/macos.rs crates/nono-cli/src/tool-sandbox/platform/macos.rs:972— crates/nono-cli/src/tool-sandbox/platform/macos.rs changed 32 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 972. 20 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/profile/mod.rs crates/nono-cli/src/profile/mod.rs:607— crates/nono-cli/src/profile/mod.rs changed 35 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in nono_cli::profile::validate_custom_credential at line 607. 16 of those changes were fix/bug commits, and the other 19 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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-proxy/src/server.rs crates/nono-proxy/src/server.rs:1477— crates/nono-proxy/src/server.rs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in nono_proxy::server::handle_connection at line 1477. 11 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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-cli/src/execution_runtime.rs crates/nono-cli/src/execution_runtime.rs:203— crates/nono-cli/src/execution_runtime.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in nono_cli::execution_runtime::execute_sandboxed at line 203. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/sandbox_prepare.rs crates/nono-cli/src/sandbox_prepare.rs:1427— crates/nono-cli/src/sandbox_prepare.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in nono_cli::sandbox_prepare::prepare_sandbox at line 1427. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/proxy_runtime.rs crates/nono-cli/src/proxy_runtime.rs:1430— crates/nono-cli/src/proxy_runtime.rs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in nono_cli::proxy_runtime::prepare_proxy_launch_options at line 1430. 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/policy.rs crates/nono-cli/src/policy.rs:1435— crates/nono-cli/src/policy.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in nono_cli::policy::apply_macos_keychain_db_exception at line 1435. 7 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/profile_cmd.rs crates/nono-cli/src/profile_cmd.rs:855— 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 54 in nono_cli::profile_cmd::cmd_show at line 855. 3 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/capability_ext.rs crates/nono-cli/src/capability_ext.rs:693— crates/nono-cli/src/capability_ext.rs changed 9 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/tls_intercept/handle.rs crates/nono-proxy/src/tls_intercept/handle.rs:1030— crates/nono-proxy/src/tls_intercept/handle.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in nono_proxy::tls_intercept::handle::handle_inner_request at line 1030. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/command_policy.rs crates/nono-cli/src/command_policy.rs:1597— crates/nono-cli/src/command_policy.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in nono_cli::command_policy::validate_command at line 1597. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/profile_runtime.rs crates/nono-cli/src/profile_runtime.rs:658— crates/nono-cli/src/profile_runtime.rs changed 16 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 658. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/exec_strategy/supervisor_linux.rs crates/nono-cli/src/exec_strategy/supervisor_linux.rs:195— crates/nono-cli/src/exec_strategy/supervisor_linux.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in nono_cli::exec_strategy::supervisor_linux::handle_received_filesystem_notification at line 195. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/src/sandbox/linux.rs crates/nono/src/sandbox/linux.rs:1037— crates/nono/src/sandbox/linux.rs changed 10 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 1037. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/src/sandbox/macos.rs crates/nono/src/sandbox/macos.rs:498— crates/nono/src/sandbox/macos.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in nono::sandbox::macos::generate_profile at line 498. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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-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 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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-proxy/src/reverse.rs crates/nono-proxy/src/reverse.rs:128— crates/nono-proxy/src/reverse.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in nono_proxy::reverse::handle_reverse_proxy at line 128. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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-cli/src/audit_commands.rs crates/nono-cli/src/audit_commands.rs:348— crates/nono-cli/src/audit_commands.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in nono_cli::audit_commands::cmd_show at line 348. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01:00' --full-history --no-merges -- crates/nono-cli/src/audit_commands.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:333— crates/nono-cli/src/launch_runtime.rs changed 13 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 333. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/app_runtime.rs crates/nono-cli/src/app_runtime.rs:36— crates/nono-cli/src/app_runtime.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in nono_cli::app_runtime::dispatch_command at line 36. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01:00' --full-history --no-merges -- crates/nono-cli/src/app_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/output.rs crates/nono-cli/src/output.rs:73— crates/nono-cli/src/output.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in nono_cli::output::print_capabilities at line 73. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01:00' --full-history --no-merges -- crates/nono-cli/src/output.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_save_runtime.rs crates/nono-cli/src/profile_save_runtime.rs:1450— crates/nono-cli/src/profile_save_runtime.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in nono_cli::profile_save_runtime::interactive_denial_selector at line 1450. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01:00' --full-history --no-merges -- crates/nono-cli/src/profile_save_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:1250— crates/nono-cli/src/diagnostic/formatter.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in DiagnosticFormatter::format_supervised_footer_with_diagnostics at line 1250. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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.
Duplicated block (10 lines × 2) crates/nono/src/capability.rs:712— crates/nono/src/capability.rs:712-721 | crates/nono/src/capability.rs:765-774 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) 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.
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.
Duplicated block (10 lines × 2) crates/nono-cli/src/exec_strategy.rs:729— crates/nono-cli/src/exec_strategy.rs:729-738 | crates/nono-cli/src/exec_strategy.rs:755-764 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/nono-cli/src/exec_strategy.rs:2761— crates/nono-cli/src/exec_strategy.rs:2761-2770 | crates/nono-cli/src/exec_strategy.rs:3164-3173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/nono-cli/src/profile/mod.rs:103— crates/nono-cli/src/profile/mod.rs:103-112 | crates/nono-cli/src/profile/mod.rs:1930-1939 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:418— crates/nono-cli/src/tool-sandbox/platform/linux.rs:418-427 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:379-388 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:952— crates/nono-cli/src/tool-sandbox/platform/linux.rs:952-961 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:765-774 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2484— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2484-2493 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4902-4911 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2904— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2904-2913 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5332-5341 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:3550— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3550-3559 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3039-3048 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:4640— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4640-4649 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4083-4092 — 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 118 separate duplicated blocks between them, totalling at least 1796 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/trust_cmd.rs:999— crates/nono-cli/src/trust_cmd.rs:999-1008 | 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.
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.
Duplicated block (10 lines × 2) crates/nono-proxy/src/connect.rs:89— crates/nono-proxy/src/connect.rs:89-98 | crates/nono-proxy/src/external.rs:213-222 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) crates/nono-proxy/src/credential.rs:266— crates/nono-proxy/src/credential.rs:266-275 | crates/nono-proxy/src/credential.rs:361-370 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/nono-proxy/src/reverse.rs:790— crates/nono-proxy/src/reverse.rs:790-799 | crates/nono-proxy/src/tls_intercept/handle.rs:1476-1485 — 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 4 separate duplicated blocks between them, totalling at least 44 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:845— crates/nono-proxy/src/reverse.rs:845-854 | crates/nono-proxy/src/reverse.rs:1482-1491 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/nono-proxy/src/tls_intercept/h2_forward.rs:626— crates/nono-proxy/src/tls_intercept/h2_forward.rs:626-635 | crates/nono-proxy/src/tls_intercept/h2_forward.rs:663-672 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1203— crates/nono-proxy/src/tls_intercept/handle.rs:1203-1212 | crates/nono-proxy/src/tls_intercept/handle.rs:1867-1876 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4110— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4110-4119 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3708-3717 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:5481— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5481-5490 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4640-4649 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:4944— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4944-4953 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4383-4394 — 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 118 separate duplicated blocks between them, totalling at least 1796 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.
Duplicated block (10 lines × 2) crates/nono-proxy/src/route.rs:799— crates/nono-proxy/src/route.rs:799-808 | crates/nono-proxy/src/route.rs:862-871 — both copies are in the same file, so extract the 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/session.rs:581— crates/nono-cli/src/session.rs:581-589 | crates/nono/src/audit.rs:885-893 — 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 (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.
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.
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:674— crates/nono-cli/src/proxy_runtime.rs:674-682 | crates/nono-cli/src/proxy_runtime.rs:752-760 — both copies are in the same file, so extract the 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:2224— crates/nono-cli/src/pty_proxy.rs:2224-2232 | crates/nono-cli/src/pty_proxy.rs:2266-2274 — both copies are in the same file, so extract the 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:2632— crates/nono-cli/src/pty_proxy.rs:2632-2640 | crates/nono-cli/src/pty_proxy.rs:2704-2712 — both copies are in the same file, so extract the 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/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.
Duplicated block (9 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3005— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3005-3013 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3020-3028 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:4122— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4122-4130 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3720-3728 — 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 118 separate duplicated blocks between them, totalling at least 1796 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/policy.rs:141— crates/nono-cli/src/tool-sandbox/policy.rs:141-149 | crates/nono-cli/src/tool-sandbox/policy.rs:151-159 — both copies are in the same file, so extract the 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/audit_commands.rs:313— crates/nono-cli/src/audit_commands.rs:313-321 | crates/nono-cli/src/rollback_commands.rs:266-274 — 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 136 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) REDACTED:310— REDACTED:310-318 | crates/nono-proxy/src/tls_intercept/cert_cache.rs:216-224 — 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/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.
Duplicated block (9 lines × 2) crates/nono-cli/src/audit_commands.rs:905— crates/nono-cli/src/audit_commands.rs:905-913 | 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:519— crates/nono-cli/src/tool-sandbox/platform/linux.rs:519-527 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:460-468 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:4717— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4717-4725 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4165-4173 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2459— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2459-2467 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4877-4885 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:4241— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4241-4249 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3804-3812 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:4874— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4874-4882 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4320-4328 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:5492— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5492-5500 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4651-4659 — 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 118 separate duplicated blocks between them, totalling at least 1796 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/output.rs:707— crates/nono-cli/src/output.rs:707-718 | crates/nono-cli/src/output.rs:740-748 — both copies are in the same file, so extract the 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/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.
Duplicated block (9 lines × 2) crates/nono-cli/src/connect_client.rs:609— crates/nono-cli/src/connect_client.rs:609-617 | crates/nono-cli/src/connect_client.rs:707-715 — both copies are in the same file, so extract the 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/src/keystore.rs:1121— crates/nono/src/keystore.rs:1121-1129 | crates/nono/src/keystore.rs:1589-1597 — both copies are in the same file, so extract the 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:4092— crates/nono-cli/src/exec_strategy.rs:4092-4099 | crates/nono/src/capability.rs:2146-2153 — 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/src/supervisor/socket.rs:271— crates/nono/src/supervisor/socket.rs:271-278 | crates/nono/src/supervisor/socket.rs:328-335 — both copies are in the same file, so extract the 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/audit_client.rs:350— crates/nono-cli/src/audit_client.rs:350-357 | crates/nono-cli/src/platform_client.rs:241-248 — 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/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.
Duplicated block (8 lines × 2) crates/nono-cli/src/command_policy.rs:3486— crates/nono-cli/src/command_policy.rs:3486-3493 | crates/nono-cli/src/profile/mod.rs:3994-4001 — 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/connect_client.rs:307— crates/nono-cli/src/connect_client.rs:307-314 | crates/nono-cli/src/connect_client.rs:565-572 — both copies are in the same file, so extract the 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:2237— crates/nono-cli/src/exec_strategy.rs:2237-2244 | crates/nono-cli/src/pty_proxy.rs:2305-2312 — 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/proxy_command.rs:273— crates/nono-cli/src/proxy_command.rs:273-280 | crates/nono-cli/src/proxy_runtime.rs:1516-1523 — 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:218— crates/nono-cli/src/tool-sandbox/platform/linux.rs:218-225 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:228-235 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:230— crates/nono-cli/src/tool-sandbox/platform/linux.rs:230-237 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:245-252 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:1886— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1886-1893 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1606-1613 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2119— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2119-2126 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1907-1914 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:3632— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3632-3639 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3650-3657 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:5733— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5733-5740 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:5760-5767 — both copies are in the same file, so extract the 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/audit_commands.rs:938— crates/nono-cli/src/audit_commands.rs:938-945 | crates/nono-cli/src/rollback_commands.rs:192-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 136 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-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/reverse.rs:412— crates/nono-proxy/src/reverse.rs:412-419 | crates/nono-proxy/src/tls_intercept/handle.rs:840-847 — 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 4 separate duplicated blocks between them, totalling at least 44 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 (8 lines × 2) crates/nono-proxy/src/reverse.rs:2428— crates/nono-proxy/src/reverse.rs:2428-2435 | crates/nono-proxy/src/reverse.rs:2539-2546 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:2450— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2450-2457 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4868-4875 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2545— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2545-2552 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4963-4970 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2567— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2567-2574 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4974-4981 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:1907— crates/nono-cli/src/connect_client.rs:1907-1914 | crates/nono-cli/src/pty_proxy.rs:1374-1381 — 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:3402— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3402-3409 | crates/nono/src/sandbox/linux.rs:1463-1470 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono/src/sandbox/linux.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3478— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3478-3485 | 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.
Duplicated block (8 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:517— crates/nono-cli/src/tool-sandbox/platform/macos.rs:517-524 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:570-577 — both copies are in the same file, so extract the 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/src/audit.rs:916— crates/nono/src/audit.rs:916-926 | crates/nono/src/audit.rs:994-1004 — both copies are in the same file, so extract the 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/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.
Duplicated block (11 lines × 2) crates/nono/src/keystore.rs:1136— crates/nono/src/keystore.rs:1136-1146 | crates/nono/src/keystore.rs:1609-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.
Duplicated block (11 lines × 2) crates/nono-cli/src/proxy_command.rs:333— crates/nono-cli/src/proxy_command.rs:333-343 | crates/nono-cli/src/proxy_runtime.rs:1563-1573 — 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-cli/src/sandbox_log.rs:312— crates/nono-cli/src/sandbox_log.rs:312-322 | crates/nono-cli/src/sandbox_log.rs:328-340 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:1709— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1709-1719 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1416-1426 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2496— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2496-2506 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4914-4924 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3433— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3433-3443 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3466-3476 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:5348— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5348-5358 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4507-4517 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 × 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.
Duplicated block (11 lines × 2) crates/nono-cli/src/audit_commands.rs:838— crates/nono-cli/src/audit_commands.rs:838-848 | 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 136 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 × 2) crates/nono-cli/src/audit_commands.rs:861— crates/nono-cli/src/audit_commands.rs:861-871 | 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 136 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 × 2) crates/nono-proxy/src/audit.rs:170— crates/nono-proxy/src/audit.rs:170-180 | crates/nono-proxy/src/audit.rs:289-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 (11 lines × 2) crates/nono-proxy/src/server.rs:1938— crates/nono-proxy/src/server.rs:1938-1948 | crates/nono-proxy/src/server.rs:2074-2084 — both copies are in the same file, so extract the 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/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.
Duplicated block (11 lines × 2) crates/nono/src/trust/bundle.rs:551— crates/nono/src/trust/bundle.rs:551-562 | crates/nono/src/trust/bundle.rs:568-578 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:2966— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2966-2976 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5422-5432 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 × 2) crates/nono-cli/src/output.rs:870— crates/nono-cli/src/output.rs:870-880 | crates/nono-cli/src/output.rs:936-946 — both copies are in the same file, so extract the 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/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.
Duplicated block (11 lines × 2) crates/nono-cli/src/exec_strategy.rs:3560— crates/nono-cli/src/exec_strategy.rs:3560-3570 | crates/nono-cli/src/exec_strategy.rs:3629-3639 — both copies are in the same file, so extract the 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/exec_strategy/supervisor_linux.rs:460— crates/nono-cli/src/exec_strategy/supervisor_linux.rs:460-470 | crates/nono-cli/src/exec_strategy/supervisor_linux.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.
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/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/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.
Duplicated block (13 lines × 2) crates/nono-cli/src/exec_strategy.rs:1158— crates/nono-cli/src/exec_strategy.rs:1158-1170 | crates/nono-cli/src/exec_strategy.rs:1176-1188 — both copies are in the same file, so extract the 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:2918— crates/nono-cli/src/exec_strategy.rs:2918-2930 | crates/nono-cli/src/exec_strategy.rs:2945-2957 — both copies are in the same file, so extract the 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/network_policy.rs:359— crates/nono-cli/src/network_policy.rs:359-371 | crates/nono-cli/src/network_policy.rs:382-394 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:457— crates/nono-cli/src/tool-sandbox/platform/linux.rs:457-469 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:414-426 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1384— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1384-1396 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1098-1110 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1501— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1501-1513 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1215-1227 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1969— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1969-1981 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1696-1709 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2520— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2520-2532 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4938-4950 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3798— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3798-3810 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3249-3261 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5744— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5744-5756 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:5771-5783 — both copies are in the same file, so extract the 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/trust_cmd.rs:938— crates/nono-cli/src/trust_cmd.rs:938-950 | 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.
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.
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:352-364 — both copies are in the same file, so extract the 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-proxy/src/server.rs:1915— crates/nono-proxy/src/server.rs:1915-1927 | crates/nono-proxy/src/server.rs:2051-2063 — both copies are in the same file, so extract the 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:224— crates/nono-cli/src/proxy_runtime.rs:224-236 | crates/nono-cli/src/proxy_runtime.rs:249-261 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:4504— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4504-4516 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3943-3955 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (13 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3341— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3341-3353 | crates/nono/src/sandbox/linux.rs:1419-1431 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono/src/sandbox/linux.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (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.
Duplicated block (12 lines × 2) crates/nono/src/trust/signing.rs:102— crates/nono/src/trust/signing.rs:102-113 | crates/nono/src/trust/signing.rs:190-201 — both copies are in the same file, so extract the 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/exec_strategy.rs:2747— crates/nono-cli/src/exec_strategy.rs:2747-2758 | crates/nono-cli/src/exec_strategy.rs:3150-3161 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:1366— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1366-1377 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1080-1091 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1488— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1488-1499 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1202-1213 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1627— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1627-1638 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1335-1346 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2416— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2416-2427 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4834-4845 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4932— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4932-4943 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4372-4383 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:2588— crates/nono-cli/src/tool-sandbox/platform/macos.rs:2588-2599 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:2661-2672 — both copies are in the same file, so extract the 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-cli/src/profile_cmd.rs:1588— crates/nono-cli/src/profile_cmd.rs:1588-1599 | crates/nono-cli/src/profile_cmd.rs:2057-2068 — both copies are in the same file, so extract the 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/reverse.rs:1790— crates/nono-proxy/src/reverse.rs:1790-1801 | crates/nono-proxy/src/reverse.rs:2304-2315 — both copies are in the same file, so extract the 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:1949— crates/nono-proxy/src/tls_intercept/handle.rs:1949-1960 | crates/nono-proxy/src/tls_intercept/handle.rs:2056-2067 — both copies are in the same file, so extract the 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/exec_strategy.rs:1160— crates/nono-cli/src/exec_strategy.rs:1160-1171 | crates/nono-cli/src/exec_strategy.rs:1271-1285 — both copies are in the same file, so extract the 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/exec_strategy.rs:2065— crates/nono-cli/src/exec_strategy.rs:2065-2076 | crates/nono-cli/src/exec_strategy.rs:2719-2731 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:3389— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3389-3400 | crates/nono/src/sandbox/linux.rs:1450-1461 — before extracting anything, compare `crates/nono-cli/src/tool-sandbox/platform/linux.rs` and `crates/nono/src/sandbox/linux.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (12 lines × 2) crates/nono-cli/src/exec_strategy/supervisor_linux.rs:371— crates/nono-cli/src/exec_strategy/supervisor_linux.rs:371-382 | crates/nono-cli/src/exec_strategy/supervisor_linux.rs:428-439 — both copies are in the same file, so extract the 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/reverse.rs:1866— crates/nono-proxy/src/reverse.rs:1866-1877 | crates/nono-proxy/src/tls_intercept/handle.rs:2196-2207 — 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 4 separate duplicated blocks between them, totalling at least 44 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 (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.
Duplicated block (7 lines × 2) crates/nono/src/supervisor/socket.rs:259— crates/nono/src/supervisor/socket.rs:259-265 | crates/nono/src/supervisor/socket.rs:316-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/nono-cli/src/exec_strategy.rs:540— crates/nono-cli/src/exec_strategy.rs:540-546 | crates/nono-cli/src/exec_strategy.rs:687-693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/nono-cli/src/proxy_runtime.rs:716— crates/nono-cli/src/proxy_runtime.rs:716-722 | crates/nono-cli/src/proxy_runtime.rs:734-740 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:903— crates/nono-cli/src/tool-sandbox/platform/linux.rs:903-909 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:742-748 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:1495— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1495-1501 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1621-1627 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1515— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1515-1521 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1229-1235 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2512— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2512-2518 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4930-4936 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:5341— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5341-5347 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4500-4506 — 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 118 separate duplicated blocks between them, totalling at least 1796 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-proxy/src/reverse.rs:1907— crates/nono-proxy/src/reverse.rs:1907-1913 | crates/nono-proxy/src/reverse.rs:1954-1960 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2722— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2722-2728 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5178-5184 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:3722— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3722-3728 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3118-3124 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:5038— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5038-5044 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:2725-2731 — 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 118 separate duplicated blocks between them, totalling at least 1796 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: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 136 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 136 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:2283— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2283-2293 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4692-4698 — 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 118 separate duplicated blocks between them, totalling at least 1796 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/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.
Duplicated block (7 lines × 2) crates/nono-proxy/src/tls_intercept/h2_forward.rs:615— crates/nono-proxy/src/tls_intercept/h2_forward.rs:615-621 | crates/nono-proxy/src/tls_intercept/h2_forward.rs:652-658 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/nono-cli/src/profile/mod.rs:3219— crates/nono-cli/src/profile/mod.rs:3219-3225 | crates/nono-cli/src/profile/mod.rs:3232-3238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
nono_proxy::server::handle_connection (cognitive 131) crates/nono-proxy/src/server.rs:1477— nono_proxy::server::handle_connection has cognitive complexity 131 (threshold 15). Drivers by points: if/else 37 (94 pts), match/switch 3 (16 pts), loops 3 (13 pts), boolean chains 8 (nesting depth added 80). 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::select_intercept_route (cognitive 57) crates/nono-proxy/src/tls_intercept/handle.rs:397— nono_proxy::tls_intercept::handle::select_intercept_route has cognitive complexity 57 (threshold 15). Drivers by points: if/else 21 (42 pts), match/switch 5 (11 pts), boolean chains 3, loops 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent 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 52) crates/nono-proxy/src/reverse.rs:128— nono_proxy::reverse::handle_reverse_proxy has cognitive complexity 52 (threshold 15). Drivers by points: if/else 27 (37 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::tls_intercept::handle::handle_inner_request (cognitive 43) crates/nono-proxy/src/tls_intercept/handle.rs:1030— nono_proxy::tls_intercept::handle::handle_inner_request has cognitive complexity 43 (threshold 15). Drivers by points: if/else 21 (23 pts), match/switch 9 (14 pts), boolean chains 5, loops 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
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::server::start_with_nonce_resolver (cognitive 43) crates/nono-proxy/src/server.rs:1054— nono_proxy::server::start_with_nonce_resolver 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::config::validate_no_proxy_host_pattern (cognitive 27) crates/nono-proxy/src/config.rs:603— 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:2119— 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:1438— 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::server::accept_loop (cognitive 22) crates/nono-proxy/src/server.rs:1388— 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::reverse::read_chunked_request_body (cognitive 22) crates/nono-proxy/src/reverse.rs:1704— 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::config::validate_no_proxy_entry (cognitive 19) crates/nono-proxy/src/config.rs:391— 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:367— 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:2687— 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.
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.
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.
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.
Duplicated block (14 lines × 2) crates/nono-cli/src/exec_strategy.rs:2731— crates/nono-cli/src/exec_strategy.rs:2731-2744 | crates/nono-cli/src/exec_strategy.rs:3128-3141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/nono-cli/src/exec_strategy.rs:3928— crates/nono-cli/src/exec_strategy.rs:3928-3941 | crates/nono-cli/src/exec_strategy.rs:3993-4006 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:786— crates/nono-cli/src/tool-sandbox/platform/linux.rs:786-799 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:656-669 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1096— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1096-1109 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4469-4482 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 lines × 2) crates/nono-cli/src/output.rs:109— crates/nono-cli/src/output.rs:109-122 | crates/nono-cli/src/output.rs:162-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/nono-cli/src/trust_cmd.rs:347— crates/nono-cli/src/trust_cmd.rs:347-360 | crates/nono-cli/src/trust_cmd.rs:497-510 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/nono-proxy/src/reverse.rs:1219— crates/nono-proxy/src/reverse.rs:1219-1232 | crates/nono-proxy/src/tls_intercept/handle.rs:561-574 — 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 4 separate duplicated blocks between them, totalling at least 44 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 (14 lines × 2) crates/nono-proxy/src/reverse.rs:1431— crates/nono-proxy/src/reverse.rs:1431-1444 | crates/nono-proxy/src/reverse.rs:1521-1534 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1280— crates/nono-proxy/src/tls_intercept/handle.rs:1280-1293 | crates/nono-proxy/src/tls_intercept/handle.rs:1777-1790 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3732— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3732-3745 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3128-3141 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:625— crates/nono-proxy/src/tls_intercept/handle.rs:625-639 | crates/nono-proxy/src/tls_intercept/handle.rs:683-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.
Duplicated block (14 lines × 2) crates/nono-proxy/src/reverse.rs:1713— crates/nono-proxy/src/reverse.rs:1713-1726 | crates/nono-proxy/src/reverse.rs:1756-1769 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) 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.
Duplicated block (6 lines × 2) crates/nono-proxy/src/config.rs:710— crates/nono-proxy/src/config.rs:710-715 | 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.
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:365-370 — 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/profile/mod.rs:961— crates/nono-cli/src/profile/mod.rs:961-966 | crates/nono-cli/src/profile/mod.rs:973-978 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:1219— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1219-1224 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:910-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 118 separate duplicated blocks between them, totalling at least 1796 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/tool-sandbox/platform/linux.rs:2935— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2935-2940 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5403-5408 — 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 118 separate duplicated blocks between them, totalling at least 1796 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.
Duplicated block (6 lines × 2) crates/nono-proxy/src/config.rs:1188— crates/nono-proxy/src/config.rs:1188-1193 | crates/nono-proxy/src/config.rs:1348-1353 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:2610— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2610-2615 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5032-5037 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2237— crates/nono-cli/src/pty_proxy.rs:2237-2242 | crates/nono-cli/src/pty_proxy.rs:2279-2285 — both copies are in the same file, so extract the 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:585— crates/nono-cli/src/connect_client.rs:585-590 | 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.
Duplicated block (6 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2295— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2295-2300 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4700-4705 — 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 118 separate duplicated blocks between them, totalling at least 1796 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-proxy/src/tls_intercept/h2_forward.rs:609— crates/nono-proxy/src/tls_intercept/h2_forward.rs:609-614 | crates/nono-proxy/src/tls_intercept/h2_forward.rs:646-651 — both copies are in the same file, so extract the 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/sandbox_prepare.rs:1321— crates/nono-cli/src/sandbox_prepare.rs:1321-1326 | crates/nono-cli/src/sandbox_prepare.rs:1332-1337 — both copies are in the same file, so extract the 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:899— crates/nono/src/sandbox/linux.rs:899-904 | crates/nono/src/sandbox/linux.rs:1072-1077 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
nono::capability::tokenize_sexp (cognitive 63) crates/nono/src/capability.rs:681— 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 25) crates/nono/src/audit.rs:1434— nono::audit::verify_audit_log has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (21 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:1123— 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::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::audit::verify_inclusion_proof (cognitive 22) crates/nono/src/audit.rs:775— 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::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::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::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::capability::validate_platform_rule (cognitive 18) crates/nono/src/capability.rs:615— 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::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.
nono::audit::build_inclusion_proof (cognitive 17) crates/nono/src/audit.rs:714— 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.
Duplicated block (5 lines × 2) crates/nono-cli/src/profile_cmd.rs:1446— crates/nono-cli/src/profile_cmd.rs:1446-1450 | crates/nono-cli/src/profile_cmd.rs:1689-1693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2534— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2534-2538 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4952-4956 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2811— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2811-2815 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5239-5243 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:5277— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5277-5281 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4489-4493 — 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 118 separate duplicated blocks between them, totalling at least 1796 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.
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.
Duplicated block (5 lines × 2) crates/nono-cli/src/profile_cmd.rs:1828— crates/nono-cli/src/profile_cmd.rs:1828-1832 | crates/nono-cli/src/profile_cmd.rs:1857-1861 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3001— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3001-3005 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5533-5537 — 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 118 separate duplicated blocks between them, totalling at least 1796 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/supervisor/socket.rs:266— crates/nono/src/supervisor/socket.rs:266-270 | crates/nono/src/supervisor/socket.rs:323-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3780— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3780-3784 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3183-3187 — 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 118 separate duplicated blocks between them, totalling at least 1796 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/profile_cmd.rs:2051— crates/nono-cli/src/profile_cmd.rs:2051-2055 | crates/nono-cli/src/profile_cmd.rs:2188-2192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) 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.
Repeated repair: crates/nono-cli/src/tool-sandbox/mod.rs crates/nono-cli/src/tool-sandbox/mod.rs:330— crates/nono-cli/src/tool-sandbox/mod.rs changed 12 times in last 90 days and 10 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 330), 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/tool-sandbox/policy.rs crates/nono-cli/src/tool-sandbox/policy.rs:277— crates/nono-cli/src/tool-sandbox/policy.rs changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is nono_cli::tool-sandbox::policy::evaluate_invocation_policy at line 277), 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(keystore): refuse empty sanitized PATH for host-side brokers (#1895)”; “fix(tool-sandbox): isolate network policy by effective command scope (#1981)”; “fix(proxy): fail closed on non-granted endpoint approvals in TLS intercept (#1585)”; “fix(cli): add explicit intercept match predicates (#1364)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01:00' --full-history --no-merges -- crates/nono-cli/src/tool-sandbox/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:606— crates/nono-cli/src/sandbox_state.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 11 (its worst body is nono_cli::sandbox_state::cleanup_stale_state_files at line 606), 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(why): tolerate volatile process-relative aliases in --self reload (#1873)”; “fix(why): evaluate network.deny_domain in nono why host queries (#1751)”; “fix(policy): survive atomic replacement of resolv.conf; report stale … (#1448)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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-cli/src/command_runtime.rs crates/nono-cli/src/command_runtime.rs:155— crates/nono-cli/src/command_runtime.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 12 (its worst body is nono_cli::command_runtime::run_sandbox at line 155), 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: allow non-UTF-8 command line arguments (#1521)”; “fix(cli): reject upstream proxy with block net (#1392)”; “fix(tool-sandbox): resolve command policy paths against the live cwd (#1339)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01:00' --full-history --no-merges -- crates/nono-cli/src/command_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.
Repeated repair: crates/nono-proxy/src/token.rs crates/nono-proxy/src/token.rs:319— 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 5 (its worst body is nono_proxy::token::validate_proxy_auth at line 319), 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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-cli/src/terminal_approval.rs crates/nono-cli/src/terminal_approval.rs:139— crates/nono-cli/src/terminal_approval.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 13 (its worst body is nono_cli::terminal_approval::sanitize_for_terminal at line 139), 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): stop save-prompt failures from overriding the child exit code (#1804)”; “fix(cli): guard consent prompts against type-ahead”; “fix(proxy): fail closed on non-granted endpoint approvals in TLS intercept (#1585)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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.
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), 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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), 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-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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/src/error.rs crates/nono/src/error.rs:225— crates/nono/src/error.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 12 (its worst body is NonoError::diagnostic_code at line 225), 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): stop save-prompt failures from overriding the child exit code (#1804)”; “fix(fs): validate unix socket nodes and normalize landlock (#1654)”; “fix(audit): propogate errors after unparseable ledger (#1596)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01:00' --full-history --no-merges -- crates/nono/src/error.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: crates/nono-proxy/src/forward.rs crates/nono-proxy/src/forward.rs:367— crates/nono-proxy/src/forward.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 14 (its worst body is nono_proxy::forward::rewrite_http1_response at line 367), 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 closed when upstream DNS returns no addresses (#1894)”; “fix(proxy): add authenticated WebSocket tunneling for CONNECT/TLS-intercept routes (#1443)”; “fix(oauth): harden capture security boundaries”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-02..2026-09-30, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-02 16:27:11 +01:00' --until='2026-09-30 16:27:11 +01: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.
nono_proxy::server::handle_connection (cyclomatic 41) crates/nono-proxy/src/server.rs:1477— nono_proxy::server::handle_connection has cyclomatic complexity 41 (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 37) crates/nono-proxy/src/reverse.rs:128— nono_proxy::reverse::handle_reverse_proxy has cyclomatic complexity 37 (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::handle_inner_request (cyclomatic 34) crates/nono-proxy/src/tls_intercept/handle.rs:1030— nono_proxy::tls_intercept::handle::handle_inner_request 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_proxy::tls_intercept::handle::select_intercept_route (cyclomatic 31) crates/nono-proxy/src/tls_intercept/handle.rs:397— nono_proxy::tls_intercept::handle::select_intercept_route has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
nono_proxy::tls_intercept::h2_forward::handle_h2_stream (cyclomatic 31) crates/nono-proxy/src/tls_intercept/h2_forward.rs:232— nono_proxy::tls_intercept::h2_forward::handle_h2_stream has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
nono_proxy::server::start_with_nonce_resolver (cyclomatic 27) crates/nono-proxy/src/server.rs:1054— nono_proxy::server::start_with_nonce_resolver 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:2119— 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::config::validate_no_proxy_host_pattern (cyclomatic 20) crates/nono-proxy/src/config.rs:603— 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::config::validate_no_proxy_entry (cyclomatic 17) crates/nono-proxy/src/config.rs:391— 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.
Duplicated block (19 lines × 2) crates/nono-cli/src/diagnostic/formatter.rs:2717— crates/nono-cli/src/diagnostic/formatter.rs:2717-2735 | crates/nono-cli/src/exec_strategy.rs:4013-4031 — 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1452— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1452-1470 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1476-1494 — both copies are in the same file, so extract the 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1950— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1950-1968 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2029-2047 — both copies are in the same file, so extract the 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2430— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2430-2448 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4848-4866 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2618— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2618-2636 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5040-5058 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5257— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5257-5275 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4416-4434 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1166— crates/nono-cli/src/tool-sandbox/platform/macos.rs:1166-1184 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1190-1208 — both copies are in the same file, so extract the 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 (19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1677— crates/nono-cli/src/tool-sandbox/platform/macos.rs:1677-1695 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1763-1781 — both copies are in the same file, so extract the 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 (19 lines × 2) crates/nono-proxy/src/connect.rs:157— crates/nono-proxy/src/connect.rs:157-175 | crates/nono-proxy/src/forward.rs:232-250 — 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 (16 lines × 2) crates/nono-cli/src/exec_strategy.rs:2682— crates/nono-cli/src/exec_strategy.rs:2682-2697 | crates/nono-cli/src/exec_strategy.rs:3004-3019 — both copies are in the same file, so extract the 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:1578— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1578-1593 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1293-1308 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2916— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2916-2931 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5344-5359 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3367— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3367-3382 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3385-3400 — both copies are in the same file, so extract the 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:3764— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3764-3779 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3160-3175 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) crates/nono-cli/src/profile_cmd.rs:809— crates/nono-cli/src/profile_cmd.rs:809-824 | crates/nono-cli/src/profile_cmd.rs:833-848 — both copies are in the same file, so extract the 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-proxy/src/tls_intercept/handle.rs:645— crates/nono-proxy/src/tls_intercept/handle.rs:645-660 | crates/nono-proxy/src/tls_intercept/handle.rs:663-678 — both copies are in the same file, so extract the 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:2703— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2703-2718 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5129-5144 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) crates/nono/src/sandbox/linux.rs:2661— crates/nono/src/sandbox/linux.rs:2661-2678 | crates/nono/src/sandbox/linux.rs:2694-2709 — both copies are in the same file, so extract the 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 (18 lines × 2) crates/nono/src/capability.rs:1237— crates/nono/src/capability.rs:1237-1254 | crates/nono/src/capability.rs:1434-1451 — both copies are in the same file, so extract the 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 (18 lines × 2) crates/nono-cli/src/registry_client.rs:236— crates/nono-cli/src/registry_client.rs:236-253 | crates/nono-cli/src/registry_client.rs:371-388 — both copies are in the same file, so extract the 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 (18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1464— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1464-1481 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1178-1195 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1686— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1686-1703 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1393-1410 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4833— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4833-4850 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4279-4296 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) crates/nono-proxy/src/reverse.rs:232— crates/nono-proxy/src/reverse.rs:232-249 | crates/nono-proxy/src/reverse.rs:455-472 — both copies are in the same file, so extract the 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 (18 lines × 2) crates/nono-cli/src/profile/mod.rs:1515— crates/nono-cli/src/profile/mod.rs:1515-1532 | crates/nono-cli/src/proxy_runtime.rs:1289-1306 — 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:437— crates/nono-proxy/src/credential.rs:437-454 | crates/nono-proxy/src/credential.rs:501-519 — both copies are in the same file, so extract the 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/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:253— crates/nono-cli/src/sandbox_state.rs:253-278 | crates/nono-cli/src/session.rs:807-832 — 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 (26 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:711— crates/nono-cli/src/tool-sandbox/platform/linux.rs:711-736 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:607-632 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (26 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4050— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4050-4075 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3648-3673 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (26 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4200— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4200-4225 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3765-3790 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (26 lines × 2) tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:34— tool-sandbox-examples/kubernetes-with-approval/https-front-proxy.py:34-59 | tool-sandbox-examples/kubernetes/https-front-proxy.py:34-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 101 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 (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 101 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 (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.
Duplicated block (17 lines × 2) crates/nono-cli/src/policy.rs:1590— crates/nono-cli/src/policy.rs:1590-1606 | crates/nono-cli/src/policy.rs:1642-1658 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1371— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1371-1387 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1390-1406 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4856— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4856-4872 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4302-4318 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1085— crates/nono-cli/src/tool-sandbox/platform/macos.rs:1085-1101 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1104-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.
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:431-447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) crates/nono-proxy/src/reverse.rs:1298— crates/nono-proxy/src/reverse.rs:1298-1314 | crates/nono-proxy/src/reverse.rs:1317-1333 — both copies are in the same file, so extract the 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/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.
Duplicated block (15 lines × 2) crates/nono-cli/src/exec_strategy.rs:1095— crates/nono-cli/src/exec_strategy.rs:1095-1109 | crates/nono-cli/src/exec_strategy.rs:1301-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 (15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:394— crates/nono-cli/src/tool-sandbox/platform/linux.rs:394-408 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:354-368 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:477— crates/nono-cli/src/tool-sandbox/platform/linux.rs:477-491 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:437-451 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (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:511— crates/nono-proxy/src/reverse.rs:511-525 | crates/nono-proxy/src/reverse.rs:803-817 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:4519— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4519-4533 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3958-3973 — 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 118 separate duplicated blocks between them, totalling at least 1796 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.
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:1934— 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:1777— 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:1525— 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.
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: CredentialStore.load_with_diagnostics crates/nono-proxy/src/credential.rs:222— MethodTooLong — load_with_diagnostics 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.
MethodTooLong: ProxyCredentialCaptureBackend.run_capture_command crates/nono-cli/src/proxy_runtime.rs:381— 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: DiagnosticFormatter.format_exit_explanation crates/nono-cli/src/diagnostic/formatter.rs:991— MethodTooLong — format_exit_explanation runs 126 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RouteStore.load crates/nono-proxy/src/route.rs:206— MethodTooLong — load runs 116 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 16 over it, 1.16× 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:552— MethodTooLong — try_accept runs 107 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 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: DiagnosticFormatter crates/nono-cli/src/diagnostic/formatter.rs:634— ClassTooLong — 1096 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 70 methods, 2 blocks, lines 634-2330. The bar is 400 significant lines; this is 696 over it, 2.74× 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:263— ClassTooLong — 646 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 38 methods, 3 blocks, lines 263-1722. The bar is 400 significant lines; this is 246 over it, 1.62× 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:951— ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 73 methods, 2 blocks, lines 951-2086. The bar is 400 significant lines; this is 80 over it, 1.20× 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 — 445 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 3 blocks, lines 144-773. The bar is 400 significant lines; this is 45 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Commands crates/nono-cli/src/cli.rs:107— ClassTooLong — 427 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 27 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (22 lines × 2) crates/nono-cli/src/pty_proxy.rs:2163— crates/nono-cli/src/pty_proxy.rs:2163-2184 | crates/nono-cli/src/pty_proxy.rs:2191-2212 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:1526— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1526-1547 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1662-1683 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:2644— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2644-2665 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5066-5087 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (22 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1240— crates/nono-cli/src/tool-sandbox/platform/macos.rs:1240-1261 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1368-1389 — both copies are in the same file, so extract the 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.
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 101 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.
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:1934— 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:1777— 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.
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.
Change coupling: app_runtime.rs ↔ cli_bootstrap.rs crates/nono-cli/src/app_runtime.rs— `crates/nono-cli/src/app_runtime.rs` and `crates/nono-cli/src/cli_bootstrap.rs` change together 73% of the time (8 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 8 shared commits counted here, the most recent 3 are `9078ffcf` feat(remote): add remote session connect and ps (#1656); `4d221938` chore: remove deprecated nono learn command (#1543); `c5c7f56e` feat(cli): add platform enrollment and audit delivery (#1538) — run `git show` on any of them.
Change coupling: network_policy.rs ↔ credential.rs crates/nono-cli/src/network_policy.rs— `crates/nono-cli/src/network_policy.rs` and `crates/nono-proxy/src/credential.rs` change together 50% of the time (15 of the 30 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `7301ac2e` fix(proxy): add redeem_phantoms for by-value phantom redemption (#1469); `5bb098cd` feat: [aws] implement aws_auth config (#1166); `57005737` fix(proxy): honor explicit credential_format on custom inject headers — run `git show` on any of them.
Change coupling: mod.rs ↔ credential.rs crates/nono-cli/src/profile/mod.rs— `crates/nono-cli/src/profile/mod.rs` and `crates/nono-proxy/src/credential.rs` change together 50% of the time (15 of the 30 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `9488c4c5` feat(cleanup)!: remove remaining deprecated surfaces (#1871); `7301ac2e` fix(proxy): add redeem_phantoms for by-value phantom redemption (#1469); `5bb098cd` feat: [aws] implement aws_auth config (#1166) — run `git show` on any of them.
Change coupling: main.rs ↔ snapshot.rs crates/nono-cli/src/main.rs— `crates/nono-cli/src/main.rs` and `crates/nono/src/undo/snapshot.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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `6ecade2e` feat(audit): add audit attestation for session merkle roots; `4f9552ec` feat(audit): add tamper-evident audit log integrity; `8897d29a` chore: remove Monitor strategy, make Supervised the default (#267) — run `git show` on any of them.
Change coupling: cli.rs ↔ package.rs crates/nono-cli/src/cli.rs— `crates/nono-cli/src/cli.rs` and `crates/nono-cli/src/package.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 5 shared commits counted here, the most recent 3 are `64d9f283` feat(package): add package pinning and outdated commands; `829c341a` add commands to manage profile drafts and check package status; `d05672d5` fix(wiring): harden install and uninstall wiring — run `git show` on any of them.
Duplicated block (10–11 lines × 2) crates/nono-cli/src/command_policy.rs:309— crates/nono-cli/src/command_policy.rs:309-319 | crates/nono-cli/src/command_policy.rs:664-673 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) crates/nono-cli/src/package_cmd.rs:429— crates/nono-cli/src/package_cmd.rs:429-439 | crates/nono-cli/src/package_cmd.rs:458-467 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1918— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1918-1927 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1644-1654 — 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 118 separate duplicated blocks between them, totalling at least 1796 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–11 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1997— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1997-2006 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1730-1740 — 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 118 separate duplicated blocks between them, totalling at least 1796 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–11 lines × 2) crates/nono-proxy/src/reverse.rs:2013— crates/nono-proxy/src/reverse.rs:2013-2022 | crates/nono-proxy/src/reverse.rs:2042-2052 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 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:533-542 — 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.
Duplicated block (10 lines × 3) crates/nono-cli/src/command_policy.rs:2584— crates/nono-cli/src/command_policy.rs:2584-2593 | crates/nono-cli/src/command_policy.rs:2618-2627 | crates/nono-cli/src/command_policy.rs:2684-2693 — 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-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-cli/src/tool-sandbox/platform/linux.rs:2800— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2800-2809 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5228-5237 | crates/nono/src/broker_path.rs:183-192 — 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 118 separate duplicated blocks between them, totalling at least 1796 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.
nono::capability::tokenize_sexp (cyclomatic 25) crates/nono/src/capability.rs:681— 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::audit::verify_audit_attestation_bundle (cyclomatic 25) crates/nono/src/audit.rs:1123— 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::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 16) crates/nono/src/audit.rs:1434— nono::audit::verify_audit_log 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.
DiagnosticFormatter::format_consolidated_denial_guidance (cognitive 46) crates/nono-cli/src/diagnostic/formatter.rs:1707— 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 36) crates/nono-cli/src/diagnostic/formatter.rs:1250— DiagnosticFormatter::format_supervised_footer_with_diagnostics has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 9 (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 26) crates/nono-cli/src/diagnostic/formatter.rs:991— DiagnosticFormatter::format_exit_explanation has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (23 pts), match/switch 2 (3 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DiagnosticFormatter::format_network_denial_guidance (cognitive 18) crates/nono-cli/src/diagnostic/formatter.rs:2109— 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.
TooManyFields: PreparedSandbox crates/nono-cli/src/sandbox_prepare.rs:506— TooManyFields — 45 stored fields. The bar is 30 stored fields; this is 15 over it, 1.50× 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 — 38 stored fields. The bar is 30 stored fields; this is 8 over it, 1.27× 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 — 33 stored fields. 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: WrapSandboxArgs crates/nono-cli/src/cli.rs:1636— 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.
Duplicated block (20 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2736— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2736-2755 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5192-5211 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (20 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2818— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2818-2837 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5246-5265 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (20 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5359— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5359-5378 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4518-4537 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (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:410-429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–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.
Duplicated block (17–18 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:546— crates/nono-cli/src/tool-sandbox/platform/linux.rs:546-562 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:476-493 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:3586— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3586-3603 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3068-3084 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:4484— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4484-4500 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3920-3937 — 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 118 separate duplicated blocks between them, totalling at least 1796 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/diagnostic/formatter.rs:125— crates/nono-cli/src/diagnostic/formatter.rs:125-138 | crates/nono-cli/src/output.rs:1271-1285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14–15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:306— crates/nono-cli/src/tool-sandbox/platform/linux.rs:306-319 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:309-323 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:2263— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2263-2277 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4675-4688 — 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 118 separate duplicated blocks between them, totalling at least 1796 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-proxy/src/reverse.rs:572— crates/nono-proxy/src/reverse.rs:572-585 | crates/nono-proxy/src/reverse.rs:1485-1499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 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.
Duplicated block (7 lines × 3) crates/nono-proxy/src/tls_intercept/handle.rs:1278— crates/nono-proxy/src/tls_intercept/handle.rs:1278-1284 | crates/nono-proxy/src/tls_intercept/handle.rs:1535-1541 | crates/nono-proxy/src/tls_intercept/handle.rs:1775-1781 — 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 (7 lines × 3) crates/nono-cli/src/output.rs:638— crates/nono-cli/src/output.rs:638-644 | crates/nono-cli/src/output.rs:706-715 | crates/nono-cli/src/output.rs:739-745 — 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 (7 lines × 3) crates/nono-proxy/src/reverse.rs:2428— crates/nono-proxy/src/reverse.rs:2428-2434 | crates/nono-proxy/src/reverse.rs:2539-2545 | crates/nono-proxy/src/reverse.rs:2549-2555 — 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.
DiagnosticFormatter::format_supervised_footer_with_diagnostics (cyclomatic 25) crates/nono-cli/src/diagnostic/formatter.rs:1250— DiagnosticFormatter::format_supervised_footer_with_diagnostics 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_consolidated_denial_guidance (cyclomatic 25) crates/nono-cli/src/diagnostic/formatter.rs:1707— 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 22) crates/nono-cli/src/diagnostic/formatter.rs:991— DiagnosticFormatter::format_exit_explanation 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.
PtyProxy::try_accept (cognitive 34) crates/nono-cli/src/pty_proxy.rs:552— PtyProxy::try_accept has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 5 (10 pts), boolean chains 1 (nesting depth added 18). 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:1214— 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:810— 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.
TooManyMethods: CapabilitySet crates/nono/src/capability.rs:951— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× 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: DiagnosticFormatter crates/nono-cli/src/diagnostic/formatter.rs:634— TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PtyProxy crates/nono-cli/src/pty_proxy.rs:263— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
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:2817— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2817-2837 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2844-2901 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5245-5265 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5272-5329 — 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:2431— crates/nono/src/sandbox/linux.rs:2431-2461 | crates/nono/src/sandbox/linux.rs:2542-2565 | crates/nono/src/sandbox/linux.rs:3569-3702 | crates/nono/src/sandbox/linux.rs:3721-3757 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (23 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2673— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2673-2695 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5095-5117 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (23 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1432— crates/nono-cli/src/tool-sandbox/platform/macos.rs:1432-1454 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1536-1558 — both copies are in the same file, so extract the 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 (23 lines × 2) tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:46— tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:46-68 | tool-sandbox-examples/kubernetes/make-proxy-kubeconfig.py:46-68 — `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 3 separate duplicated blocks between them, totalling at least 73 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. Read the line range as the matched WINDOW rather than a finished unit: at `tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:46` 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 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.
Duplicated block (21 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1318— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1318-1338 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1032-1052 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (21 lines × 2) crates/nono-proxy/src/reverse.rs:735— crates/nono-proxy/src/reverse.rs:735-755 | crates/nono-proxy/src/reverse.rs:757-777 — both copies are in the same file, so extract the 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–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.
Duplicated block (16–17 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4168— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4168-4183 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3731-3747 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16–17 lines × 2) crates/nono-proxy/src/connect.rs:183— crates/nono-proxy/src/connect.rs:183-199 | crates/nono-proxy/src/external.rs:314-329 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 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.
Duplicated block (13 lines × 3) crates/nono-proxy/src/reverse.rs:714— crates/nono-proxy/src/reverse.rs:714-726 | crates/nono-proxy/src/reverse.rs:742-755 | crates/nono-proxy/src/reverse.rs:764-777 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) crates/nono-proxy/src/reverse.rs:1100— crates/nono-proxy/src/reverse.rs:1100-1112 | crates/nono-proxy/src/reverse.rs:1135-1147 | crates/nono-proxy/src/reverse.rs:1164-1177 — 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 (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:2951-2962 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5494-5505 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) crates/nono-proxy/src/tls_intercept/handle.rs:1437— crates/nono-proxy/src/tls_intercept/handle.rs:1437-1448 | crates/nono-proxy/src/tls_intercept/handle.rs:1462-1473 | crates/nono-proxy/src/tls_intercept/handle.rs:1760-1772 — 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 (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.
Duplicated block (11–12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1646— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1646-1657 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1353-1363 — 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 118 separate duplicated blocks between them, totalling at least 1796 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–12 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4900— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4900-4911 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4344-4354 — 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 118 separate duplicated blocks between them, totalling at least 1796 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–12 lines × 2) crates/nono-cli/src/profile_cmd.rs:1521— crates/nono-cli/src/profile_cmd.rs:1521-1532 | crates/nono-cli/src/profile_cmd.rs:1653-1663 — both copies are in the same file, so extract the 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 × 3) crates/nono-proxy/src/tls_intercept/handle.rs:1287— crates/nono-proxy/src/tls_intercept/handle.rs:1287-1297 | crates/nono-proxy/src/tls_intercept/handle.rs:1784-1794 | crates/nono-proxy/src/tls_intercept/handle.rs:1928-1938 — 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:1160— crates/nono-cli/src/exec_strategy.rs:1160-1171 | crates/nono-cli/src/exec_strategy.rs:1240-1250 | crates/nono-cli/src/exec_strategy.rs:1271-1285 — 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-proxy/src/reverse.rs:1791— crates/nono-proxy/src/reverse.rs:1791-1801 | crates/nono-proxy/src/reverse.rs:2305-2315 | crates/nono-proxy/src/reverse.rs:2323-2333 — 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 (9–10 lines × 2) crates/nono-cli/src/query_ext.rs:360— crates/nono-cli/src/query_ext.rs:360-369 | crates/nono-cli/src/query_ext.rs:458-466 — both copies are in the same file, so extract the 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–10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1556— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1556-1565 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1275-1283 — 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 118 separate duplicated blocks between them, totalling at least 1796 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–10 lines × 2) crates/nono-proxy/src/reverse.rs:2003— crates/nono-proxy/src/reverse.rs:2003-2011 | crates/nono-proxy/src/reverse.rs:2031-2040 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
PtyProxy::try_accept (cyclomatic 18) crates/nono-cli/src/pty_proxy.rs:552— PtyProxy::try_accept 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.
PtyProxy::filter_client_input (cyclomatic 17) crates/nono-cli/src/pty_proxy.rs:1214— 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.
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.
TodoComment crates/nono-cli/src/trust_cmd.rs:1519— // 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.
TodoComment crates/nono-cli/src/exec_strategy.rs:3796— /// 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.
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.
Duplicated block (32 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1748— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1748-1779 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1462-1493 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (32 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5448— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5448-5479 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4607-4638 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (30 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4677— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4677-4706 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4125-4154 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (30 lines × 2) crates/nono-cli/src/audit_commands.rs:792— crates/nono-cli/src/audit_commands.rs:792-821 | 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 136 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 (28–29 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1921— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1921-1948 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1999-2027 — both copies are in the same file, so extract the 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 (28–29 lines × 2) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1648— crates/nono-cli/src/tool-sandbox/platform/macos.rs:1648-1675 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1733-1761 — both copies are in the same file, so extract the 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 (25 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4084— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4084-4108 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3682-3706 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (25 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5302— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5302-5326 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5369-5393 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (24 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1434— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1434-1457 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1148-1171 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (24 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1425— crates/nono-proxy/src/tls_intercept/handle.rs:1425-1448 | crates/nono-proxy/src/tls_intercept/handle.rs:1450-1473 — both copies are in the same file, so extract the 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–24 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5507— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5507-5530 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5453-5473 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (21–24 lines × 2) crates/nono/src/sandbox/macos.rs:743— crates/nono/src/sandbox/macos.rs:743-766 | crates/nono/src/sandbox/macos.rs:779-799 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–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.
Duplicated block (17–19 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1900— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1900-1916 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1620-1638 — 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 118 separate duplicated blocks between them, totalling at least 1796 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–19 lines × 2) crates/nono-cli/src/session.rs:329— crates/nono-cli/src/session.rs:329-347 | crates/nono-cli/src/session.rs:381-398 — both copies are in the same file, so extract the 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 (18–19 lines × 2) crates/nono-proxy/src/reverse.rs:527— crates/nono-proxy/src/reverse.rs:527-544 | crates/nono-proxy/src/reverse.rs:818-836 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 3) crates/nono-cli/src/audit_commands.rs:810— crates/nono-cli/src/audit_commands.rs:810-826 | 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 136 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 lines × 3) crates/nono-proxy/src/tls_intercept/handle.rs:1388— crates/nono-proxy/src/tls_intercept/handle.rs:1388-1404 | crates/nono-proxy/src/tls_intercept/handle.rs:1580-1596 | crates/nono-proxy/src/tls_intercept/handle.rs:1822-1838 — 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 (15–17 lines × 2) crates/nono-cli/src/exec_strategy.rs:422— crates/nono-cli/src/exec_strategy.rs:422-438 | crates/nono-cli/src/exec_strategy.rs:629-643 — both copies are in the same file, so extract the 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–17 lines × 2) crates/nono-proxy/src/reverse.rs:2435— crates/nono-proxy/src/reverse.rs:2435-2449 | crates/nono-proxy/src/reverse.rs:2556-2572 — both copies are in the same file, so extract the 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 × 3) crates/nono-cli/src/registry_client.rs:178— crates/nono-cli/src/registry_client.rs:178-193 | crates/nono-cli/src/registry_client.rs:234-249 | crates/nono-cli/src/registry_client.rs:369-384 — 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:1461— crates/nono-cli/src/profile_cmd.rs:1461-1485 | crates/nono-cli/src/profile_cmd.rs:1500-1519 | crates/nono-cli/src/profile_cmd.rs:1704-1719 — 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 (15–16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2581— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2581-2596 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4988-5002 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (15–16 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:754— crates/nono-proxy/src/tls_intercept/handle.rs:754-768 | crates/nono-proxy/src/tls_intercept/handle.rs:785-800 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–16 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4662— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4662-4675 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4108-4123 — 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 118 separate duplicated blocks between them, totalling at least 1796 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–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.
Duplicated block (13–14 lines × 2) crates/nono/src/capability.rs:163— crates/nono/src/capability.rs:163-176 | crates/nono/src/capability.rs:534-546 — both copies are in the same file, so extract the 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–14 lines × 2) crates/nono/src/sandbox/linux.rs:886— crates/nono/src/sandbox/linux.rs:886-898 | crates/nono/src/sandbox/linux.rs:1044-1057 — both copies are in the same file, so extract the 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–14 lines × 2) crates/nono-cli/src/exec_strategy.rs:3909— crates/nono-cli/src/exec_strategy.rs:3909-3919 | crates/nono-cli/src/exec_strategy.rs:3952-3965 — both copies are in the same file, so extract the 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–14 lines × 2) crates/nono-proxy/src/oauth2.rs:216— crates/nono-proxy/src/oauth2.rs:216-229 | crates/nono-proxy/src/oauth2.rs:564-574 — both copies are in the same file, so extract the 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/tool-sandbox/platform/linux.rs:4737— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4737-4749 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4185-4195 — 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 118 separate duplicated blocks between them, totalling at least 1796 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–13 lines × 2) crates/nono-cli/src/why_runtime.rs:205— crates/nono-cli/src/why_runtime.rs:205-217 | crates/nono-cli/src/why_runtime.rs:241-251 — both copies are in the same file, so extract the 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 × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2820— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2820-2830 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2858-2868 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5248-5258 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5286-5296 — 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 118 separate duplicated blocks between them, totalling at least 1796 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:1949— crates/nono-proxy/src/tls_intercept/handle.rs:1949-1959 | crates/nono-proxy/src/tls_intercept/handle.rs:2009-2019 | crates/nono-proxy/src/tls_intercept/handle.rs:2030-2042 | crates/nono-proxy/src/tls_intercept/handle.rs:2056-2066 — 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 (8–10 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1011— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1011-1020 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:791-798 — 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 118 separate duplicated blocks between them, totalling at least 1796 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–10 lines × 2) crates/nono-proxy/src/credential.rs:90— crates/nono-proxy/src/credential.rs:90-97 | crates/nono-proxy/src/credential.rs:325-334 — both copies are in the same file, so extract the 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 × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1503— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1503-1511 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1629-1637 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1217-1225 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1337-1345 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 × 4) crates/nono-cli/src/profile_cmd.rs:1486— crates/nono-cli/src/profile_cmd.rs:1486-1494 | crates/nono-cli/src/profile_cmd.rs:1520-1528 | crates/nono-cli/src/profile_cmd.rs:1720-1728 | crates/nono-cli/src/profile_cmd.rs:1750-1758 — 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 (11 lines × 5) crates/nono-cli/src/exec_strategy.rs:1160— crates/nono-cli/src/exec_strategy.rs:1160-1170 | crates/nono-cli/src/exec_strategy.rs:1178-1188 | crates/nono-cli/src/exec_strategy.rs:1223-1236 | crates/nono-cli/src/exec_strategy.rs:1240-1250 | crates/nono-cli/src/exec_strategy.rs:1271-1284 — 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.
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.
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.
ProxyCredentialCaptureBackend::run_capture_command (cyclomatic 20) crates/nono-cli/src/proxy_runtime.rs:381— 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.
CredentialStore::load_with_diagnostics (cyclomatic 19) crates/nono-proxy/src/credential.rs:222— CredentialStore::load_with_diagnostics 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.
EffectiveDenyPolicy::keychain_child_deny_rules (cyclomatic 16) crates/nono-cli/src/policy.rs:1224— 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.
DaemonPidLineage::attribute_with_negative_ttl (cyclomatic 16) crates/nono-cli/src/tool-sandbox/platform/macos.rs:2162— 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.
CredentialStore::load_with_diagnostics (cognitive 45) crates/nono-proxy/src/credential.rs:222— CredentialStore::load_with_diagnostics has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (23 pts), match/switch 6 (21 pts), loops 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.
DetachMatcher::push (cognitive 32) crates/nono-cli/src/connect_client.rs:1826— DetachMatcher::push has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (27 pts), match/switch 1 (3 pts), boolean chains 1, loops 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.
EffectiveDenyPolicy::keychain_child_deny_rules (cognitive 29) crates/nono-cli/src/policy.rs:1224— 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.
ProxyCredentialCaptureBackend::run_capture_command (cognitive 22) crates/nono-cli/src/proxy_runtime.rs:381— 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.
DaemonPidLineage::attribute_with_negative_ttl (cognitive 21) crates/nono-cli/src/tool-sandbox/platform/macos.rs:2162— 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.
ProxyHandle::route_diagnostics (cognitive 19) crates/nono-proxy/src/server.rs:402— 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.
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.
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.
OAuthCaptureStore::rewrite_response_body (cognitive 17) crates/nono-proxy/src/oauth_capture/rewrite.rs:127— OAuthCaptureStore::rewrite_response_body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (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.
RouteStore::load (cognitive 16) crates/nono-proxy/src/route.rs:206— RouteStore::load has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (298 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1271— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1271-2051 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:978-1785 — These two members are variants of one another: 298 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.
Near-duplicate member pair (54 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4639— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4639-4706 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4082-4154 — 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.
Near-duplicate member pair (45 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4431— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4431-4537 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3875-3978 — These two members are variants of one another: 45 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.
Near-duplicate member pair (39 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:266— crates/nono-cli/src/tool-sandbox/platform/linux.rs:266-431 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:276-392 — These two members are variants of one another: 39 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.
Near-duplicate member pair (37 shared lines) crates/nono-proxy/src/tls_intercept/handle.rs:1418— crates/nono-proxy/src/tls_intercept/handle.rs:1418-1596 | crates/nono-proxy/src/tls_intercept/handle.rs:1681-1838 — 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.
Near-duplicate member pair (33 shared lines) crates/nono/src/sandbox/linux.rs:1414— crates/nono/src/sandbox/linux.rs:1414-1487 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:3337-3418 — These two members are variants of one another: 33 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.
Near-duplicate member pair (27 shared lines) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2254— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2254-2306 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4667-4711 — 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· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) crates/nono-cli/src/sandbox_state.rs:247— crates/nono-cli/src/sandbox_state.rs:247-281 | crates/nono-cli/src/session.rs:803-835 — 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 (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) crates/nono-cli/src/profile_cmd.rs:2042— crates/nono-cli/src/profile_cmd.rs:2042-2180 | crates/nono-cli/src/profile_cmd.rs:2185-2206 — 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· 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:1126— crates/nono-cli/src/command_policy.rs:1126-1142 | crates/nono-cli/src/command_policy.rs:3451-3458 | crates/nono-cli/src/command_policy.rs:3463-3470 | crates/nono-cli/src/command_policy.rs:3475-3482 | crates/nono-cli/src/profile/mod.rs:3719-3977 | crates/nono-cli/src/profile/mod.rs:3982-3989 — 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.
Duplicated block (64–65 lines × 2) crates/nono-cli/src/query_ext.rs:263— crates/nono-cli/src/query_ext.rs:263-327 | crates/nono-cli/src/query_ext.rs:374-437 — both copies are in the same file, so extract the 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 (61 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1144— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1144-1204 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:835-895 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (56 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:2846— crates/nono-cli/src/tool-sandbox/platform/linux.rs:2846-2901 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:5274-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 118 separate duplicated blocks between them, totalling at least 1796 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 (47 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4758— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4758-4804 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4204-4250 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (44 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:3997— crates/nono-cli/src/tool-sandbox/platform/linux.rs:3997-4040 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3595-3638 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (39–40 lines × 2) crates/nono-cli/src/exec_strategy.rs:3390— crates/nono-cli/src/exec_strategy.rs:3390-3429 | crates/nono-cli/src/exec_strategy.rs:3456-3494 — both copies are in the same file, so extract the 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 (38–40 lines × 2) crates/nono-cli/src/audit_commands.rs:1092— crates/nono-cli/src/audit_commands.rs:1092-1129 | crates/nono-cli/src/terminal_approval.rs:140-179 — 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 (38 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:4256— crates/nono-cli/src/tool-sandbox/platform/linux.rs:4256-4293 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:3819-3856 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (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 136 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 (30–34 lines × 2) crates/nono-cli/src/profile_save_runtime.rs:1080— crates/nono-cli/src/profile_save_runtime.rs:1080-1113 | crates/nono-cli/src/terminal_prompt.rs:61-90 — 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 (34 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5412— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5412-5445 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4571-4604 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (31–34 lines × 2) crates/nono-proxy/src/server.rs:1481— crates/nono-proxy/src/server.rs:1481-1514 | crates/nono-proxy/src/server.rs:1633-1663 — both copies are in the same file, so extract the 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 (3–30 lines × 4) crates/nono-cli/src/profile_cmd.rs:1455— crates/nono-cli/src/profile_cmd.rs:1455-1484 | crates/nono-cli/src/profile_cmd.rs:1698-1718 | crates/nono-cli/src/profile_cmd.rs:1833-1835 | crates/nono-cli/src/profile_cmd.rs:1862-1864 — 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 (29 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:5381— crates/nono-cli/src/tool-sandbox/platform/linux.rs:5381-5409 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:4540-4568 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (27–28 lines × 2) crates/nono-proxy/src/reverse.rs:333— crates/nono-proxy/src/reverse.rs:333-360 | crates/nono-proxy/src/reverse.rs:362-388 — both copies are in the same file, so extract the 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 (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.
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 (20–22 lines × 2) crates/nono-proxy/src/reverse.rs:1135— crates/nono-proxy/src/reverse.rs:1135-1154 | crates/nono-proxy/src/reverse.rs:1164-1185 — both copies are in the same file, so extract the 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 (20–21 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1714— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1714-1733 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1813-1832 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1886-1905 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1974-1994 — 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 (18–21 lines × 2) crates/nono-cli/src/trust_cmd.rs:910— crates/nono-cli/src/trust_cmd.rs:910-930 | crates/nono-cli/src/trust_cmd.rs:1036-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.
Duplicated block (12–21 lines × 2) crates/nono-proxy/src/oauth2.rs:259— crates/nono-proxy/src/oauth2.rs:259-279 | crates/nono-proxy/src/oauth2.rs:596-607 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 4) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1421— crates/nono-cli/src/tool-sandbox/platform/macos.rs:1421-1440 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1525-1544 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1606-1625 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1702-1721 — 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 (19–20 lines × 2) crates/nono-proxy/src/tls_intercept/handle.rs:1381— crates/nono-proxy/src/tls_intercept/handle.rs:1381-1400 | crates/nono-proxy/src/tls_intercept/handle.rs:1816-1834 — both copies are in the same file, so extract the 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–17 lines × 3) crates/nono-proxy/src/server.rs:1495— crates/nono-proxy/src/server.rs:1495-1509 | crates/nono-proxy/src/server.rs:1644-1658 | crates/nono-proxy/src/tls_intercept/handle.rs:320-336 — 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.
Duplicated block (15–16 lines × 4) crates/nono-cli/src/tool-sandbox/platform/macos.rs:1505— crates/nono-cli/src/tool-sandbox/platform/macos.rs:1505-1519 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1586-1600 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1683-1697 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1769-1784 — 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 (15–16 lines × 3) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1791— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1791-1805 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:1956-1970 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:2035-2050 — 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 (9–15 lines × 2) crates/nono-cli/src/tool-sandbox/platform/linux.rs:1541— crates/nono-cli/src/tool-sandbox/platform/linux.rs:1541-1549 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:1255-1269 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (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.
Duplicated block (12–14 lines × 2) crates/nono-proxy/src/reverse.rs:487— crates/nono-proxy/src/reverse.rs:487-498 | crates/nono-proxy/src/reverse.rs:2810-2823 — both copies are in the same file, so extract the 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–12 lines × 3) crates/nono-proxy/src/reverse.rs:2439— crates/nono-proxy/src/reverse.rs:2439-2448 | crates/nono-proxy/src/reverse.rs:2560-2571 | crates/nono-proxy/src/reverse.rs:2704-2711 — 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 (9–11 lines × 2) crates/nono-cli/src/profile/mod.rs:3251— crates/nono-cli/src/profile/mod.rs:3251-3259 | crates/nono-cli/src/profile/mod.rs:3385-3395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 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.
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.
Duplicated block (7–9 lines × 2) crates/nono-cli/src/trust_cmd.rs:1180— crates/nono-cli/src/trust_cmd.rs:1180-1186 | crates/nono-cli/src/trust_cmd.rs:1241-1249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 4) crates/nono-cli/src/tool-sandbox/platform/linux.rs:955— crates/nono-cli/src/tool-sandbox/platform/linux.rs:955-961 | crates/nono-cli/src/tool-sandbox/platform/linux.rs:967-973 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:768-774 | crates/nono-cli/src/tool-sandbox/platform/macos.rs:780-786 — 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 118 separate duplicated blocks between them, totalling at least 1796 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 (3–5 lines × 6) crates/nono-cli/src/command_policy.rs:1135— crates/nono-cli/src/command_policy.rs:1135-1137 | crates/nono-cli/src/command_policy.rs:3454-3458 | crates/nono-cli/src/command_policy.rs:3466-3470 | crates/nono-cli/src/command_policy.rs:3478-3482 | crates/nono-cli/src/profile/mod.rs:3892-3894 | crates/nono-cli/src/profile/mod.rs:3985-3989 — 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.
Duplicated block (20 lines × 3) crates/nono-cli/src/profile/mod.rs:491— crates/nono-cli/src/profile/mod.rs:491-510 | crates/nono-cli/src/proxy_runtime.rs:1268-1287 | crates/nono-proxy/src/tls_intercept/http1.rs:51-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (13 lines × 4) crates/nono-proxy/src/reverse.rs:1070— crates/nono-proxy/src/reverse.rs:1070-1082 | crates/nono-proxy/src/reverse.rs:1100-1112 | crates/nono-proxy/src/reverse.rs:1135-1147 | crates/nono-proxy/src/reverse.rs:1165-1177 — 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 (11 lines × 7) crates/nono-cli/src/exec_strategy.rs:1039— crates/nono-cli/src/exec_strategy.rs:1039-1051 | crates/nono-cli/src/exec_strategy.rs:1121-1133 | crates/nono-cli/src/exec_strategy.rs:1159-1169 | crates/nono-cli/src/exec_strategy.rs:1177-1187 | crates/nono-cli/src/exec_strategy.rs:1223-1235 | crates/nono-cli/src/exec_strategy.rs:1239-1249 | crates/nono-cli/src/exec_strategy.rs:1271-1283 — 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.
D4 · Code Duplication· Edited copy of a member (88 corresponding lines) · ×1
Edited copy of a member (88 corresponding lines) 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 — These two members are one piece of code written twice and then edited apart: 88 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (3–5 lines × 4) crates/nono/src/sandbox/linux.rs:2432— crates/nono/src/sandbox/linux.rs:2432-2436 | crates/nono/src/sandbox/linux.rs:2543-2547 | crates/nono/src/sandbox/linux.rs:3580-3582 | crates/nono/src/sandbox/linux.rs:3731-3733 — 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 (40 lines × 2) tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:94— tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:94-133 | tool-sandbox-examples/kubernetes/make-proxy-kubeconfig.py:94-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 3 separate duplicated blocks between them, totalling at least 73 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. Read the line range as the matched WINDOW rather than a finished unit: at `tool-sandbox-examples/kubernetes-with-approval/make-proxy-kubeconfig.py:94` 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 (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 101 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.
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.
Low cohesion: CapabilitySet (LCOM4 12) crates/nono/src/capability.rs:951— 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.
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/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/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/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.
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/tool-sandbox/platform/macos.rs:2810— `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/sandbox_prepare.rs:282— `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-proxy/src/server.rs:421— `route_diagnostics` turns every `Err` into `true` — 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.
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/command_runtime.rs:452— `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-cli/src/audit_session.rs:251— `session_id.contains(std::path::MAIN_SEPARATOR) || session_id.contains('/') || session_id.contains("..") || session_id.contains('\0')` appears character-identically in 2 files — crates/nono-cli/src/audit_session.rs, crates/nono-cli/src/rollback_session.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.
Subsumed condition operand crates/nono-proxy/src/route.rs:1954— `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:11175— `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/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.
Documentation: no project overview README.md— The root README is a marketing banner with no description of what nono does or what it is for. Replace the centered logo and boilerplate links with an overview paragraph explaining that nono provides capability-based OS-enforced sandboxing, its security goals (secure attestation), and which tools it protects.
Documentation: no contributor guidance README.md— The root README gives no contribution guidance. Link to the repository's CONTRIBUTING doc or add a short PR/bug-reporting note.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 10 significant file(s) lose their only recent owner: crates/nono-cli/src/connect_client.rs, crates/nono/src/trust/signing.rs, crates/nono-cli/src/platform.rs, crates/nono-cli/src/platform_client.rs, crates/nono/src/undo/object_store.rs, crates/nono/src/undo/merkle.rs, crates/nono-proxy/src/oauth_capture/persist.rs, crates/nono-proxy/src/approval.rs (+2 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 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 (16 single-owned of 192 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 192 of the 205 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.
Split crates/nono-cli — The cli is huge and sprawls across seven namespaces (profile, config, tool-sandbox), a classic grab-bag. Suggested: split into focused sub-commands or tools over the listed namespaces
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 1 of 192 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 and example/demo trees and test files identified by path convention, largest first; 192 of the 205 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-cli/src/deprecation_warnings.rs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No seccomp profile — Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No AppArmor/SELinux confinement — Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
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.
README/code drift — README claims nono runs on macOS, Linux, WSL2; the evidence has no such claim — reported by the model that read the README against this repository; no term search was run for this one, so nothing here has been checked against the tree. Treat it as a reading to confirm, not as a measured contradiction: verify it against the code before acting on it, and if the footprint it describes does exist, this row is wrong.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 205/262 types (78%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
Logging is not universal — Only 3/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`.
No security response headers detected testdata/spire/server.conf:1— No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. This is reported because `server.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
Outdated: aws-sigv4 — `aws-sigv4` is locked at 1.5.1 but 1.6.0 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-sigv4` and commit the updated Cargo.lock.
Outdated: clap_complete — `clap_complete` is locked at 4.6.9 but 4.6.11 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/nono-cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap_complete` and commit the updated Cargo.lock.
Outdated: der — `der` is locked at 0.8.1 but 0.8.2 is the current stable release on crates.io, and it already satisfies the `"0.8"` requirement declared in crates/nono/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p der` and commit the updated Cargo.lock.
Outdated: tokio-rustls — `tokio-rustls` is locked at 0.26.5 but 0.26.6 is the current stable release on crates.io, and it already satisfies the `"0.26"` requirement declared in crates/nono-proxy/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio-rustls` and commit the updated Cargo.lock.
Outdated: ureq — `ureq` is locked at 3.4.1 but 3.4.2 is the current stable release on crates.io, and it already satisfies the `"3"` 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 Cargo.lock.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
Run 01a0f35c-d299-71ce-9f93-da84e2a46edb · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 14 · Warnings: 885 · Recommendations: 36 · Info: 5 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 30-09-2026 @ 17:29 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.