Public report — Sharpino, published 4 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
371findings with an exact file:lineof 404 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
23/94dimensions across the health lenses10882 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
tonyx/Sharpino is sound in substance but carries real gaps (53%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (86%) — the structure is clean and changes stay contained. Security (86%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (35%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Code Health (57%) is the next concern — changes there are slower and more error-prone.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); Keep a changelog (e.g. Keep-a-Changelog) recording what shipped… (Release Hygiene); approval/environment gate (required reviewers / protection… (Deployment & Rollback).
For scale: Small (~10,882 production lines); rebuilding it from scratch would take roughly ~0.3 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (86%); the priorities above are the highest-leverage way to bring the rest up to that level.
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.
294 finding(s) are new versus the previous scan (2026-07-29) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.
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.
0.7× (at 53% quality) — the last 20% of quality is most of the work
Size & shape
Small · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.3 person-years of build effort (about ~€48,000 to rebuild). Its weakest lens is Readiness at 35% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — domain model × a 0.7× 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
Add a CI workflow that builds and runs the test suite on every push/PR.
Value concentrated against a weak lens · High · Value at risk
This is a Small asset (~0.3 person-years to rebuild), and its weakest lens is Readiness at 35%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
The top fix pays for itself · High · Economics
The top-ranked fix costs roughly 3–10 engineer-days once. Not doing it costs about 30.8–184.7 engineer-days every year, paid as drag on the ~166,813 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–4 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 7–17% 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: 41,132 line(s) changed over a 90-day window ⇒ ~166,813/year · D1/D2/D4 code quality: averaging 5.0/10 ⇒ a 7–17% 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 4 months.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 5.0/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 7–17% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4 code quality: averaging 5.0/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 matrix
62 modules, 25 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. 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.)
At a glance — Code Health · 57% · Adequate · gated by D4
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
A06:2021 — Vulnerable & Outdated Components
14
High / Critical
A03:2021 — Injection
1
High / Critical
Roadmap
First, establish a CI workflow that builds and runs the test suite on every push or pull request to ensure code quality. Next, maintain a changelog to track what ships in each release, while adding approval gates before promoting to production. Then, document significant architectural decisions in a dedicated ADR format to preserve context and consequences. Finally, update the root README with a build and run quick-start section to help newcomers get started.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a CI workflow that builds and runs the test suite on every push/PR.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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. 22 of 23 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 1 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — 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 — 23 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, 371 of 404 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.
D19 Documentation Quality — 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.
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 (jscpd) — 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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.
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.
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 the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
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.
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 (2): D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These 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.
Resolve the 4 Main.main (cyclomatic 60) finding(s) in Cyclomatic Complexity — start with Program.fs (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Main.main (cyclomatic 57) finding(s) in Cyclomatic Complexity — start with Program.fs. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Main.main (cognitive 105) finding(s) in Cognitive Complexity — start with Program.fs (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Main.main (cognitive 101) finding(s) in Cognitive Complexity — start with Program.fs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 AggregateCache3.SetupL2AndBackplane (cognitive 36) finding(s) in Cognitive Complexity — start with Cache.fs. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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 Classes7.7 / 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.
Resolve the 6 FileTooLong finding(s) in God Classes — start with CommandHandler.fs, PgBinaryEventStore.fs, PgEventStore.fs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 TooManyMethods finding(s) in God Classes — start with CommandHandler.fs, PgBinaryEventStore.fs, PgEventStore.fs. — One of this dimension's main actionable groups (5 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
+ 68 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 22 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with PgEventStore.fs (10), Consumer.fs (4), PgBinaryEventStore.fs (2). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 22 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with PgEventStore.fs (5), CommandHandler.fs (4), Commands.fs (4). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 22 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with CommandHandler.fs (8), Cache.fs (3), StateView.fs (3). — One of this dimension's main actionable groups (22 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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.
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: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
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.
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; coupling through a build step, config, or non-source file isn't seen.
Resolve the 7 Change coupling finding(s) in Change Coupling — start with Events.fs (3), Context.fs (3), Commands.fs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with Categories.fs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×3Sharpino.Sample.Client/package-lock.jsondetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×2Sharpino.Sample.Client/package-lock.jsondetected by osv-scanner finding
Medium vulnerability: [GHSA redacted]Sharpino.Sample.Client/package-lock.jsondetected by osv-scanner finding
Low CVE: [GHSA redacted]Sharpino.Sample.Client/package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 3 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Medium vulnerability finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
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 a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
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.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
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.
No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build.
What to do
Run what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
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.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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.
Not included — 71 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 — Frontend below the scale floor (12 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (12 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (12 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (12 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (12 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (12 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (12 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
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
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
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.
D10 Test Quality — ~32275 lines of test source are present (.fs) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (package.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
D19 Documentation Quality — LLM evaluation failed
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.fs, .py) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. 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 — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .fs, .py, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured
D9 Test Distribution — Test source is present (.fs) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this check looks for (26 event handler(s))
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this check looks for (an append-only event-store seam (IEventStore/Append-of-events))
GD1 Unfinished & placeholder code — no source files
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 — no CI workflow found
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, 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
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from 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
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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
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
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
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.
Issue — 6 finding(s)
D38 · OSV Dependency Vulnerabilities· High CVE · ×3
High CVE: [GHSA redacted] Sharpino.Sample.Client/package-lock.json— postcss 8.4.34: [GHSA redacted] — postcss is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin postcss to 8.5.12 with an `overrides` entry). This is 1 of 4 advisories with a published fix this scan raises against postcss 8.4.34, and their fixed versions do not agree — anything below 8.5.23 still leaves at least one of them open. Take this package to 8.5.23 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against postcss 8.4.34: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] Sharpino.Sample.Client/package-lock.json— rollup 3.29.4: [GHSA redacted] — rollup is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin rollup to 3.29.5 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against rollup 3.29.4, and their fixed versions do not agree — anything below 3.30.0 still leaves at least one of them open. Take this package to 3.30.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against rollup 3.29.4: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] Sharpino.Sample.Client/package-lock.json— vite 4.5.2: [GHSA redacted] — upgrade to 5.4.9. This is 1 of 16 advisories with a published fix this scan raises against vite 4.5.2, and their fixed versions do not agree — anything below 4.5.14 still leaves at least one of them open. Take this package to 4.5.14 or later: that is the floor for the package, not this row's target alone. This one row stands for the 16 advisories this scan raises against vite 4.5.2: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High: npm-missing-minimum-release-age Sharpino.Sample.Client/.npmrc:1— This .npmrc does not set a minimum release age or sets it too low. Newly published packages can be malicious or unstable. Add a minimum release age (`min-release-age = 7` for the npm CLI, `minimum-release-age = 7` for pnpm, `minimumReleaseAge` in `pnpm-workspace.yaml`, or `npmMinimalAgeGate: 7d` in `.yarnrc.yml` for Yarn Berry) — use the key your package manager reads; Yarn Classic has no release-age setting, so pin exact versions and review lockfile bumps there instead to wait 7 days before resolving newly published package versions. Added in: v11.10 Reference: https://github.blog/changelog/2026-02-18-npm-bulk-trusted-publishing-config-and-script-security-now-generally-available/. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is.
High CVE: System.Formats.Asn1 5.0.0 — System.Formats.Asn1 5.0.0 (transitive) has a High advisory; affects 10 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:480— Sharpino.Lib/PgEventStore.fs:480-495 | Sharpino.Lib/PgBinaryEventStore.fs:508-523 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:480` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:1382— Sharpino.Lib/PgEventStore.fs:1382-1397 | Sharpino.Lib/PgBinaryEventStore.fs:1349-1365 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1382` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:1810— Sharpino.Lib/PgEventStore.fs:1810-1825 | Sharpino.Lib/PgBinaryEventStore.fs:1810-1825 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:2140— Sharpino.Lib/PgEventStore.fs:2140-2155 | Sharpino.Lib/PgBinaryEventStore.fs:2269-2284 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:2268— Sharpino.Lib/PgEventStore.fs:2268-2283 | Sharpino.Lib/PgBinaryEventStore.fs:2385-2400 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2268` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:2504— Sharpino.Lib/PgEventStore.fs:2504-2519 | Sharpino.Lib/PgBinaryEventStore.fs:2653-2668 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2504` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:2531— Sharpino.Lib/PgEventStore.fs:2531-2546 | Sharpino.Lib/PgBinaryEventStore.fs:2680-2695 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2531` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:2629— Sharpino.Lib/PgEventStore.fs:2629-2644 | Sharpino.Lib/PgBinaryEventStore.fs:2233-2248 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2629` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Lib/PgEventStore.fs:2666— Sharpino.Lib/PgEventStore.fs:2666-2681 | Sharpino.Lib/PgEventStore.fs: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 (16 lines × 2) Sharpino.Lib/PgEventStore.fs:2786— Sharpino.Lib/PgEventStore.fs:2786-2801 | Sharpino.Lib/PgBinaryEventStore.fs:2766-2781 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1863— Sharpino.Lib/PgBinaryEventStore.fs:1863-1878 | Sharpino.Lib/PgBinaryEventStore.fs:1922-1937 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1863` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2128— Sharpino.Lib/PgBinaryEventStore.fs:2128-2143 | Sharpino.Lib/PgBinaryEventStore.fs:2156-2171 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:4212— Sharpino.Lib/CommandHandler.fs:4212-4227 | Sharpino.Lib/CommandHandler.fs:4361-4376 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:4212` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Sample.11/Models/Course/Course.fs:42— Sharpino.Sample.11/Models/Course/Course.fs:42-57 | Sharpino.Sample.14/Models/Course/Course.fs:41-56 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) Sharpino.Sample.11/Models/Course/Consumer.fs:65— Sharpino.Sample.11/Models/Course/Consumer.fs:65-80 | Sharpino.Sample.14/Models/Course/Consumer.fs:65-80 — 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 (16 lines × 2) Sharpino.Sample.11/Models/Student/Consumer.fs:44— Sharpino.Sample.11/Models/Student/Consumer.fs:44-59 | Sharpino.Sample.14/Models/Student/Consumer.fs:44-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.11/Models/Student/Consumer.fs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Sample.16/Models/Products/Product.fs:1— Sharpino.Sample.16/Models/Products/Product.fs:1-16 | Sharpino.Sample.17/Models/Products/Product.fs:1-16 — 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 (16 lines × 2) Sharpino.Sample.16/MaterialManager.fs:30— Sharpino.Sample.16/MaterialManager.fs:30-45 | Sharpino.Sample.17/MaterialManager.fs:45-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.16/MaterialManager.fs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:87— Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:87-102 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:86-101 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs` are the same file name in two sibling directories, 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 41 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 `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Sample/AppVersions.fs:102— Sharpino.Sample/AppVersions.fs:102-117 | Sharpino.Sample/AppVersions.fs:153-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample/AppVersions.fs:102` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:71— Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:71-86 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:78-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs:1— Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs:1-16 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:1-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Sharpino.Lib/PgEventStore.fs:714— Sharpino.Lib/PgEventStore.fs:714-726 | Sharpino.Lib/PgBinaryEventStore.fs:878-890 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) Sharpino.Lib/PgEventStore.fs:1092— Sharpino.Lib/PgEventStore.fs:1092-1104 | Sharpino.Lib/PgEventStore.fs:1506-1519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1092` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Lib/PgEventStore.fs:1138— Sharpino.Lib/PgEventStore.fs:1138-1150 | Sharpino.Lib/PgBinaryEventStore.fs:1156-1168 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Lib/PgEventStore.fs:1235— Sharpino.Lib/PgEventStore.fs:1235-1247 | Sharpino.Lib/PgEventStore.fs:2485-2497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1235` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Lib/PgEventStore.fs:2606— Sharpino.Lib/PgEventStore.fs:2606-2618 | Sharpino.Lib/PgBinaryEventStore.fs:2103-2115 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2606` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:136— Sharpino.Lib/PgBinaryEventStore.fs:136-148 | Sharpino.Lib/PgBinaryEventStore.fs:378-390 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:613— Sharpino.Lib/PgBinaryEventStore.fs:613-625 | Sharpino.Lib/PgBinaryEventStore.fs:676-688 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:613` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1111— Sharpino.Lib/PgBinaryEventStore.fs:1111-1123 | Sharpino.Lib/PgBinaryEventStore.fs:1522-1535 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Lib/MemoryStorage.fs:348— Sharpino.Lib/MemoryStorage.fs:348-360 | Sharpino.Lib/MemoryStorage.fs:1022-1034 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:1723— Sharpino.Lib/CommandHandler.fs:1723-1736 | Sharpino.Lib/CommandHandler.fs:1825-1837 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1723` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Lib/CommandHandler.fs:3139— Sharpino.Lib/CommandHandler.fs:3139-3151 | Sharpino.Lib/CommandHandler.fs:3215-3227 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:3691— Sharpino.Lib/CommandHandler.fs:3691-3703 | Sharpino.Lib/CommandHandler.fs:3917-3929 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:3995— Sharpino.Lib/CommandHandler.fs:3995-4008 | Sharpino.Lib/CommandHandler.fs:4507-4519 — both copies are in the same file, so extract the 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) Sharpino.Sample.10/Models/Counter/Consumer.fs:1— Sharpino.Sample.10/Models/Counter/Consumer.fs:1-13 | Sharpino.Sample.10/Models/Account/Consumer.fs:1-13 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Sharpino.Sample.11/Test2.fs:269— Sharpino.Sample.11/Test2.fs:269-281 | Sharpino.Sample.11/Test2.fs:483-495 — both copies are in the same file, so extract the 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) Sharpino.Sample.16/Models/Materials/Events.fs:1— Sharpino.Sample.16/Models/Materials/Events.fs:1-13 | Sharpino.Sample.17/Models/Materials/Events.fs:1-13 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Sharpino.Sample.16/Models/Materials/Commands.fs:3— Sharpino.Sample.16/Models/Materials/Commands.fs:3-15 | Sharpino.Sample.17/Models/Materials/Commands.fs:3-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Sharpino.Sample.16/Models/WorkOrders/Commands.fs:1— Sharpino.Sample.16/Models/WorkOrders/Commands.fs:1-13 | Sharpino.Sample.17/Models/WorkOrders/Commands.fs:1-13 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Sharpino.Sample.8/Domain/Site/Consumer.fs:58— Sharpino.Sample.8/Domain/Site/Consumer.fs:58-70 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:69-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.8/Domain/Site/Consumer.fs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:44— Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:44-56 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:44-56 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs` are the same file name in two sibling directories, 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 41 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 (13 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Commands.fs:38— Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Commands.fs:38-50 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Commands.fs:38-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Commands.fs:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Commands.fs:36— Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Commands.fs:36-48 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/Commands.fs:35-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Commands.fs:36` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sharpino.Lib/PgEventStore.fs:24— Sharpino.Lib/PgEventStore.fs:24-31 | Sharpino.Lib/PgBinaryEventStore.fs:23-30 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 2) Sharpino.Lib/PgEventStore.fs:868— Sharpino.Lib/PgEventStore.fs:868-875 | Sharpino.Lib/PgBinaryEventStore.fs:705-712 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:630— Sharpino.Lib/PgBinaryEventStore.fs:630-637 | Sharpino.Lib/PgBinaryEventStore.fs:697-704 — both copies are in the same file, so extract the 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) Sharpino.Lib/Cache.fs:234— Sharpino.Lib/Cache.fs:234-241 | Sharpino.Lib/Cache.fs:306-313 — both copies are in the same file, so extract the 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) Sharpino.Lib/Cache.fs:258— Sharpino.Lib/Cache.fs:258-265 | Sharpino.Lib/Cache.fs:580-587 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) Sharpino.Lib/Cache.fs:309— Sharpino.Lib/Cache.fs:309-316 | Sharpino.Lib/Cache.fs:507-514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/Cache.fs:309` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sharpino.Lib/StateView.fs:399— Sharpino.Lib/StateView.fs:399-406 | Sharpino.Lib/StateView.fs:509-516 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:630— Sharpino.Lib/StateView.fs:630-637 | Sharpino.Lib/StateView.fs:657-664 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:894— Sharpino.Lib/StateView.fs:894-902 | Sharpino.Lib/StateView.fs:918-925 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:894` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sharpino.Lib/RabbitMq.fs:197— Sharpino.Lib/RabbitMq.fs:197-204 | Sharpino.Lib/RabbitMq.fs:256-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/RabbitMq.fs:197` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sharpino.Lib/RabbitMq.fs:215— Sharpino.Lib/RabbitMq.fs:215-222 | Sharpino.Lib/RabbitMq.fs:277-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/RabbitMq.fs:215` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) Sharpino.Lib/CommandHandler.fs:399— Sharpino.Lib/CommandHandler.fs:399-406 | Sharpino.Lib/CommandHandler.fs:532-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:399` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sharpino.Lib/CommandHandler.fs:641— Sharpino.Lib/CommandHandler.fs:641-648 | Sharpino.Lib/CommandHandler.fs:877-884 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:641` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sharpino.Lib/CommandHandler.fs:1207— Sharpino.Lib/CommandHandler.fs:1207-1215 | Sharpino.Lib/CommandHandler.fs:1280-1287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) Sharpino.Lib/CommandHandler.fs:1243— Sharpino.Lib/CommandHandler.fs:1243-1250 | Sharpino.Lib/CommandHandler.fs:1983-1990 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:3682— Sharpino.Lib/CommandHandler.fs:3682-3689 | Sharpino.Lib/CommandHandler.fs:3908-3915 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) Sharpino.Lib/CommandHandler.fs:4020— Sharpino.Lib/CommandHandler.fs:4020-4027 | Sharpino.Lib/CommandHandler.fs:4531-4538 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:4154— Sharpino.Lib/CommandHandler.fs:4154-4162 | Sharpino.Lib/CommandHandler.fs:5671-5678 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:4293— Sharpino.Lib/CommandHandler.fs:4293-4300 | Sharpino.Lib/CommandHandler.fs:4442-4449 — both copies are in the same file, so extract the 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) Sharpino.Sample.11/Models/Course/Events.fs:21— Sharpino.Sample.11/Models/Course/Events.fs:21-28 | Sharpino.Sample.14/Models/Course/Events.fs:23-30 — 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) Sharpino.Sample/App.fs:94— Sharpino.Sample/App.fs:94-101 | Sharpino.Sample/App.fs:111-118 — both copies are in the same file, so extract the 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) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Events.fs:14— Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Events.fs:14-21 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Events.fs:12-19 — 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 (12 lines × 2) Sharpino.Lib/PgEventStore.fs:553— Sharpino.Lib/PgEventStore.fs:553-564 | Sharpino.Lib/PgBinaryEventStore.fs:581-592 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:553` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) Sharpino.Lib/PgEventStore.fs:700— Sharpino.Lib/PgEventStore.fs:700-711 | Sharpino.Lib/PgBinaryEventStore.fs:864-875 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (12 lines × 2) Sharpino.Lib/PgEventStore.fs:778— Sharpino.Lib/PgEventStore.fs:778-789 | Sharpino.Lib/PgEventStore.fs:842-853 — both copies are in the same file, so extract the 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) Sharpino.Lib/PgEventStore.fs:1522— Sharpino.Lib/PgEventStore.fs:1522-1533 | Sharpino.Lib/PgBinaryEventStore.fs:1537-1548 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1522` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Sharpino.Lib/StateView.fs:289— Sharpino.Lib/StateView.fs:289-300 | Sharpino.Lib/StateView.fs:347-358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:289` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Sharpino.Lib/StateView.fs:558— Sharpino.Lib/StateView.fs:558-569 | Sharpino.Lib/StateView.fs:585-596 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:558` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Sharpino.Lib/StateView.fs:965— Sharpino.Lib/StateView.fs:965-976 | Sharpino.Lib/StateView.fs:999-1010 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:965` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) Sharpino.Lib/CommandHandler.fs:1324— Sharpino.Lib/CommandHandler.fs:1324-1335 | Sharpino.Lib/CommandHandler.fs:1975-1986 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1324` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) Sharpino.Lib/CommandHandler.fs:2586— Sharpino.Lib/CommandHandler.fs:2586-2597 | Sharpino.Lib/CommandHandler.fs:2690-2701 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) Sharpino.Sample.11/Test2.fs:82— Sharpino.Sample.11/Test2.fs:82-93 | Sharpino.Sample.11/Test2.fs:225-236 — both copies are in the same file, so extract the 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) Sharpino.Sample.11/Test2.fs:188— Sharpino.Sample.11/Test2.fs:188-199 | Sharpino.Sample.11/Test2.fs:263-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) Sharpino.Sample.11/Test2.fs:371— Sharpino.Sample.11/Test2.fs:371-382 | Sharpino.Sample.11/Test2.fs:441-452 — both copies are in the same file, so extract the 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) Sharpino.Sample.11/Test2.fs:405— Sharpino.Sample.11/Test2.fs:405-416 | Sharpino.Sample.11/Test2.fs:476-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 lines × 2) Sharpino.Sample.12/Models/Student/Student.fs:16— Sharpino.Sample.12/Models/Student/Student.fs:16-27 | Sharpino.Sample.9/models/Student/Student.fs:13-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.12/Models/Student/Student.fs:16` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) Sharpino.Sample.12/Models/Student/Commands.fs:6— Sharpino.Sample.12/Models/Student/Commands.fs:6-17 | Sharpino.Sample.9/models/Student/Commands.fs:6-18 — 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 (12 lines × 2) Sharpino.Sample.25/TodoManager.fs:89— Sharpino.Sample.25/TodoManager.fs:89-100 | Sharpino.Sample.25/TodoManager.fs:113-124 — both copies are in the same file, so extract the 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) Sharpino.Sample.3/Rows/Consumer.fs:25— Sharpino.Sample.3/Rows/Consumer.fs:25-36 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:20-31 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:3— Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs:3-14 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:3-14 — `Sharpino.Sample.FormerlySaga/Domain/Rows/Consumer.fs` and `Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs` are the same file name in two sibling directories, 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 41 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 (12 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:7— Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:7-19 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Cart.fs:8-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:7` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Events.fs:7— Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Events.fs:7-18 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Events.fs:6-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) Sharpino.Lib/PgEventStore.fs:654— Sharpino.Lib/PgEventStore.fs:654-668 | Sharpino.Lib/PgBinaryEventStore.fs:819-832 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:654` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Sharpino.Lib/PgEventStore.fs:919— Sharpino.Lib/PgEventStore.fs:919-932 | Sharpino.Lib/PgBinaryEventStore.fs:943-956 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:919` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Sharpino.Lib/PgEventStore.fs:2113— Sharpino.Lib/PgEventStore.fs:2113-2126 | Sharpino.Lib/PgBinaryEventStore.fs:2069-2084 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) Sharpino.Lib/PgEventStore.fs:2165— Sharpino.Lib/PgEventStore.fs:2165-2178 | Sharpino.Lib/PgBinaryEventStore.fs:2294-2307 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) Sharpino.Lib/PgEventStore.fs:2187— Sharpino.Lib/PgEventStore.fs:2187-2200 | Sharpino.Lib/PgEventStore.fs:2210-2223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2187` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) Sharpino.Lib/PgEventStore.fs:2215— Sharpino.Lib/PgEventStore.fs:2215-2228 | Sharpino.Lib/PgBinaryEventStore.fs:2434-2447 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (14 lines × 2) Sharpino.Lib/PgEventStore.fs:2861— Sharpino.Lib/PgEventStore.fs:2861-2875 | Sharpino.Lib/PgBinaryEventStore.fs:2835-2848 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2861` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:755— Sharpino.Lib/PgBinaryEventStore.fs:755-768 | Sharpino.Lib/PgBinaryEventStore.fs:842-855 — both copies are in the same file, so extract the 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) Sharpino.Lib/PgBinaryEventStore.fs:804— Sharpino.Lib/PgBinaryEventStore.fs:804-817 | Sharpino.Lib/PgBinaryEventStore.fs:901-914 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:804` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) Sharpino.Lib/CommandHandler.fs:1171— Sharpino.Lib/CommandHandler.fs:1171-1184 | Sharpino.Lib/CommandHandler.fs:1233-1246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1171` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) Sharpino.Lib/CommandHandler.fs:3176— Sharpino.Lib/CommandHandler.fs:3176-3189 | Sharpino.Lib/CommandHandler.fs:3252-3265 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:3176` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Sharpino.Sample.11/Models/Course/Commands.fs:1— Sharpino.Sample.11/Models/Course/Commands.fs:1-14 | Sharpino.Sample.12/Models/Course/Commands.fs:1-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) Sharpino.Sample.11/Models/Course/Consumer.fs:3— Sharpino.Sample.11/Models/Course/Consumer.fs:3-16 | Sharpino.Sample.14/Models/Course/Consumer.fs:3-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) Sharpino.Sample.16/Models/Products/Commands.fs:1— Sharpino.Sample.16/Models/Products/Commands.fs:1-14 | Sharpino.Sample.17/Models/Products/Commands.fs:1-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) Sharpino.Sample.27/Program.fs:53— Sharpino.Sample.27/Program.fs:53-66 | Sharpino.Sample.28/Program.fs:53-66 — `Sharpino.Sample.27/Program.fs` and `Sharpino.Sample.28/Program.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 98 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 2) Sharpino.Sample.9/models/Item/Consumer.fs:82— Sharpino.Sample.9/models/Item/Consumer.fs:82-95 | Sharpino.Sample.9/models/Course/Consumer.fs:74-87 — `Sharpino.Sample.9/models/Item/Consumer.fs` and `Sharpino.Sample.9/models/Course/Consumer.fs` are the same file name in two sibling directories, 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 53 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:29— Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:29-43 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Cart.fs:28-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Cart.fs:29` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Commands.fs:58— Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Commands.fs:58-71 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Commands.fs:56-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Commands.fs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:47— Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:47-60 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:49-62 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Sharpino.Lib/PgEventStore.fs:2715— Sharpino.Lib/PgEventStore.fs:2715-2723 | Sharpino.Lib/PgEventStore.fs:2745-2756 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2715` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Sharpino.Lib/MemoryStorage.fs:203— Sharpino.Lib/MemoryStorage.fs:203-211 | Sharpino.Lib/MemoryStorage.fs:289-297 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:411— Sharpino.Lib/StateView.fs:411-419 | Sharpino.Lib/StateView.fs:452-460 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:546— Sharpino.Lib/StateView.fs:546-554 | Sharpino.Lib/StateView.fs:690-698 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:647— Sharpino.Lib/StateView.fs:647-655 | Sharpino.Lib/StateView.fs:680-688 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:647` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Sharpino.Lib/StateView.fs:756— Sharpino.Lib/StateView.fs:756-764 | Sharpino.Lib/StateView.fs:820-828 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:334— Sharpino.Lib/CommandHandler.fs:334-342 | Sharpino.Lib/CommandHandler.fs:1115-1123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:825— Sharpino.Lib/CommandHandler.fs:825-833 | Sharpino.Lib/CommandHandler.fs:1026-1034 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:872— Sharpino.Lib/CommandHandler.fs:872-880 | Sharpino.Lib/CommandHandler.fs:2802-2811 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:872` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:1456— Sharpino.Lib/CommandHandler.fs:1456-1464 | Sharpino.Lib/CommandHandler.fs:1549-1557 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:2171— Sharpino.Lib/CommandHandler.fs:2171-2179 | Sharpino.Lib/CommandHandler.fs:2299-2307 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:2620— Sharpino.Lib/CommandHandler.fs:2620-2628 | Sharpino.Lib/CommandHandler.fs:2818-2826 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:2689— Sharpino.Lib/CommandHandler.fs:2689-2697 | Sharpino.Lib/CommandHandler.fs:2787-2795 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:3154— Sharpino.Lib/CommandHandler.fs:3154-3162 | Sharpino.Lib/CommandHandler.fs:3230-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.
Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:4066— Sharpino.Lib/CommandHandler.fs:4066-4074 | Sharpino.Lib/CommandHandler.fs:5558-5566 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:4066` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Sharpino.Lib/CommandHandler.fs:4307— Sharpino.Lib/CommandHandler.fs:4307-4315 | Sharpino.Lib/CommandHandler.fs:4456-4464 — both copies are in the same file, so extract the 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) Sharpino.Sample.11/Models/Course/Course.fs:62— Sharpino.Sample.11/Models/Course/Course.fs:62-70 | Sharpino.Sample.14/Models/Course/Course.fs:69-77 — 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) Sharpino.Sample.11/Models/Student/Commands.fs:13— Sharpino.Sample.11/Models/Student/Commands.fs:13-21 | Sharpino.Sample.14/Models/Student/Commands.fs:16-24 — 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) Sharpino.Sample.12/Models/Course/Commands.fs:17— Sharpino.Sample.12/Models/Course/Commands.fs:17-25 | Sharpino.Sample.9/models/Course/Commands.fs:15-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) Sharpino.Lib/PgEventStore.fs:851— Sharpino.Lib/PgEventStore.fs:851-857 | Sharpino.Lib/PgBinaryEventStore.fs:688-694 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:928— Sharpino.Lib/PgBinaryEventStore.fs:928-934 | Sharpino.Lib/PgBinaryEventStore.fs:962-968 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) Sharpino.Lib/MemoryStorage.fs:1056— Sharpino.Lib/MemoryStorage.fs:1056-1062 | Sharpino.Lib/MemoryStorage.fs:1070-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.
Duplicated block (7 lines × 2) Sharpino.Lib/Cache.fs:505— Sharpino.Lib/Cache.fs:505-511 | Sharpino.Lib/Cache.fs:553-560 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:271— Sharpino.Lib/StateView.fs:271-277 | Sharpino.Lib/StateView.fs:329-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 (7 lines × 2) Sharpino.Lib/StateView.fs:845— Sharpino.Lib/StateView.fs:845-851 | Sharpino.Lib/StateView.fs:869-875 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:845` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:98— Sharpino.Lib/CommandHandler.fs:98-104 | Sharpino.Sample.9/Commons.fs:54-60 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:153— Sharpino.Lib/CommandHandler.fs:153-159 | Sharpino.Lib/CommandHandler.fs:212-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:153` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:272— Sharpino.Lib/CommandHandler.fs:272-278 | Sharpino.Lib/CommandHandler.fs:311-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:505— Sharpino.Lib/CommandHandler.fs:505-511 | Sharpino.Lib/CommandHandler.fs:542-548 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:858— Sharpino.Lib/CommandHandler.fs:858-864 | Sharpino.Lib/CommandHandler.fs:1065-1073 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:1281— Sharpino.Lib/CommandHandler.fs:1281-1287 | Sharpino.Lib/CommandHandler.fs:1379-1385 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1281` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:1667— Sharpino.Lib/CommandHandler.fs:1667-1673 | Sharpino.Lib/CommandHandler.fs:1769-1775 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1667` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:1699— Sharpino.Lib/CommandHandler.fs:1699-1705 | Sharpino.Lib/CommandHandler.fs:1801-1807 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:4285— Sharpino.Lib/CommandHandler.fs:4285-4291 | Sharpino.Lib/CommandHandler.fs:4434-4440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:5872— Sharpino.Lib/CommandHandler.fs:5872-5878 | Sharpino.Lib/CommandHandler.fs:5936-5943 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Sharpino.Lib/CommandHandler.fs:5974— Sharpino.Lib/CommandHandler.fs:5974-5980 | Sharpino.Lib/CommandHandler.fs:6056-6062 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/GoodsContainer.fs:33— Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/GoodsContainer.fs:33-39 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/GoodsContainer.fs:32-38 — 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 (10 lines × 2) Sharpino.Lib/PgEventStore.fs:466— Sharpino.Lib/PgEventStore.fs:466-475 | Sharpino.Lib/PgBinaryEventStore.fs:444-455 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:466` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:650— Sharpino.Lib/PgBinaryEventStore.fs:650-659 | Sharpino.Lib/PgBinaryEventStore.fs:720-729 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:650` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1245— Sharpino.Lib/PgBinaryEventStore.fs:1245-1254 | Sharpino.Lib/PgBinaryEventStore.fs:2629-2638 — both copies are in the same file, so extract the 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) Sharpino.Lib/PgBinaryEventStore.fs:2349— Sharpino.Lib/PgBinaryEventStore.fs:2349-2358 | Sharpino.Lib/PgBinaryEventStore.fs:2620-2629 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:2349` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sharpino.Lib/MemoryStorage.fs:83— Sharpino.Lib/MemoryStorage.fs:83-92 | Sharpino.Lib/MemoryStorage.fs:147-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) Sharpino.Lib/MemoryStorage.fs:838— Sharpino.Lib/MemoryStorage.fs:838-847 | Sharpino.Lib/MemoryStorage.fs:856-865 — both copies are in the same file, so extract the 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) Sharpino.Lib/AzureServiceBusBackplane.fs:118— Sharpino.Lib/AzureServiceBusBackplane.fs:118-127 | Sharpino.Lib/PgNotifyBackplane.fs:104-113 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/AzureServiceBusBackplane.fs:118` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sharpino.Lib/StateView.fs:123— Sharpino.Lib/StateView.fs:123-133 | Sharpino.Lib/StateView.fs:152-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:123` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sharpino.Lib/RabbitMq.fs:184— Sharpino.Lib/RabbitMq.fs:184-195 | Sharpino.Lib/RabbitMq.fs:245-254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) Sharpino.Lib/CommandHandler.fs:1138— Sharpino.Lib/CommandHandler.fs:1138-1147 | Sharpino.Lib/CommandHandler.fs:1194-1203 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:1563— Sharpino.Lib/CommandHandler.fs:1563-1572 | Sharpino.Lib/CommandHandler.fs:2652-2661 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1563` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sharpino.Lib/CommandHandler.fs:2210— Sharpino.Lib/CommandHandler.fs:2210-2219 | Sharpino.Lib/CommandHandler.fs:2431-2441 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:2261— Sharpino.Lib/CommandHandler.fs:2261-2270 | Sharpino.Lib/CommandHandler.fs:2277-2286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:2261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sharpino.Lib/CommandHandler.fs:3504— Sharpino.Lib/CommandHandler.fs:3504-3513 | Sharpino.Lib/CommandHandler.fs:4166-4177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:3504` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sharpino.Sample.11/Models/Student/Student.fs:56— Sharpino.Sample.11/Models/Student/Student.fs:56-65 | Sharpino.Sample.14/Models/Student/Student.fs:71-81 — 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 (10 lines × 2) Sharpino.Sample/App.fs:116— Sharpino.Sample/App.fs:116-125 | Sharpino.Sample/App.fs:306-315 — both copies are in the same file, so extract the 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) Sharpino.Lib.Core/Utils.fs:60— Sharpino.Lib.Core/Utils.fs:60-71 | Sharpino.Lib.Core/Utils.fs:75-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib.Core/Utils.fs:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) Sharpino.Lib/PgEventStore.fs:2050— Sharpino.Lib/PgEventStore.fs:2050-2060 | Sharpino.Lib/PgBinaryEventStore.fs:2075-2085 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2050` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:2361— Sharpino.Lib/PgBinaryEventStore.fs:2361-2371 | Sharpino.Lib/PgBinaryEventStore.fs:2407-2417 — both copies are in the same file, so extract the 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) Sharpino.Lib/MemoryStorage.fs:659— Sharpino.Lib/MemoryStorage.fs:659-669 | Sharpino.Lib/MemoryStorage.fs:678-688 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:196— Sharpino.Lib/StateView.fs:196-206 | Sharpino.Lib/StateView.fs:230-240 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) Sharpino.Lib/StateView.fs:911— Sharpino.Lib/StateView.fs:911-921 | Sharpino.Lib/StateView.fs:935-945 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:911` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) Sharpino.Lib/CommandHandler.fs:1265— Sharpino.Lib/CommandHandler.fs:1265-1275 | Sharpino.Lib/CommandHandler.fs:1926-1936 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:1362— Sharpino.Lib/CommandHandler.fs:1362-1372 | Sharpino.Lib/CommandHandler.fs:2046-2056 — both copies are in the same file, so extract the 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) Sharpino.Sample.11/Test2.fs:112— Sharpino.Sample.11/Test2.fs:112-122 | Sharpino.Sample.11/Test2.fs:331-341 — both copies are in the same file, so extract the 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) Sharpino.Sample.11/Test2.fs:244— Sharpino.Sample.11/Test2.fs:244-254 | Sharpino.Sample.11/Test2.fs:459-469 — both copies are in the same file, so extract the 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) Sharpino.Sample.9/models/Item/Consumer.fs:46— Sharpino.Sample.9/models/Item/Consumer.fs:46-56 | Sharpino.Sample.9/models/Reservation/Consumer.fs:47-57 — `Sharpino.Sample.9/models/Item/Consumer.fs` and `Sharpino.Sample.9/models/Reservation/Consumer.fs` are the same file name in two sibling directories, 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 50 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 (11 lines × 2) Sharpino.Sample.9/CourseManager.fs:3— Sharpino.Sample.9/CourseManager.fs:3-13 | Sharpino.Sample.9/CourseManagerAsync.fs:4-14 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (11 lines × 2) Sharpino.Sample.FormerlySaga/Domain/Booking/Consumer.fs:63— Sharpino.Sample.FormerlySaga/Domain/Booking/Consumer.fs:63-73 | Sharpino.Sample.FormerlySaga/Domain/Voucher/Consumer.fs:95-105 — 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 (11 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:21— Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:21-31 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:22-34 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 (11 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Events.fs:8— Sharpino.Sample.7/shoppingCartWithSharpino/GoodsContainer/Events.fs:8-18 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/GoodsContainer/Events.fs:7-17 — 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 (20 lines × 2) Sharpino.Lib/PgEventStore.fs:375— Sharpino.Lib/PgEventStore.fs:375-394 | Sharpino.Lib/PgBinaryEventStore.fs:363-383 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:375` 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 (20 lines × 2) Sharpino.Lib/PgEventStore.fs:1543— Sharpino.Lib/PgEventStore.fs:1543-1565 | Sharpino.Lib/PgBinaryEventStore.fs:1556-1575 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1543` 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 (20 lines × 2) Sharpino.Lib/PgEventStore.fs:1692— Sharpino.Lib/PgEventStore.fs:1692-1711 | Sharpino.Lib/PgBinaryEventStore.fs:1695-1715 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1692` 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 (20 lines × 2) Sharpino.Lib/PgEventStore.fs:1991— Sharpino.Lib/PgEventStore.fs:1991-2010 | Sharpino.Lib/PgBinaryEventStore.fs:2017-2036 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1991` 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 (20 lines × 2) Sharpino.Lib/PgEventStore.fs:2390— Sharpino.Lib/PgEventStore.fs:2390-2409 | Sharpino.Lib/PgBinaryEventStore.fs:2532-2551 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (20 lines × 2) Sharpino.Lib/PgEventStore.fs:2989— Sharpino.Lib/PgEventStore.fs:2989-3008 | Sharpino.Lib/PgBinaryEventStore.fs:2962-2982 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2989` 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 (20 lines × 2) Sharpino.Sample.11/Models/Student/Student.fs:23— Sharpino.Sample.11/Models/Student/Student.fs:23-42 | Sharpino.Sample.14/Models/Student/Student.fs:23-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.11/Models/Student/Student.fs:23` 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 (20 lines × 2) Sharpino.Sample.11/CourseManager.fs:75— Sharpino.Sample.11/CourseManager.fs:75-95 | Sharpino.Sample.14/CourseManager.fs:199-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.11/CourseManager.fs:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20 lines × 2) Sharpino.Sample.12/Models/Student/Student.fs:33— Sharpino.Sample.12/Models/Student/Student.fs:33-52 | Sharpino.Sample.9/models/Student/Student.fs:26-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.12/Models/Student/Student.fs:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) Sharpino.Sample.16/Models/Materials/Material.fs:7— Sharpino.Sample.16/Models/Materials/Material.fs:7-26 | Sharpino.Sample.17/Models/Materials/Material.fs:7-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.16/Models/Materials/Material.fs:7` 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 (20 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:179— Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:179-198 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:181-200 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) Sharpino.Lib/PgEventStore.fs:141— Sharpino.Lib/PgEventStore.fs:141-158 | Sharpino.Lib/PgBinaryEventStore.fs:126-143 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:141` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 2) Sharpino.Lib/PgEventStore.fs:521— Sharpino.Lib/PgEventStore.fs:521-538 | Sharpino.Lib/PgBinaryEventStore.fs:549-566 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:521` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 2) Sharpino.Lib/PgEventStore.fs:609— Sharpino.Lib/PgEventStore.fs:609-626 | Sharpino.Lib/PgBinaryEventStore.fs:776-793 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (18 lines × 2) Sharpino.Lib/PgEventStore.fs:1199— Sharpino.Lib/PgEventStore.fs:1199-1216 | Sharpino.Lib/PgBinaryEventStore.fs:1213-1230 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1199` 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 (18 lines × 2) Sharpino.Lib/PgEventStore.fs:1287— Sharpino.Lib/PgEventStore.fs:1287-1304 | Sharpino.Lib/PgBinaryEventStore.fs:1398-1416 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1398` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) Sharpino.Lib/PgEventStore.fs:1617— Sharpino.Lib/PgEventStore.fs:1617-1634 | Sharpino.Lib/PgBinaryEventStore.fs:1628-1645 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1617` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) Sharpino.Lib/PgEventStore.fs:2071— Sharpino.Lib/PgEventStore.fs:2071-2088 | Sharpino.Lib/PgBinaryEventStore.fs:1947-1964 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2071` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) Sharpino.Lib/PgEventStore.fs:2579— Sharpino.Lib/PgEventStore.fs:2579-2596 | Sharpino.Lib/PgBinaryEventStore.fs:2729-2746 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2579` 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 (18 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1663— Sharpino.Lib/PgBinaryEventStore.fs:1663-1680 | Sharpino.Lib/PgBinaryEventStore.fs:1771-1788 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1663` 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 (18 lines × 2) Sharpino.Lib/CommandHandler.fs:2957— Sharpino.Lib/CommandHandler.fs:2957-2974 | Sharpino.Lib/CommandHandler.fs:3028-3046 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:2957` 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 (18 lines × 2) Sharpino.Sample.16/MaterialManager.fs:1— Sharpino.Sample.16/MaterialManager.fs:1-18 | Sharpino.Sample.25/TodoManager.fs:1-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) Sharpino.Lib/PgEventStore.fs:2897— Sharpino.Lib/PgEventStore.fs:2897-2911 | Sharpino.Lib/PgBinaryEventStore.fs:2870-2884 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2897` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) Sharpino.Lib/PgEventStore.fs:3072— Sharpino.Lib/PgEventStore.fs:3072-3086 | Sharpino.Lib/PgBinaryEventStore.fs:3044-3058 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:3072` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) Sharpino.Lib/CommandHandler.fs:2599— Sharpino.Lib/CommandHandler.fs:2599-2615 | Sharpino.Lib/CommandHandler.fs:2711-2725 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:2599` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) Sharpino.Sample.16/Commons.fs:51— Sharpino.Sample.16/Commons.fs:51-65 | Sharpino.Sample.17/Commons.fs:51-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) Sharpino.Sample.16/Models/Products/Events.fs:1— Sharpino.Sample.16/Models/Products/Events.fs:1-15 | Sharpino.Sample.17/Models/Products/Events.fs:1-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) Sharpino.Sample.16/Models/WorkOrders/Events.fs:4— Sharpino.Sample.16/Models/WorkOrders/Events.fs:4-18 | Sharpino.Sample.17/Models/WorkOrders/Events.fs:4-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:1— Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:1-15 | Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:1-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Good.fs:20— Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Good.fs:20-34 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Good.fs:20-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Good.fs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:39— Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:39-53 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/SuperMarket.fs:34-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.7/shoppingCartWithSharpino/SuperMarket.fs:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) Sharpino.Lib/PgEventStore.fs:1043— Sharpino.Lib/PgEventStore.fs:1043-1059 | Sharpino.Lib/PgBinaryEventStore.fs:1059-1075 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1043` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) Sharpino.Lib/PgEventStore.fs:1264— Sharpino.Lib/PgEventStore.fs:1264-1280 | Sharpino.Lib/PgBinaryEventStore.fs:1279-1295 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (17 lines × 2) Sharpino.Lib/PgEventStore.fs:1889— Sharpino.Lib/PgEventStore.fs:1889-1905 | Sharpino.Lib/PgBinaryEventStore.fs:411-427 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1889` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) Sharpino.Lib/RabbitMq.fs:78— Sharpino.Lib/RabbitMq.fs:78-94 | Sharpino.Lib/RabbitMq.fs:105-122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) Sharpino.Lib/CommandHandler.fs:1523— Sharpino.Lib/CommandHandler.fs:1523-1539 | Sharpino.Lib/CommandHandler.fs:1615-1631 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1523` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) Sharpino.Lib/CommandHandler.fs:2186— Sharpino.Lib/CommandHandler.fs:2186-2202 | Sharpino.Lib/CommandHandler.fs:2226-2242 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:2186` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) Sharpino.Lib/CommandHandler.fs:3715— Sharpino.Lib/CommandHandler.fs:3715-3731 | Sharpino.Lib/CommandHandler.fs:3941-3957 — both copies are in the same file, so extract the 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) Sharpino.Sample.12/Models/Course/Course.fs:46— Sharpino.Sample.12/Models/Course/Course.fs:46-62 | Sharpino.Sample.9/models/Course/Course.fs:53-69 — 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.
Change coupling: Events.fs ↔ Events.fs Sharpino.Sample/Domain/Tags/Events.fs— `Sharpino.Sample/Domain/Tags/Events.fs` and `Sharpino.Sample/Domain/Todos/Events.fs` change together 100% of the time (15 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: Events.fs ↔ Events.fs Sharpino.Sample/Domain/Categories/Events.fs— `Sharpino.Sample/Domain/Categories/Events.fs` and `Sharpino.Sample/Domain/Tags/Events.fs` change together 100% of the time (15 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: Context.fs ↔ Context.fs Sharpino.Sample/Domain/Categories/Context.fs— `Sharpino.Sample/Domain/Categories/Context.fs` and `Sharpino.Sample/Domain/Tags/Context.fs` change together 85% of the time (22 of the 26 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: Commands.fs ↔ Commands.fs Sharpino.Sample/Domain/Categories/Commands.fs— `Sharpino.Sample/Domain/Categories/Commands.fs` and `Sharpino.Sample/Domain/Tags/Commands.fs` change together 83% of the time (15 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: Context.fs ↔ Events.fs Sharpino.Sample/Domain/Categories/Context.fs— `Sharpino.Sample/Domain/Categories/Context.fs` and `Sharpino.Sample/Domain/Tags/Events.fs` change together 80% of the time (12 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: Events.fs ↔ Events.fs Sharpino.Sample/Domain/Categories/Events.fs— `Sharpino.Sample/Domain/Categories/Events.fs` and `Sharpino.Sample/Domain/Todos/Events.fs` change together 79% of the time (15 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: Context.fs ↔ Events.fs Sharpino.Sample/Domain/Tags/Context.fs— `Sharpino.Sample/Domain/Tags/Context.fs` and `Sharpino.Sample/Domain/Todos/Events.fs` change together 79% of the time (15 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Duplicated block (6 lines × 2) Sharpino.Lib/PgBinaryEventStore.fs:1976— Sharpino.Lib/PgBinaryEventStore.fs:1976-1981 | Sharpino.Lib/PgBinaryEventStore.fs:2051-2056 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) Sharpino.Lib/MemoryStorage.fs:804— Sharpino.Lib/MemoryStorage.fs:804-809 | Sharpino.Lib/MemoryStorage.fs:931-937 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) Sharpino.Lib/MemoryStorage.fs:946— Sharpino.Lib/MemoryStorage.fs:946-951 | Sharpino.Lib/MemoryStorage.fs:968-973 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:84— Sharpino.Lib/StateView.fs:84-89 | Sharpino.Lib/StateView.fs:103-108 — both copies are in the same file, so extract the 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) Sharpino.Lib/StateView.fs:928— Sharpino.Lib/StateView.fs:928-933 | Sharpino.Lib/StateView.fs:986-991 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) Sharpino.Lib/CommandHandler.fs:1706— Sharpino.Lib/CommandHandler.fs:1706-1711 | Sharpino.Lib/CommandHandler.fs:1808-1813 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:5962— Sharpino.Lib/CommandHandler.fs:5962-5967 | Sharpino.Lib/CommandHandler.fs:6044-6049 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
FileTooLong: Sharpino.Lib/CommandHandler.fs Sharpino.Lib/CommandHandler.fs:0— FileTooLong — 5174 significant lines (blank, comment-only and punctuation-only lines excluded). 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: Sharpino.Lib/PgBinaryEventStore.fs Sharpino.Lib/PgBinaryEventStore.fs:0— FileTooLong — 2536 significant lines (blank, comment-only and punctuation-only lines excluded). 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: Sharpino.Lib/PgEventStore.fs Sharpino.Lib/PgEventStore.fs:0— FileTooLong — 2536 significant lines (blank, comment-only and punctuation-only lines excluded). 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: Sharpino.Lib/MemoryStorage.fs Sharpino.Lib/MemoryStorage.fs:0— FileTooLong — 1043 significant lines (blank, comment-only and punctuation-only lines excluded). 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: Sharpino.Lib/StateView.fs Sharpino.Lib/StateView.fs:0— FileTooLong — 900 significant lines (blank, comment-only and punctuation-only lines excluded). 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: Sharpino.Lib/Cache.fs Sharpino.Lib/Cache.fs:0— FileTooLong — 687 significant lines (blank, comment-only and punctuation-only lines excluded). 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.
Duplicated block (19 lines × 2) Sharpino.Lib/PgEventStore.fs:339— Sharpino.Lib/PgEventStore.fs:339-357 | Sharpino.Lib/PgBinaryEventStore.fs:327-345 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (19 lines × 2) Sharpino.Lib/PgEventStore.fs:987— Sharpino.Lib/PgEventStore.fs:987-1005 | Sharpino.Lib/PgBinaryEventStore.fs:1003-1021 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:987` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) Sharpino.Lib/PgEventStore.fs:1858— Sharpino.Lib/PgEventStore.fs:1858-1876 | Sharpino.Lib/PgBinaryEventStore.fs:1858-1876 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1858` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19 lines × 2) Sharpino.Lib/PgEventStore.fs:2412— Sharpino.Lib/PgEventStore.fs:2412-2430 | Sharpino.Lib/PgBinaryEventStore.fs:2553-2574 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (19 lines × 2) Sharpino.Lib/MemoryStorage.fs:411— Sharpino.Lib/MemoryStorage.fs:411-429 | Sharpino.Lib/MemoryStorage.fs:436-454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) Sharpino.Lib/CommandHandler.fs:5076— Sharpino.Lib/CommandHandler.fs:5076-5094 | Sharpino.Lib/CommandHandler.fs:5374-5392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) Sharpino.Lib/CommandHandler.fs:136— Sharpino.Lib/CommandHandler.fs:136-140 | Sharpino.Lib/CommandHandler.fs:187-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) Sharpino.Lib/CommandHandler.fs:325— Sharpino.Lib/CommandHandler.fs:325-329 | Sharpino.Lib/CommandHandler.fs:1106-1110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:325` 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 (5 lines × 2) Sharpino.Lib/CommandHandler.fs:1319— Sharpino.Lib/CommandHandler.fs:1319-1323 | Sharpino.Lib/CommandHandler.fs:1970-1974 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:1504— Sharpino.Lib/CommandHandler.fs:1504-1508 | Sharpino.Lib/CommandHandler.fs:1598-1602 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:1961— Sharpino.Lib/CommandHandler.fs:1961-1965 | Sharpino.Lib/CommandHandler.fs:2089-2094 — both copies are in the same file, so extract the 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) Sharpino.Lib/CommandHandler.fs:2679— Sharpino.Lib/CommandHandler.fs:2679-2683 | Sharpino.Lib/CommandHandler.fs:2776-2781 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
TooManyMethods: CommandHandler Sharpino.Lib/CommandHandler.fs:33— TooManyMethods — 86 methods. 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: PgBinaryStore Sharpino.Lib/PgBinaryEventStore.fs:35— TooManyMethods — 74 methods. 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: PgEventStore Sharpino.Lib/PgEventStore.fs:52— TooManyMethods — 74 methods. 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: MemoryStorage Sharpino.Lib/MemoryStorage.fs:27— TooManyMethods — 69 methods. 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: StateView Sharpino.Lib/StateView.fs:23— TooManyMethods — 37 methods. 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.
Medium CVE: Microsoft.IdentityModel.JsonWebTokens 6.8.0 — Microsoft.IdentityModel.JsonWebTokens 6.8.0 (transitive) has a Medium advisory; affects 9 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.IdentityModel.Tokens.Jwt 6.8.0 — System.IdentityModel.Tokens.Jwt 6.8.0 (transitive) has a Medium advisory; affects 9 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: log4net 3.2.0 — log4net 3.2.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.IdentityModel.JsonWebTokens 6.10.0 — Microsoft.IdentityModel.JsonWebTokens 6.10.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.IdentityModel.Tokens.Jwt 6.10.0 — System.IdentityModel.Tokens.Jwt 6.10.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Duplicated block (23 lines × 2) Sharpino.Lib/PgEventStore.fs:270— Sharpino.Lib/PgEventStore.fs:270-292 | Sharpino.Lib/PgBinaryEventStore.fs:255-277 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:270` 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 (23 lines × 2) Sharpino.Lib/PgEventStore.fs:419— Sharpino.Lib/PgEventStore.fs:419-441 | Sharpino.Lib/PgBinaryEventStore.fs:455-477 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:419` 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 (23 lines × 2) Sharpino.Lib/PgEventStore.fs:1426— Sharpino.Lib/PgEventStore.fs:1426-1448 | Sharpino.Lib/PgBinaryEventStore.fs:1444-1466 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1426` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23 lines × 2) Sharpino.Lib/PgEventStore.fs:2686— Sharpino.Lib/PgEventStore.fs:2686-2708 | Sharpino.Lib/PgBinaryEventStore.fs:2148-2170 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (23 lines × 2) Sharpino.Lib/PgEventStore.fs:3134— Sharpino.Lib/PgEventStore.fs:3134-3156 | Sharpino.Lib/PgBinaryEventStore.fs:3106-3128 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:3134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 3) Sharpino.Lib/PgBinaryEventStore.fs:1547— Sharpino.Lib/PgBinaryEventStore.fs:1547-1556 | Sharpino.Lib/PgBinaryEventStore.fs:1658-1667 | Sharpino.Lib/PgBinaryEventStore.fs:1766-1775 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:1547` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) Sharpino.Lib/CommandHandler.fs:2347— Sharpino.Lib/CommandHandler.fs:2347-2356 | Sharpino.Lib/CommandHandler.fs:2395-2404 | Sharpino.Lib/CommandHandler.fs:2442-2451 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:2347` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) Sharpino.Lib/CommandHandler.fs:2844— Sharpino.Lib/CommandHandler.fs:2844-2853 | Sharpino.Lib/CommandHandler.fs:3123-3132 | Sharpino.Lib/CommandHandler.fs:3200-3209 — 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) Sharpino.Sample.2/Commons.fs:3— Sharpino.Sample.2/Commons.fs:3-12 | Sharpino.Sample.6/Commons.fs:2-11 | Sharpino.Sample/Commons.fs:2-11 — `Sharpino.Sample.2/Commons.fs` and `Sharpino.Sample.6/Commons.fs` are the same file name in two sibling directories, 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 30 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 (10 lines × 3) Sharpino.Sample.2/Commons.fs:29— Sharpino.Sample.2/Commons.fs:29-38 | Sharpino.Sample.6/Commons.fs:28-37 | Sharpino.Sample/Commons.fs:28-37 — `Sharpino.Sample.2/Commons.fs` and `Sharpino.Sample.6/Commons.fs` are the same file name in two sibling directories, 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 30 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 `Sharpino.Sample.2/Commons.fs:29` 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.
Main.main (cyclomatic 60) Sharpino.Sample.24/Program.fs:20— Main.main has cyclomatic complexity 60 (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.
Main.main (cyclomatic 60) Sharpino.Sample.26/Program.fs:20— Main.main has cyclomatic complexity 60 (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.
Main.main (cyclomatic 60) Sharpino.Sample.27/Program.fs:20— Main.main has cyclomatic complexity 60 (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.
Main.main (cyclomatic 60) Sharpino.Sample.28/Program.fs:20— Main.main has cyclomatic complexity 60 (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.
Main.main (cognitive 105) Sharpino.Sample.24/Program.fs:20— Main.main has cognitive complexity 105 (threshold 15). Drivers by points: match/switch 57, if/else 42, boolean chains 6 (nesting depth added 62). 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.
Main.main (cognitive 105) Sharpino.Sample.26/Program.fs:20— Main.main has cognitive complexity 105 (threshold 15). Drivers by points: match/switch 57, if/else 42, boolean chains 6 (nesting depth added 62). 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.
Main.main (cognitive 105) Sharpino.Sample.27/Program.fs:20— Main.main has cognitive complexity 105 (threshold 15). Drivers by points: match/switch 57, if/else 42, boolean chains 6 (nesting depth added 62). 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.
Main.main (cognitive 105) Sharpino.Sample.28/Program.fs:20— Main.main has cognitive complexity 105 (threshold 15). Drivers by points: match/switch 57, if/else 42, boolean chains 6 (nesting depth added 62). 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 (22 lines × 2) Sharpino.Lib/PgEventStore.fs:94— Sharpino.Lib/PgEventStore.fs:94-115 | Sharpino.Lib/PgBinaryEventStore.fs:79-100 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs: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 (22 lines × 2) Sharpino.Lib/PgEventStore.fs:1165— Sharpino.Lib/PgEventStore.fs:1165-1187 | Sharpino.Lib/PgBinaryEventStore.fs:1183-1204 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) Sharpino.Lib/PgEventStore.fs:1730— Sharpino.Lib/PgEventStore.fs:1730-1751 | Sharpino.Lib/PgBinaryEventStore.fs:1734-1755 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1730` 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 (22 lines × 2) Sharpino.Lib/CommandHandler.fs:4998— Sharpino.Lib/CommandHandler.fs:4998-5019 | Sharpino.Lib/CommandHandler.fs:5296-5317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 3) Sharpino.Lib/CommandHandler.fs:1434— Sharpino.Lib/CommandHandler.fs:1434-1446 | Sharpino.Lib/CommandHandler.fs:1721-1733 | Sharpino.Lib/CommandHandler.fs:1823-1834 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:1434` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 3) Sharpino.Lib/CommandHandler.fs:3473— Sharpino.Lib/CommandHandler.fs:3473-3484 | Sharpino.Lib/CommandHandler.fs:3708-3719 | Sharpino.Lib/CommandHandler.fs:3934-3945 — 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) Sharpino.Lib/CommandHandler.fs:4582— Sharpino.Lib/CommandHandler.fs:4582-4593 | Sharpino.Lib/CommandHandler.fs:4873-4885 | Sharpino.Lib/CommandHandler.fs:5171-5183 — 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) Sharpino.Sample.11/Definitions.fs:6— Sharpino.Sample.11/Definitions.fs:6-17 | Sharpino.Sample.14/Definitions.fs:9-21 | Sharpino.Sample.15/Commons.fs:6-18 — 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 (11 lines × 4) Sharpino.Lib/PgBinaryEventStore.fs:437— Sharpino.Lib/PgBinaryEventStore.fs:437-447 | Sharpino.Lib/PgBinaryEventStore.fs:493-503 | Sharpino.Lib/PgBinaryEventStore.fs:532-542 | Sharpino.Lib/PgBinaryEventStore.fs:2677-2687 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgBinaryEventStore.fs:437` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 4) Sharpino.Lib/CommandHandler.fs:1042— Sharpino.Lib/CommandHandler.fs:1042-1054 | Sharpino.Lib/CommandHandler.fs:3459-3469 | Sharpino.Lib/CommandHandler.fs:3694-3704 | Sharpino.Lib/CommandHandler.fs:3920-3930 — 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 × 4) Sharpino.Sample.6/Ingredients/Consumer.fs:67— Sharpino.Sample.6/Ingredients/Consumer.fs:67-77 | Sharpino.Sample.6/Dishes/Consumer.fs:64-74 | Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:58-68 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:60-70 — before extracting anything, compare `Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs` and `Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 4) Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:39— Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:39-49 | Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:57-67 | Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:75-85 | Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:93-103 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.FormerlySaga/Domain/Rows/Commands.fs:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (21 lines × 2) Sharpino.Lib/PgEventStore.fs:1486— Sharpino.Lib/PgEventStore.fs:1486-1506 | Sharpino.Lib/PgBinaryEventStore.fs:1501-1521 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1486` 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) Sharpino.Lib/PgEventStore.fs:1832— Sharpino.Lib/PgEventStore.fs:1832-1852 | Sharpino.Lib/PgBinaryEventStore.fs:1832-1852 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (21 lines × 2) Sharpino.Lib/PgEventStore.fs:1956— Sharpino.Lib/PgEventStore.fs:1956-1976 | Sharpino.Lib/PgBinaryEventStore.fs:1985-2005 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:1956` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 3) Sharpino.Lib/CommandHandler.fs:2364— Sharpino.Lib/CommandHandler.fs:2364-2377 | Sharpino.Lib/CommandHandler.fs:2412-2424 | Sharpino.Lib/CommandHandler.fs:2456-2470 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:2364` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) Sharpino.Lib/CommandHandler.fs:4741— Sharpino.Lib/CommandHandler.fs:4741-4753 | Sharpino.Lib/CommandHandler.fs:5045-5057 | Sharpino.Lib/CommandHandler.fs:5343-5355 — 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) Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:246— Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:246-258 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:283-295 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:362-374 — 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 × 4) Sharpino.Lib/CommandHandler.fs:1481— Sharpino.Lib/CommandHandler.fs:1481-1492 | Sharpino.Lib/CommandHandler.fs:1576-1587 | Sharpino.Lib/CommandHandler.fs:2665-2676 | Sharpino.Lib/CommandHandler.fs:2761-2773 — 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 (12 lines × 4) Sharpino.Sample.24/DetailsRefactor.fs:2— Sharpino.Sample.24/DetailsRefactor.fs:2-13 | Sharpino.Sample.26/DetailsRefactor.fs:2-13 | Sharpino.Sample.27/DetailsRefactor.fs:2-13 | Sharpino.Sample.28/DetailsRefactor.fs:2-13 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (12 lines × 4) Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:169— Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:169-180 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:194-205 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:315-327 | Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:396-407 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.FormerlySaga/Api/SeatBooking.fs:169` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) Sharpino.Lib/MqttBackplane.fs:35— Sharpino.Lib/MqttBackplane.fs:35-43 | Sharpino.Lib/AzureServiceBusBackplane.fs:55-62 | Sharpino.Lib/PgNotifyBackplane.fs:43-50 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 3) Sharpino.Lib/StateView.fs:783— Sharpino.Lib/StateView.fs:783-790 | Sharpino.Lib/StateView.fs:819-826 | Sharpino.Lib/StateView.fs:875-882 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 3) Sharpino.Lib/CommandHandler.fs:2495— Sharpino.Lib/CommandHandler.fs:2495-2502 | Sharpino.Lib/CommandHandler.fs:2638-2645 | Sharpino.Lib/CommandHandler.fs:2730-2737 — 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) Sharpino.Lib/StateView.fs:439— Sharpino.Lib/StateView.fs:439-445 | Sharpino.Lib/StateView.fs:571-577 | Sharpino.Lib/StateView.fs:598-604 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 3) Sharpino.Lib/CommandHandler.fs:2333— Sharpino.Lib/CommandHandler.fs:2333-2339 | Sharpino.Lib/CommandHandler.fs:2381-2387 | Sharpino.Lib/CommandHandler.fs:2428-2434 — 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) Sharpino.Lib/CommandHandler.fs:3449— Sharpino.Lib/CommandHandler.fs:3449-3455 | Sharpino.Lib/CommandHandler.fs:3682-3688 | Sharpino.Lib/CommandHandler.fs:3908-3914 — 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.
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×2
Medium CVE: [GHSA redacted] Sharpino.Sample.Client/package-lock.json— @babel/helpers 7.23.9: [GHSA redacted] — @babel/helpers is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/helpers to 7.26.10 with an `overrides` entry).
Medium CVE: [GHSA redacted] Sharpino.Sample.Client/package-lock.json— nanoid 3.3.7: [GHSA redacted] — nanoid is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin nanoid to 3.3.8 with an `overrides` entry).
Duplicated block (22 lines × 4) Sharpino.Lib/CommandHandler.fs:975— Sharpino.Lib/CommandHandler.fs:975-996 | Sharpino.Lib/CommandHandler.fs:3402-3423 | Sharpino.Lib/CommandHandler.fs:3635-3656 | Sharpino.Lib/CommandHandler.fs:3861-3882 — 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 (22 lines × 4) Sharpino.Sample.24/TodoManager.fs:175— Sharpino.Sample.24/TodoManager.fs:175-196 | Sharpino.Sample.26/TodoManager.fs:175-196 | Sharpino.Sample.27/TodoManager.fs:175-196 | Sharpino.Sample.28/TodoManager.fs:175-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.24/TodoManager.fs:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 4) Sharpino.Sample.24/DetailsRefactor.fs:39— Sharpino.Sample.24/DetailsRefactor.fs:39-59 | Sharpino.Sample.26/DetailsRefactor.fs:39-59 | Sharpino.Sample.27/DetailsRefactor.fs:39-59 | Sharpino.Sample.28/DetailsRefactor.fs:39-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (21 lines × 4) Sharpino.Sample.24/Program.fs:1— Sharpino.Sample.24/Program.fs:1-21 | Sharpino.Sample.26/Program.fs:1-21 | Sharpino.Sample.27/Program.fs:1-21 | Sharpino.Sample.28/Program.fs:1-21 — `Sharpino.Sample.24/Program.fs` and `Sharpino.Sample.26/Program.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 99 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 (18 lines × 5) Sharpino.Sample.22/Domain/Todo/Todo.fs:2— Sharpino.Sample.22/Domain/Todo/Todo.fs:2-19 | Sharpino.Sample.24/Domain/Todo/Todo.fs:2-19 | Sharpino.Sample.26/Domain/Todo/Todo.fs:2-19 | Sharpino.Sample.27/Domain/Todo/Todo.fs:2-19 | Sharpino.Sample.28/Domain/Todo/Todo.fs:2-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (18 lines × 5) Sharpino.Sample.22/TodoManager.fs:84— Sharpino.Sample.22/TodoManager.fs:84-101 | Sharpino.Sample.24/TodoManager.fs:145-162 | Sharpino.Sample.26/TodoManager.fs:145-162 | Sharpino.Sample.27/TodoManager.fs:145-162 | Sharpino.Sample.28/TodoManager.fs:145-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.22/TodoManager.fs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 5) Sharpino.Sample.22/Domain/Todo/Commands.fs:5— Sharpino.Sample.22/Domain/Todo/Commands.fs:5-19 | Sharpino.Sample.24/Domain/Todo/Commands.fs:5-19 | Sharpino.Sample.26/Domain/Todo/Commands.fs:5-19 | Sharpino.Sample.27/Domain/Todo/Commands.fs:5-19 | Sharpino.Sample.28/Domain/Todo/Commands.fs:5-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (15 lines × 5) Sharpino.Sample.22/Domain/User/Commands.fs:2— Sharpino.Sample.22/Domain/User/Commands.fs:2-16 | Sharpino.Sample.24/Domain/User/Commands.fs:2-16 | Sharpino.Sample.26/Domain/User/Commands.fs:2-16 | Sharpino.Sample.27/Domain/User/Commands.fs:2-16 | Sharpino.Sample.28/Domain/User/Commands.fs:2-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (15 lines × 4) Sharpino.Sample.24/TodoManager.fs:45— Sharpino.Sample.24/TodoManager.fs:45-59 | Sharpino.Sample.26/TodoManager.fs:45-59 | Sharpino.Sample.27/TodoManager.fs:45-59 | Sharpino.Sample.28/TodoManager.fs:45-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (15 lines × 4) Sharpino.Sample.24/Program.fs:76— Sharpino.Sample.24/Program.fs:76-90 | Sharpino.Sample.26/Program.fs:76-90 | Sharpino.Sample.27/Program.fs:74-88 | Sharpino.Sample.28/Program.fs:74-88 — `Sharpino.Sample.24/Program.fs` and `Sharpino.Sample.26/Program.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 99 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 (15 lines × 3) Sharpino.Lib/CommandHandler.fs:4813— Sharpino.Lib/CommandHandler.fs:4813-4827 | Sharpino.Lib/CommandHandler.fs:5111-5125 | Sharpino.Lib/CommandHandler.fs:5409-5423 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:4813` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) Sharpino.Sample.22/Program.fs:45— Sharpino.Sample.22/Program.fs:45-59 | Sharpino.Sample.24/Program.fs:54-68 | Sharpino.Sample.26/Program.fs:54-68 — 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 (14 lines × 5) Sharpino.Sample.22/Domain/Todo/Events.fs:2— Sharpino.Sample.22/Domain/Todo/Events.fs:2-15 | Sharpino.Sample.24/Domain/Todo/Events.fs:2-15 | Sharpino.Sample.26/Domain/Todo/Events.fs:2-15 | Sharpino.Sample.27/Domain/Todo/Events.fs:2-15 | Sharpino.Sample.28/Domain/Todo/Events.fs:2-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (14 lines × 5) Sharpino.Sample.22/Program.fs:4— Sharpino.Sample.22/Program.fs:4-17 | Sharpino.Sample.24/Program.fs:9-23 | Sharpino.Sample.26/Program.fs:9-23 | Sharpino.Sample.27/Program.fs:9-23 | Sharpino.Sample.28/Program.fs:9-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (14 lines × 3) Sharpino.Lib/CommandHandler.fs:4077— Sharpino.Lib/CommandHandler.fs:4077-4090 | Sharpino.Lib/CommandHandler.fs:4230-4243 | Sharpino.Lib/CommandHandler.fs:4379-4392 — 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 (14 lines × 3) Sharpino.Sample.11/Models/Student/Consumer.fs:5— Sharpino.Sample.11/Models/Student/Consumer.fs:5-18 | Sharpino.Sample.11/Models/Student2/Consumer.fs:5-18 | Sharpino.Sample.14/Models/Student/Consumer.fs:5-18 — 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 (10 lines × 4) Sharpino.Lib/Commons.fs:14— Sharpino.Lib/Commons.fs:14-23 | Sharpino.Sample.2/Commons.fs:13-22 | Sharpino.Sample.6/Commons.fs:12-21 | Sharpino.Sample/Commons.fs:12-21 — `Sharpino.Sample.2/Commons.fs` and `Sharpino.Sample.6/Commons.fs` are the same file name in two sibling directories, 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 30 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 `Sharpino.Lib/Commons.fs:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) Sharpino.Lib/CommandHandler.fs:1654— Sharpino.Lib/CommandHandler.fs:1654-1663 | Sharpino.Lib/CommandHandler.fs:1756-1765 | Sharpino.Lib/CommandHandler.fs:1857-1866 | Sharpino.Lib/CommandHandler.fs:5765-5774 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 5) Sharpino.Lib/StateView.fs:51— Sharpino.Lib/StateView.fs:51-59 | Sharpino.Lib/StateView.fs:127-135 | Sharpino.Lib/StateView.fs:155-163 | Sharpino.Lib/StateView.fs:178-186 | Sharpino.Lib/StateView.fs:212-220 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/StateView.fs:51` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 5) Sharpino.Sample.22/TodoManager.fs:148— Sharpino.Sample.22/TodoManager.fs:148-156 | Sharpino.Sample.24/TodoManager.fs:286-294 | Sharpino.Sample.26/TodoManager.fs:286-294 | Sharpino.Sample.27/TodoManager.fs:286-294 | Sharpino.Sample.28/TodoManager.fs:286-294 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Sample.22/TodoManager.fs:148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) Sharpino.Lib/CommandHandler.fs:1943— Sharpino.Lib/CommandHandler.fs:1943-1951 | Sharpino.Lib/CommandHandler.fs:3139-3149 | Sharpino.Lib/CommandHandler.fs:3215-3225 — 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 lines × 3) Sharpino.Sample.11/Test2.fs:300— Sharpino.Sample.11/Test2.fs:300-308 | Sharpino.Sample.11/Test2.fs:371-379 | Sharpino.Sample.11/Test2.fs:441-449 — 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.
Main.main (cyclomatic 57) Sharpino.Sample.22/Program.fs:14— Main.main has cyclomatic complexity 57 (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.
Hotspot: Sharpino.Lib/Cache.fs Sharpino.Lib/Cache.fs— Sharpino.Lib/Cache.fs changed 4 times in last 90 days, max complexity 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[1] | LineNumber: 0 | BytePositionInLine: 1076.
Main.main (cognitive 101) Sharpino.Sample.22/Program.fs:14— Main.main has cognitive complexity 101 (threshold 15). Drivers by points: match/switch 56, if/else 39, boolean chains 6 (nesting depth added 61). 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.
AggregateCache3.SetupL2AndBackplane (cognitive 36) Sharpino.Lib/Cache.fs:441— AggregateCache3.SetupL2AndBackplane has cognitive complexity 36 (threshold 15). Drivers by points: if/else 30, match/switch 5, boolean chains 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommandHandler.runThreeNAggregateCommandsMd (cognitive 33) Sharpino.Lib/CommandHandler.fs:5512— CommandHandler.runThreeNAggregateCommandsMd has cognitive complexity 33 (threshold 15). Drivers by points: loops 12, match/switch 12, if/else 9 (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.
DetailsCache.SetupL2AndBackplane (cognitive 32) Sharpino.Lib/Cache.fs:127— DetailsCache.SetupL2AndBackplane has cognitive complexity 32 (threshold 15). Drivers by points: if/else 29, boolean chains 3 (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.
DetailsCache.RefreshAsync (cognitive 27) Sharpino.Lib/Cache.fs:194— DetailsCache.RefreshAsync has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10, match/switch 9, error handling 7, boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommandHandler.runTwoNAggregateCommandsMd (cognitive 17) Sharpino.Lib/CommandHandler.fs:4033— CommandHandler.runTwoNAggregateCommandsMd has cognitive complexity 17 (threshold 15). Drivers by points: loops 6, match/switch 6, if/else 5 (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.
CommandHandler.runTwoNAggregateCommandsMdAsync2 (cognitive 17) Sharpino.Lib/CommandHandler.fs:4180— CommandHandler.runTwoNAggregateCommandsMdAsync2 has cognitive complexity 17 (threshold 15). Drivers by points: loops 6, match/switch 6, if/else 5 (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.
CommandHandler.runTwoNAggregateCommandsMdAsync3 (cognitive 17) Sharpino.Lib/CommandHandler.fs:4329— CommandHandler.runTwoNAggregateCommandsMdAsync3 has cognitive complexity 17 (threshold 15). Drivers by points: loops 6, match/switch 6, if/else 5 (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.
Change coupling clique: Categories.fs, Tags.fs, Todos.fs Sharpino.Sample/Domain/Categories/Categories.fs— 3 files — `Sharpino.Sample/Domain/Categories/Categories.fs`, `Sharpino.Sample/Domain/Tags/Tags.fs`, `Sharpino.Sample/Domain/Todos/Todos.fs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D38 · OSV Dependency Vulnerabilities· Medium vulnerability · ×1
Medium vulnerability: [GHSA redacted] Sharpino.Sample.Client/package-lock.json— esbuild 0.18.20: [GHSA redacted] — esbuild is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin esbuild to 0.25.0 with an `overrides` entry).
Duplicated block (35 lines × 2) Sharpino.Lib/CommandHandler.fs:4887— Sharpino.Lib/CommandHandler.fs:4887-4921 | Sharpino.Lib/CommandHandler.fs:5185-5219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:4887` 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 (30 lines × 2) Sharpino.Lib/CommandHandler.fs:3554— Sharpino.Lib/CommandHandler.fs:3554-3583 | Sharpino.Lib/CommandHandler.fs:3780-3809 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:3554` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) Sharpino.Lib/PgEventStore.fs:164— Sharpino.Lib/PgEventStore.fs:164-190 | Sharpino.Lib/PgBinaryEventStore.fs:149-175 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:164` 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 (26 lines × 2) Sharpino.Sample.16/Models/WorkOrders/WorkOrder.fs:8— Sharpino.Sample.16/Models/WorkOrders/WorkOrder.fs:8-33 | Sharpino.Sample.17/Models/WorkOrders/WorkOrder.fs:8-33 — 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 (25 lines × 2) Sharpino.Lib/PgEventStore.fs:2329— Sharpino.Lib/PgEventStore.fs:2329-2353 | Sharpino.Lib/PgBinaryEventStore.fs:2469-2493 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/PgEventStore.fs:2329` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (24 lines × 2) Sharpino.Lib/PgEventStore.fs:3186— Sharpino.Lib/PgEventStore.fs:3186-3209 | Sharpino.Lib/PgBinaryEventStore.fs:3158-3181 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (22 lines × 5) Sharpino.Sample.22/Program.fs:85— Sharpino.Sample.22/Program.fs:85-106 | Sharpino.Sample.24/Program.fs:111-132 | Sharpino.Sample.26/Program.fs:111-132 | Sharpino.Sample.27/Program.fs:109-130 | Sharpino.Sample.28/Program.fs:109-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (21 lines × 3) Sharpino.Lib/CommandHandler.fs:4696— Sharpino.Lib/CommandHandler.fs:4696-4716 | Sharpino.Lib/CommandHandler.fs:4998-5018 | Sharpino.Lib/CommandHandler.fs:5296-5316 — 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 (19 lines × 5) Sharpino.Sample.22/Domain/User/User.fs:4— Sharpino.Sample.22/Domain/User/User.fs:4-22 | Sharpino.Sample.24/Domain/User/User.fs:4-22 | Sharpino.Sample.26/Domain/User/User.fs:4-22 | Sharpino.Sample.27/Domain/User/User.fs:4-22 | Sharpino.Sample.28/Domain/User/User.fs:4-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (19 lines × 4) Sharpino.Sample.24/Details.fs:72— Sharpino.Sample.24/Details.fs:72-90 | Sharpino.Sample.26/Details.fs:72-90 | Sharpino.Sample.27/Details.fs:72-90 | Sharpino.Sample.28/Details.fs:72-90 — `Sharpino.Sample.24/Details.fs` and `Sharpino.Sample.26/Details.fs` are the same file name in two sibling directories, 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 54 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 `Sharpino.Sample.24/Details.fs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 4) Sharpino.Sample.24/Details.fs:35— Sharpino.Sample.24/Details.fs:35-52 | Sharpino.Sample.26/Details.fs:35-52 | Sharpino.Sample.27/Details.fs:35-52 | Sharpino.Sample.28/Details.fs:35-52 — `Sharpino.Sample.24/Details.fs` and `Sharpino.Sample.26/Details.fs` are the same file name in two sibling directories, 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 54 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 `Sharpino.Sample.24/Details.fs:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 5) Sharpino.Sample.22/Details.fs:2— Sharpino.Sample.22/Details.fs:2-18 | Sharpino.Sample.24/Details.fs:2-18 | Sharpino.Sample.26/Details.fs:2-18 | Sharpino.Sample.27/Details.fs:2-18 | Sharpino.Sample.28/Details.fs:2-18 — `Sharpino.Sample.24/Details.fs` and `Sharpino.Sample.26/Details.fs` are the same file name in two sibling directories, 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 54 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 `Sharpino.Sample.22/Details.fs:2` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 4) Sharpino.Sample.24/TodoManager.fs:9— Sharpino.Sample.24/TodoManager.fs:9-25 | Sharpino.Sample.26/TodoManager.fs:9-25 | Sharpino.Sample.27/TodoManager.fs:9-25 | Sharpino.Sample.28/TodoManager.fs:9-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (17 lines × 3) Sharpino.Lib/CommandHandler.fs:1388— Sharpino.Lib/CommandHandler.fs:1388-1404 | Sharpino.Lib/CommandHandler.fs:1677-1693 | Sharpino.Lib/CommandHandler.fs:1779-1795 — 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 × 5) Sharpino.Sample.22/Domain/User/Events.fs:2— Sharpino.Sample.22/Domain/User/Events.fs:2-17 | Sharpino.Sample.24/Domain/User/Events.fs:2-17 | Sharpino.Sample.26/Domain/User/Events.fs:2-17 | Sharpino.Sample.27/Domain/User/Events.fs:2-17 | Sharpino.Sample.28/Domain/User/Events.fs:2-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (14 lines × 6) Sharpino.Sample.9/models/Item/Consumer.fs:1— Sharpino.Sample.9/models/Item/Consumer.fs:1-15 | Sharpino.Sample.9/models/Reservation/Consumer.fs:1-15 | Sharpino.Sample.9/models/Student/Consumer.fs:1-15 | Sharpino.Sample.9/models/Course/Consumer.fs:1-15 | Sharpino.Sample.9/models/Balance/Consumer.fs:1-14 | Sharpino.Sample.9/models/Teacher/Consumer.fs:1-15 — `Sharpino.Sample.9/models/Item/Consumer.fs` and `Sharpino.Sample.9/models/Reservation/Consumer.fs` are the same file name in two sibling directories, 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 50 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 (14 lines × 4) Sharpino.Lib/PgEventStore.fs:205— Sharpino.Lib/PgEventStore.fs:205-218 | Sharpino.Lib/PgEventStore.fs:300-313 | Sharpino.Lib/PgBinaryEventStore.fs:190-203 | Sharpino.Lib/PgBinaryEventStore.fs:290-303 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13 lines × 5) Sharpino.Sample.22/Commons.fs:1— Sharpino.Sample.22/Commons.fs:1-13 | Sharpino.Sample.24/Commons.fs:1-13 | Sharpino.Sample.26/Commons.fs:1-13 | Sharpino.Sample.27/Commons.fs:1-13 | Sharpino.Sample.28/Commons.fs:1-13 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (13 lines × 4) Sharpino.Lib/CommandHandler.fs:3348— Sharpino.Lib/CommandHandler.fs:3348-3360 | Sharpino.Lib/CommandHandler.fs:4616-4628 | Sharpino.Lib/CommandHandler.fs:4918-4930 | Sharpino.Lib/CommandHandler.fs:5216-5228 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:3348` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 10) Sharpino.Sample.6/Suppliers/Consumer.fs:22— Sharpino.Sample.6/Suppliers/Consumer.fs:22-34 | Sharpino.Sample.9/models/Item/Consumer.fs:21-34 | Sharpino.Sample.9/models/Reservation/Consumer.fs:21-32 | Sharpino.Sample.9/models/Student/Consumer.fs:21-32 | Sharpino.Sample.9/models/Course/Consumer.fs:21-32 | Sharpino.Sample.9/models/Balance/Consumer.fs:20-31 | Sharpino.Sample.9/models/Teacher/Consumer.fs:21-32 | Sharpino.Sample.7/shoppingCartWithSharpino/Cart/Consumer.fs:20-33 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Cart/Consumer.fs:22-33 | Sharpino.Sample.7/shoppingCartWithSharpinoBinary/Goods/Consumer.fs:21-34 — `Sharpino.Sample.9/models/Item/Consumer.fs` and `Sharpino.Sample.9/models/Reservation/Consumer.fs` are the same file name in two sibling directories, 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 50 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 5) Sharpino.Sample.10/Models/Counter/Consumer.fs:20— Sharpino.Sample.10/Models/Counter/Consumer.fs:20-33 | Sharpino.Sample.10/Models/Account/Consumer.fs:20-33 | Sharpino.Sample.6/Dishes/Consumer.fs:18-29 | Sharpino.Sample.8/Domain/Site/Consumer.fs:20-31 | Sharpino.Sample.7/shoppingCartWithSharpino/Goods/Consumer.fs:20-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 6) Sharpino.Sample.17/MaterialManager.fs:25— Sharpino.Sample.17/MaterialManager.fs:25-35 | Sharpino.Sample.22/Program.fs:17-27 | Sharpino.Sample.24/Program.fs:23-33 | Sharpino.Sample.26/Program.fs:23-33 | Sharpino.Sample.27/Program.fs:23-33 | Sharpino.Sample.28/Program.fs:23-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times.
Duplicated block (11 lines × 3) Sharpino.Sample.9/models/Student/Consumer.fs:47— Sharpino.Sample.9/models/Student/Consumer.fs:47-57 | Sharpino.Sample.9/models/Course/Consumer.fs:47-57 | Sharpino.Sample.9/models/Teacher/Consumer.fs:47-57 — `Sharpino.Sample.9/models/Student/Consumer.fs` and `Sharpino.Sample.9/models/Course/Consumer.fs` are the same file name in two sibling directories, 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 40 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 (10 lines × 9) Sharpino.Sample.3/Rows/Consumer.fs:73— Sharpino.Sample.3/Rows/Consumer.fs:73-82 | Sharpino.Sample.8/Domain/Site/Consumer.fs:50-59 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:42-51 | Sharpino.Sample.8/Domain/Truck/Consumer.fs:61-70 | Sharpino.Sample.9/models/Item/Consumer.fs:49-58 | Sharpino.Sample.9/models/Item/Consumer.fs:74-83 | Sharpino.Sample.9/models/Reservation/Consumer.fs:50-59 | Sharpino.Sample.9/models/Course/Consumer.fs:66-75 | Sharpino.Sample.9/models/Balance/Consumer.fs:43-52 — `Sharpino.Sample.9/models/Item/Consumer.fs` and `Sharpino.Sample.9/models/Reservation/Consumer.fs` are the same file name in two sibling directories, 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 50 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 (9 lines × 8) Sharpino.Lib/CommandHandler.fs:3304— Sharpino.Lib/CommandHandler.fs:3304-3312 | Sharpino.Lib/CommandHandler.fs:3531-3539 | Sharpino.Lib/CommandHandler.fs:3757-3765 | Sharpino.Lib/CommandHandler.fs:3982-3990 | Sharpino.Lib/CommandHandler.fs:4048-4056 | Sharpino.Lib/CommandHandler.fs:4195-4203 | Sharpino.Lib/CommandHandler.fs:4344-4352 | Sharpino.Lib/CommandHandler.fs:4494-4502 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 7) Sharpino.Lib/CommandHandler.fs:4567— Sharpino.Lib/CommandHandler.fs:4567-4575 | Sharpino.Lib/CommandHandler.fs:4850-4858 | Sharpino.Lib/CommandHandler.fs:5148-5156 | Sharpino.Lib/CommandHandler.fs:5446-5454 | Sharpino.Lib/CommandHandler.fs:5497-5505 | Sharpino.Lib/CommandHandler.fs:5535-5543 | Sharpino.Lib/CommandHandler.fs:5727-5735 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 11) Sharpino.Lib/CommandHandler.fs:3535— Sharpino.Lib/CommandHandler.fs:3535-3541 | Sharpino.Lib/CommandHandler.fs:3761-3767 | Sharpino.Lib/CommandHandler.fs:3986-3992 | Sharpino.Lib/CommandHandler.fs:4199-4205 | Sharpino.Lib/CommandHandler.fs:4348-4354 | Sharpino.Lib/CommandHandler.fs:4498-4504 | Sharpino.Lib/CommandHandler.fs:4572-4578 | Sharpino.Lib/CommandHandler.fs:4855-4861 | Sharpino.Lib/CommandHandler.fs:5153-5159 | Sharpino.Lib/CommandHandler.fs:5451-5457 | Sharpino.Lib/CommandHandler.fs:5540-5546 — all 11 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 4) Sharpino.Lib/CommandHandler.fs:3737— Sharpino.Lib/CommandHandler.fs:3737-3744 | Sharpino.Lib/CommandHandler.fs:3963-3969 | Sharpino.Lib/CommandHandler.fs:4323-4331 | Sharpino.Lib/CommandHandler.fs:4472-4481 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:3737` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 43) Sharpino.Lib/CommandHandler.fs:578— Sharpino.Lib/CommandHandler.fs:578-583 | Sharpino.Lib/CommandHandler.fs:1129-1134 | Sharpino.Lib/CommandHandler.fs:1185-1190 | Sharpino.Lib/CommandHandler.fs:1247-1252 | Sharpino.Lib/CommandHandler.fs:1336-1341 | Sharpino.Lib/CommandHandler.fs:1447-1452 | Sharpino.Lib/CommandHandler.fs:1540-1545 | Sharpino.Lib/CommandHandler.fs:1632-1637 | Sharpino.Lib/CommandHandler.fs:1734-1739 | Sharpino.Lib/CommandHandler.fs:1835-1840 | Sharpino.Lib/CommandHandler.fs:1885-1890 | Sharpino.Lib/CommandHandler.fs:1908-1913 | Sharpino.Lib/CommandHandler.fs:1987-1992 | Sharpino.Lib/CommandHandler.fs:2020-2025 | Sharpino.Lib/CommandHandler.fs:2117-2122 | Sharpino.Lib/CommandHandler.fs:2489-2494 | Sharpino.Lib/CommandHandler.fs:2614-2619 | Sharpino.Lib/CommandHandler.fs:2632-2637 | Sharpino.Lib/CommandHandler.fs:2724-2729 | Sharpino.Lib/CommandHandler.fs:2812-2817 | Sharpino.Lib/CommandHandler.fs:2830-2835 | Sharpino.Lib/CommandHandler.fs:3109-3114 | Sharpino.Lib/CommandHandler.fs:3186-3191 | Sharpino.Lib/CommandHandler.fs:3262-3267 | Sharpino.Lib/CommandHandler.fs:3290-3295 | Sharpino.Lib/CommandHandler.fs:3517-3522 | Sharpino.Lib/CommandHandler.fs:3743-3748 | Sharpino.Lib/CommandHandler.fs:3968-3973 | Sharpino.Lib/CommandHandler.fs:4006-4011 | Sharpino.Lib/CommandHandler.fs:4034-4039 | Sharpino.Lib/CommandHandler.fs:4181-4186 | Sharpino.Lib/CommandHandler.fs:4330-4335 | Sharpino.Lib/CommandHandler.fs:4480-4485 | Sharpino.Lib/CommandHandler.fs:4517-4522 | Sharpino.Lib/CommandHandler.fs:4545-4550 | Sharpino.Lib/CommandHandler.fs:4828-4833 | Sharpino.Lib/CommandHandler.fs:5126-5131 | Sharpino.Lib/CommandHandler.fs:5424-5429 | Sharpino.Lib/CommandHandler.fs:5475-5480 | Sharpino.Lib/CommandHandler.fs:5513-5518 | Sharpino.Lib/CommandHandler.fs:5705-5710 | Sharpino.Lib/CommandHandler.fs:5743-5748 | Sharpino.Lib/CommandHandler.fs:5819-5824 — all 43 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:578` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 12) Sharpino.Lib/CommandHandler.fs:586— Sharpino.Lib/CommandHandler.fs:586-591 | Sharpino.Lib/CommandHandler.fs:1134-1139 | Sharpino.Lib/CommandHandler.fs:1190-1195 | Sharpino.Lib/CommandHandler.fs:1252-1257 | Sharpino.Lib/CommandHandler.fs:1341-1346 | Sharpino.Lib/CommandHandler.fs:1452-1457 | Sharpino.Lib/CommandHandler.fs:1545-1550 | Sharpino.Lib/CommandHandler.fs:1890-1895 | Sharpino.Lib/CommandHandler.fs:1913-1918 | Sharpino.Lib/CommandHandler.fs:1992-1997 | Sharpino.Lib/CommandHandler.fs:2025-2030 | Sharpino.Lib/CommandHandler.fs:2122-2127 — all 12 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 6) Sharpino.Lib/CommandHandler.fs:377— Sharpino.Lib/CommandHandler.fs:377-382 | Sharpino.Lib/CommandHandler.fs:403-408 | Sharpino.Lib/CommandHandler.fs:436-441 | Sharpino.Lib/CommandHandler.fs:469-474 | Sharpino.Lib/CommandHandler.fs:499-504 | Sharpino.Lib/CommandHandler.fs:536-541 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:377` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) Sharpino.Lib/CommandHandler.fs:1089— Sharpino.Lib/CommandHandler.fs:1089-1094 | Sharpino.Lib/CommandHandler.fs:4807-4812 | Sharpino.Lib/CommandHandler.fs:5105-5110 | Sharpino.Lib/CommandHandler.fs:5403-5408 — 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 lines × 3) Sharpino.Lib/CommandHandler.fs:718— Sharpino.Lib/CommandHandler.fs:718-723 | Sharpino.Lib/CommandHandler.fs:3160-3165 | Sharpino.Lib/CommandHandler.fs:3236-3241 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:718` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 4) Sharpino.Lib/CommandHandler.fs:83— Sharpino.Lib/CommandHandler.fs:83-87 | Sharpino.Lib/CommandHandler.fs:131-135 | Sharpino.Lib/CommandHandler.fs:266-270 | Sharpino.Lib/CommandHandler.fs:305-309 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sharpino.Lib/CommandHandler.fs:83` 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 (5 lines × 3) Sharpino.Lib/CommandHandler.fs:4139— Sharpino.Lib/CommandHandler.fs:4139-4143 | Sharpino.Lib/CommandHandler.fs:4296-4300 | Sharpino.Lib/CommandHandler.fs:4445-4449 — 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 (28 lines × 2) Sharpino.Sample.15/Models/Course/Events.fs:1— Sharpino.Sample.15/Models/Course/Events.fs:1-28 | Sharpino.Sample.15/Models/Student/Events.fs:1-28 — 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.
Coverage not measured — The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. No coverage collector was found in your CI either, so there is no existing report to hand us: add a coverage collector to your test run and commit (or publish) its Cobertura/OpenCover/lcov output anywhere in the repo, or make the suite runnable in-image, and real coverage will be measured.
Recommendation — 2 finding(s)
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.fs) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
Low CVE: [GHSA redacted] Sharpino.Sample.Client/package-lock.json— @babel/core 7.23.9: [GHSA redacted] — @babel/core is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/core to 7.29.6 with an `overrides` entry).
Outdated: Azure.Messaging.ServiceBus — Azure.Messaging.ServiceBus 7.20.1 → 7.20.2 available (referenced by Sharpino.Lib).
Outdated: FsCheck — FsCheck 3.3.3 → 3.3.4 available (referenced by Sharpino.Lib).
Outdated: FSharp.Data — FSharp.Data 8.1.14 → 8.2.0 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Caching.Memory — Microsoft.Extensions.Caching.Memory 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Caching.SqlServer — Microsoft.Extensions.Caching.SqlServer 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Caching.StackExchangeRedis — Microsoft.Extensions.Caching.StackExchangeRedis 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Configuration.Binder — Microsoft.Extensions.Configuration.Binder 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Logging — Microsoft.Extensions.Logging 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 10.0.9 → 10.0.10 available (referenced by Sharpino.Lib).
Outdated: MQTTnet — MQTTnet 5.1.0.1559 → 5.2.0.1603 available (referenced by Sharpino.Lib).
Outdated: Sharpino.Core — Sharpino.Core 6.0.6 → 6.2.0 available (referenced by Sharpino.Lib).
Outdated: StackExchange.Redis — StackExchange.Redis 3.0.17 → 3.1.3 available (referenced by Sharpino.Lib).
Outdated: YoloDev.Expecto.TestSdk — YoloDev.Expecto.TestSdk 0.15.6 → 0.16.0 available (referenced by Sharpino.Lib).
Outdated: DotNetEnv — DotNetEnv 3.1.1 → 3.2.0 available (referenced by Sharpino.Sample).
Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.14.1 → 18.8.1 available (referenced by Sharpino.Sample.11).
Outdated: FSharpPlus — FSharpPlus 1.8.0 → 1.9.1 available (referenced by sharpinoSample17).
Outdated: Microsoft.Data.SqlClient — Microsoft.Data.SqlClient 5.2.2 → 7.0.2 available (referenced by Sharpino.Sample.24.Test).
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 019fce7c-afad-7189-a364-5f70c5899b64 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 6 · Warnings: 374 · Recommendations: 2 · Info: 22 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 04-08-2026 @ 20:35 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.