Public report — language-ext, published 5 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
393findings 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
50/98dimensions across the health lenses171034 LoC · 23 projects — 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.
louthy/language-ext carries serious risk (43%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.
It is strongest in Architecture (95%) — the structure is clean and changes stay contained.
The area that most needs attention is Readiness (25%) — operating, monitoring and recovering the system safely is harder. Security (53%) is the next concern — exposure to security and compliance incidents is elevated.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); Make types internal by default (Library API & versioning); ILogger (or Serilog) and log at meaningful points across… (Observability).
For scale: Large (~171,034 production lines); rebuilding it from scratch would take roughly ~1.0 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (95%); 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.
This codebase represents roughly ~1.0 person-years of build effort (about ~€150,000 to rebuild). Its weakest lens is Readiness at 25% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — service/app × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. 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 Large asset (~1.0 person-years to rebuild), and its weakest lens is Readiness at 25%. 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.
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.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture — module dependency matrix
32 modules, 60 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.)
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
A04:2021 — Insecure Design
2
High / Critical
Roadmap
First, establish a continuous integration workflow to automatically build and test every change. Next, restrict the public API by making types internal by default to protect consumers from internal changes. Then, implement structured logging across all services to improve observability. After that, configure explicit timeouts and cancellation tokens for all outbound HTTP calls to ensure fast failures. Finally, fix the three empty test files to improve test coverage and quality.
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.
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
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. 46 of 50 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 50 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 393 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
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
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.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
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.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
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").
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
The LLM boundary
LLM-set scores this run (4): D19, D21, D24, 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.
15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Internal.chaini at 29. A further 10 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Layout.layout at 26 — they are counted neither in the figure above nor in this dimension's score.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 VectorClock.relation (cyclomatic 19) finding(s) in Cyclomatic Complexity — start with VectorClock.A.cs, VectorClock.OrdA.NumB.A.B.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Iterable.Bind (cyclomatic 16) finding(s) in Cyclomatic Complexity — start with Iterable.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Internal.chaini (cyclomatic 29) finding(s) in Cyclomatic Complexity — start with Parsec.Internal.cs. — 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.
+ 24 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Iterable.Bind (cognitive 41) finding(s) in Cognitive Complexity — start with Iterable.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 IterableAdd.FoldWhileIO (cognitive 31) finding(s) in Cognitive Complexity — start with Iterable.Add.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 IterableAdd.FoldUntilIO (cognitive 31) finding(s) in Cognitive Complexity — start with Iterable.Add.cs (2). — One of this dimension's main actionable groups (2 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.0 / 10Adequate✓ 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 103 TooManyMethods finding(s) in God Classes — start with Prim.cs (3), Eff.cs (2), Prelude.Collections.cs. — One of this dimension's main actionable groups (103 warning-level).
Resolve the 16 FileTooLong finding(s) in God Classes — start with TrieMap.cs, Map.Internal.cs, AtomHashMap.Eq.cs. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 1 ClassTooLong finding(s) in God Classes — start with IL.cs. — One of this dimension's main actionable groups (1 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.
+ 22 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.7 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
1434 test methods: 1434 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
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.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
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 knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
104 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is LanguageExt.Core/Immutable Collections/Map/Map.cs.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
23 projects, 1755 source files, 189936 hand-written lines of code (169641 production / 20295 test), 55 inter-project edges (build status unknown — did not finish).
Thin analysable surface across projects
Build status unknown
✓ On the Gold path — maintain.
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The Language-Ext project is well documented with a strong README and architecture/usage guide for each major subsystem. The core monad-transformer system (Pipes, ProducerT/PipeT/ConsumerT, EffectT) is detailed in the Streaming README, while the Prelude section explains how to load static prelude types into every file so functional constructs are accessible everywhere. A dedicated release notes document covers breaking changes for each major version and links out to personal blog posts explaining new features like higher-kinded polymorphism and trait usage. The content is comprehensive but the visible portion of the XML-doc coverage (93% for F#) falls below the threshold, so any missing documentation in those namespaces would be outside the scope of this assessment. The LanguageExt project is well documented with a strong README presence (37 total) covering types, usage examples, and design rationale. The core documentation is split between markdown READMEs and XML doc coverage: the Effect/EffectsExamples namespaces are particularly thorough, with concrete type tables, migration notes, and law-cases for every major trait (Functor, Monad, Applicative, CoNatural, NaturalIso, MonoidK), while the remaining namespaces like Concurrency, Common/Error, and Ad-hoc polymorphism are well written. The XML coverage is mostly strong but not perfect: only 3 % of TestBed projects are covered (3/96) and one project (LanguageExt.Benchmarks) has zero coverage; these are minor gaps in a cohesive structure rather than defects.
Resolve the 13 Low XML-doc coverage finding(s) in Documentation Quality — start with LanguageExt.Parsec.csproj, TestBed.csproj, LanguageExt.Benchmarks.csproj. — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D24 · Comment Value / 10Exemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
2 of 23 projects flagged as possibly oversized/incoherent.
Split LanguageExt.Core
What to do
Resolve the 1 Split LanguageExt.Core finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability5.0 / 10Weak✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
56 % of calls cross a namespace and 3 % go through an interface, but 46 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
Scattered collaborators
What to do
Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
D32 · Data Compliance (PII/GDPR)5.0 / 10Adequate✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR pattern scan via semgrep across the repo, using Watchdog's own ruleset (personal data reaching log/console sinks, URLs and query strings, or unprotected browser storage); matches map to severity and a 0-10 wide normalizer. NotApplicable when the scan runs and detects no PII/GDPR surface (no unearned 10); reported LOUDLY as a measurement gap, never as not-applicable, if the ruleset is missing from the analyzer image. Exhaustive, advisory-leaning; degrades on parse failure.
High: watchdog-sensitive-personal-data-in-log · ×2Samples/CreditCardValidation/Program.cs:10detected by semgrep finding
What to do
Resolve the 2 High finding(s) in Data Compliance (PII/GDPR) — start with Program.cs (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
2 of 600 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is LanguageExt.Core/Effects/Schedule/Duration.cs.
Further orphaned files (smaller)
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
`Alternative<F>` declares 22 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Alternative.Trait.cs:7
`Applicative<F>` declares 16 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Applicative.Trait.cs:16
`Floating<A>` declares 18 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Floating.cs:10
`Foldable<T>` declares 58 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Foldable.Trait.cs:10
`MonadUnliftIO<M>` declares 73 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — MonadUnliftIO.Trait.cs:19
`DirectoryIO` declares 30 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — DirectoryIO.cs:6
`EnvironmentIO` declares 34 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — EnvironmentIO.cs:5
`FileIO` declares 19 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — FileIO.cs:7
`MonadParsecT<MP, E, S, T, M>` declares 17 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — MonadParsecT.cs:21
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C1 · Data Protection3.0 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×13) — ErrorException.cs:471, StateEff.cs:162, EnvironmentIO.cs:53, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
`Compare` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — OrdTrue.cs:10
`Combine` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — ErrorException.cs:471
`SelectMany` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — Fail.cs:41
`CompareTo` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — ErrorItem.cs:25, ErrorItem.cs:36, ErrorItem.cs:46
`TryConvertFromChecked` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Pos.cs:137
`TryConvertFromSaturating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Pos.cs:140
`TryConvertFromTruncating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Pos.cs:143
`TryConvertToChecked` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Pos.cs:146
`TryConvertToSaturating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Pos.cs:149
`TryConvertToTruncating` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Pos.cs:152
`TryFormat` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Pos.cs:210
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×17) — Arr.cs:707, Map.Internal.cs:1312, TrieMap.cs:2257, …
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
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 '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.
Add a README to the 21 of 23 project(s) that lack one — worth up to 1.8 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `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'.
Only 10/23 projects share a common root namespace — the code's module identity is inconsistent.
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.
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
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.
Do you agree with this assessment?
P10 · Library API & versioning2.0 / 10Critical✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries. Exhaustive, deterministic.
2109/2499 types (84%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
No <Version>/<VersionPrefix>/GitVersion/MinVer detected. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
Do you agree with this assessment?
P2 · Observability2.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) — 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: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — — 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 outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Roslyn scan: Polly resilience markers (Retry, CircuitBreaker, Timeout) on outbound HTTP invocations. Computed per type, deterministic.
Outbound HTTP calls were found with no timeout or retry policy around them. This codebase ships libraries/tools rather than a service it operates, so the failure lands differently: an unbounded call hangs the caller's process — a build step, a CLI run, a UI thread — with no way out.
What to do
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
Readiness · Performance — Whether the library protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way a library pressures its host's GC) aren't being measured.
What to do
Add [MemoryDiagnoser] to the benchmarks so allocation regressions are visible, not just time.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Raise allocation-aware density on the hot paths — currently 665 use(s) across 171,538 production line(s) (~3.9/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
19 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×11) — IO.cs:411, IO.cs:716, IO.cs:744, …
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.
Only 18/61 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×25) — AsyncEnumberable.Extensions.cs:14, AsyncEnumberable.Extensions.cs:22, AsyncEnumberable.Extensions.cs:34, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — Task.Prelude.cs:149, ValueTask.Prelude.cs:146, ResourcesDiscussion1366.cs:37, …
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
21/22 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~0.5 `!` suppressions per 1k syntax nodes — 394 suppression(s) across the 812862 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
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 — 48 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
D11 Test Reliability — Test runner surfaced no tests
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 — Bounded contexts not declared
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
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.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
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.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 348 value object(s); a Domain/Aggregates/ValueObjects layer
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
P12 CI test-gate honesty — no CI workflow found
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
P8 Schema migrations — no EF Core usage detected
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
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
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.
NoWarnInCsproj — 10 warning codes suppressed in one element LanguageExt.Streaming/LanguageExt.Streaming.csproj:6— A single <NoWarn> suppresses 10 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587) in one stroke — one team-wide decision, not 10 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj — 10 warning codes suppressed in one element LanguageExt.Rx/LanguageExt.Rx.csproj:6— A single <NoWarn> suppresses 10 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587) in one stroke — one team-wide decision, not 10 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj — 10 warning codes suppressed in one element LanguageExt.Parsec/LanguageExt.Parsec.csproj:6— A single <NoWarn> suppresses 10 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587) in one stroke — one team-wide decision, not 10 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj — 10 warning codes suppressed in one element LanguageExt.FSharp/LanguageExt.FSharp.csproj:7— A single <NoWarn> suppresses 10 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587) in one stroke — one team-wide decision, not 10 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj — 11 warning codes suppressed in one element LanguageExt.Core/LanguageExt.Core.csproj:6— A single <NoWarn> suppresses 11 warning codes (1701;1702;1705;IDE1006;CS1591;CS1573;CS1712;CS1711;CS1572;CS1587;CA2260) in one stroke — one team-wide decision, not 11 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
EmptyCatchBlock LanguageExt.Core/Concurrency/Task/Task.Prelude.cs:149— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock LanguageExt.Core/Concurrency/ValueTask/ValueTask.Prelude.cs:146— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Samples/TestBed/ResourcesDiscussion1366.cs:37— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Samples/TestBed/ResourcesDiscussion1366.cs:56— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Samples/TestBed/ResourcesDiscussion1366.cs:75— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
D10 · Test Quality· No assertions (empty test) · ×3
No assertions (empty test): StreamT LanguageExt.Tests/TraitTests/ApplicativeLawTests.cs:57— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): StreamT LanguageExt.Tests/TraitTests/FunctorLawTests.cs:101— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): StreamT LanguageExt.Tests/TraitTests/MonadLawsTest.cs:58— Test method has an empty body — it asserts nothing and exercises no code.
High: watchdog-sensitive-personal-data-in-log Samples/CreditCardValidation/Program.cs:10— Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.
High: watchdog-sensitive-personal-data-in-log Samples/CreditCardValidation/Program.cs:11— Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.
TooManyMethods: Prelude LanguageExt.Core/Immutable Collections/Prelude.Collections.cs:0— TooManyMethods — 4317 significant lines (blank, comment-only and punctuation-only lines excluded), 1158 methods, declared across 90 files: Immutable Collections/Prelude.Collections.cs (143), Currying and Partial Application/Prelude.PartialApplication.cs (91), Lambda function inference/Prelude.Func.cs (63), Value parsing/Prelude.Parse.cs (48), +86 more file(s). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: TrieMap LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:0— TooManyMethods — 1051 significant lines (blank, comment-only and punctuation-only lines excluded), 158 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: Map LanguageExt.Core/Immutable Collections/Map/Map.Module.cs:0— TooManyMethods — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 156 methods, declared across 2 files: Map/Map.Module.cs (80), Map/Map.Module.Ord.cs (76). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Map LanguageExt.Core/Immutable Collections/Map/Map.cs:0— TooManyMethods — 622 significant lines (blank, comment-only and punctuation-only lines excluded), 145 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: TrackingHashMap LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Eq.cs:0— TooManyMethods — 489 significant lines (blank, comment-only and punctuation-only lines excluded), 135 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: TrackingHashMap LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.cs:0— TooManyMethods — 488 significant lines (blank, comment-only and punctuation-only lines excluded), 135 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: Map LanguageExt.Core/Immutable Collections/Map/Map.Ord.cs:0— TooManyMethods — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 134 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: bigint LanguageExt.Core/DataTypes/BigInt/BigInt.cs:0— TooManyMethods — 287 significant lines (blank, comment-only and punctuation-only lines excluded), 130 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: HashMap LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:0— TooManyMethods — 575 significant lines (blank, comment-only and punctuation-only lines excluded), 129 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: HashMap LanguageExt.Core/Immutable Collections/HashMap/HashMap.cs:0— TooManyMethods — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 123 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: AtomHashMap LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:0— TooManyMethods — 955 significant lines (blank, comment-only and punctuation-only lines excluded), 118 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: TrackingHashMap LanguageExt.Core/Immutable Collections/TrackingHashMap/TrackingHashMap.Module.Eq.cs:0— TooManyMethods — 356 significant lines (blank, comment-only and punctuation-only lines excluded), 118 methods, declared across 2 files: TrackingHashMap/TrackingHashMap.Module.Eq.cs (59), TrackingHashMap/TrackingHashMap.Module.cs (59). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: AtomHashMap LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:0— TooManyMethods — 962 significant lines (blank, comment-only and punctuation-only lines excluded), 117 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: Applicative LanguageExt.Core/Traits/Applicative/Module/Applicative.Module.Apply.cs:0— TooManyMethods — 618 significant lines (blank, comment-only and punctuation-only lines excluded), 112 methods, declared across 12 files: Module/Applicative.Module.Apply.cs (19), Module/Applicative.Module.Memo.Apply.cs (19), Module/Applicative.Module.Memo.Lift.cs (17), Module/Applicative.Module.ApplyM.cs (9), +8 more file(s). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: HashMap LanguageExt.Core/Immutable Collections/HashMap/HashMap.Module.Eq.cs:0— TooManyMethods — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 111 methods, declared across 2 files: HashMap/HashMap.Module.Eq.cs (58), HashMap/HashMap.Module.cs (53). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Iterable LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:0— TooManyMethods — 612 significant lines (blank, comment-only and punctuation-only lines excluded), 110 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: EffExtensions LanguageExt.Core/Effects/Eff/Eff no runtime/Operators/Eff.Operators.Applicative.cs:0— TooManyMethods — 427 significant lines (blank, comment-only and punctuation-only lines excluded), 110 methods, declared across 12 files: Operators/Eff.Operators.Applicative.cs (21), Operators/Eff.Operators.Applicative.cs (21), Operators/Eff.Operators.Functor.cs (20), Operators/Eff.Operators.Functor.cs (20), +8 more file(s). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Either LanguageExt.Core/Monads/Alternative Monads/Either/Either.cs:0— TooManyMethods — 318 significant lines (blank, comment-only and punctuation-only lines excluded), 104 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: Validation LanguageExt.Core/Monads/Alternative Monads/Validation/Validation.cs:0— TooManyMethods — 313 significant lines (blank, comment-only and punctuation-only lines excluded), 96 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: Option LanguageExt.Core/Monads/Alternative Monads/Option/Option.cs:0— TooManyMethods — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 89 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: Set LanguageExt.Core/Immutable Collections/Set/Set.Ord.Module.cs:0— TooManyMethods — 303 significant lines (blank, comment-only and punctuation-only lines excluded), 89 methods, declared across 3 files: Set/Set.Ord.Module.cs (33), Set/Set.Module.cs (32), Trait/Set.TraitImpl.cs (24). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: MapInternal LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:0— TooManyMethods — 829 significant lines (blank, comment-only and punctuation-only lines excluded), 84 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: Fin LanguageExt.Core/Monads/Alternative Monads/Fin/Fin.cs:0— TooManyMethods — 280 significant lines (blank, comment-only and punctuation-only lines excluded), 84 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: List LanguageExt.Core/Immutable Collections/List/Lst.Module.cs:0— TooManyMethods — 376 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: ApplicativeExtensions LanguageExt.Core/Traits/Applicative/Operators/Applicative.Memo.Operators.cs:0— TooManyMethods — 373 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods, declared across 2 files: Operators/Applicative.Memo.Operators.cs (62), Operators/Applicative.Operators.cs (21). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TodoComment LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:504— // TODO: Consider building a monoid wrappers for all numeric values (and strings) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/DataTypes/StringM/OrdString.cs:1— // TODO: Work out where these types should live — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:1112— // TODO: Replace with FoldIO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:1127— // TODO: Replace with FoldIO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:1142— // TODO: Replace with FoldIO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/Immutable Collections/IterableNE/Trait/IterableNE.TraitImpl.cs:20— // TODO: We need a way of lifting an IO<IAsyncEnumerable> into IterableNE (knowing it's non-empty) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/Immutable Collections/IteratorAsync/IteratorAsync.cs:319— // TODO: Replace this with a WaitAny tasks for each side, replacing the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/Monads/IdentityT/IdentityT.Monad.cs:24— // TODO: Make a stack-safe version of this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/Traits/Applicative/Applicative.Trait.cs:225— // TODO: Consider ways to make this not be blocking as a sensible default implementation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Core/Traits/Domain/Locus.cs:1— // TODO: Decide whether you want to develop this idea or not
TodoComment LanguageExt.Core/Traits/Monads/Monad/Monad.Trait.cs:62— // TODO: Check if this implementation is valid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Megaparsec/Reach.cs:21— // TODO: Consider if the maths here are correct — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Megaparsec/Reach.cs:104— // TODO: Consider if the maths here are correct — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Megaparsec/Reach.cs:22— // TODO: Probably TokenStream should support Split — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Megaparsec/Reach.cs:105— // TODO: Probably TokenStream should support Split — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Parsec/Parsers/Token.cs:329— // : /* TODO - fully implement case insensitive version*/); — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Parsec/Parsers/Token2.cs:318— // : /* TODO - fully implement case insensitive version*/); — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Streaming/ConduitT/Internal/ConduitT.ABC.cs:84— // TODO: Deal with errors? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Streaming/SourceT/DSL/FoldUntilSourceT.cs:14— // TODO: Schedule — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Streaming/SourceT/DSL/FoldWhileSourceT.cs:14— // TODO: Schedule — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Tests/LensTests.cs:1— /*
TODO: Restore when we have SourceGen
using System;
using Xunit;
using static LanguageExt.Prelude;
namespace LanguageExt.Tests
{
public class LensTests
{
[Fact]
public void LensMutate()
{
var car = new Car("Maserati", "Ghibli", 20000);
var editor = new Editor("Joe Bloggs", 50000, car);
var book = new Book("Editors of the World", "Sarah Bloggs", editor);
var bookEditorCarMileage = lens(Book.editor, Editor.car, Car.mileage);
var mileage = bookEditorCarMileage.Get(book);
var book2 = bookEditorCarMileage.Set(25000, book);
Assert.True(book2.Editor.Car.Mileage == 25000);
}
[Fact]
public void CollectionsMutate()
{
var person = new Person("Paul", "Louth", Map(
(1, new Appt(1, DateTime.Parse("1/1/2010"), ApptState.NotArrived)),
(2, new Appt(2, DateTime.Parse("2/1/2010"), ApptState.NotArrived)),
(3, new Appt(3, DateTime.Parse("3/1/2010"), ApptState.NotArrived))));
Lens<Person, ApptState> arrive(int id) =>
lens(Person.appts, Map<int, Appt>.item(id), Appt.state);
var person2 = arrive(2).Set(ApptState.Arrived, person);
Assert.True(person2.Appts[2].State == ApptState.Arrived);
}
}
[WithLens]
public partial class Person : Record<Person>
{
public readonly string Name;
public readonly string Surname;
public readonly Map<int, Appt> Appts;
public Person(string name, string surname, Map<int, Appt> appts)
{
Name = name;
Surname = surname;
Appts = appts;
}
}
[WithLens]
public partial class Appt : Record<Appt>
{
public readonly int Id;
public readonly DateTime StartDate;
public readonly ApptState State;
public Appt(int id, DateTime startDate, ApptState state)
{
Id = id;
StartDate = startDate;
State = state;
}
}
public enum ApptState
{
NotArrived,
Arrived,
DNA,
Cancelled
}
[WithLens]
public partial class Car : Record<Car>
{
public readonly string Make;
public readonly string Model;
public readonly int Mileage;
public Car(string make, string model, int mileage)
{
Make = make;
Model = model;
Mileage = mileage;
}
}
[WithLens]
public partial class Editor : Record<Editor>
{
public readonly string Name;
public readonly int Salary;
public readonly Car Car;
public Editor(string name, int salary, Car car)
{
Name = name;
Salary = salary;
Car = car;
}
}
[WithLens]
public partial class Book : Record<Book>
{
public readonly string Name;
public readonly string Author;
public readonly Editor Editor;
public Book(string name, string author, Editor editor)
{
Name = name;
Author = author;
Editor = editor;
}
}
}
*/ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Tests/MonadTests.cs:102— // TODO: Restore when traits are complete — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Tests/OptionTTests.cs:190— // .FilterT(x => x > 2); <-- TODO: Above was this -- should we restore a filter operation? Can we even? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Tests/OptionUnsafeApply.cs:11— // TODO: Restore — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment LanguageExt.Tests/TraitTests/ApplicativeLawTests.cs:60— // TODO: Restore — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FileTooLong: TrieMap/TrieMap.cs LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:0— FileTooLong — 1321 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: Map/Map.Internal.cs LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:0— FileTooLong — 1233 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: AtomHashMap/AtomHashMap.Eq.cs LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:0— FileTooLong — 974 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: AtomHashMap/AtomHashMap.cs LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:0— FileTooLong — 967 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: Utility/IL.cs LanguageExt.Core/Utility/IL.cs:0— FileTooLong — 809 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: Internal/Set.Internal.cs LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:0— FileTooLong — 707 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: Internal/Lst.Internal.cs LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:0— FileTooLong — 671 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: Map/Map.cs LanguageExt.Core/Immutable Collections/Map/Map.cs:0— FileTooLong — 634 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: Iterable/Iterable.cs LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:0— FileTooLong — 625 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: AtomSeq/AtomSeq.cs LanguageExt.Core/Concurrency/AtomSeq/AtomSeq.cs:0— FileTooLong — 606 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: HashMap/HashMap.Eq.cs LanguageExt.Core/Immutable Collections/HashMap/HashMap.Eq.cs:0— FileTooLong — 587 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: Immutable Collections/Prelude.Collections.cs LanguageExt.Core/Immutable Collections/Prelude.Collections.cs:0— FileTooLong — 587 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: TrieSet/TrieSet.cs LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:0— FileTooLong — 571 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: HashMap/HashMap.cs LanguageExt.Core/Immutable Collections/HashMap/HashMap.cs:0— FileTooLong — 564 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: Arr/Arr.cs LanguageExt.Core/Immutable Collections/Arr/Arr.cs:0— FileTooLong — 535 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: Seq/Seq.cs LanguageExt.Core/Immutable Collections/Seq/Seq.cs:0— FileTooLong — 516 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 (13 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:250— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:250-262 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:276-288 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:250` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:287— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:287-299 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:313-325 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:287` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1032— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1032-1044 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1058-1070 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1032` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1580— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1580-1592 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1598-1610 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1580` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1606— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1606-1618 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1624-1636 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1606` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1632— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1632-1644 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1651-1663 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1632` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1698— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1698-1710 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1717-1729 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1698` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1725— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1725-1737 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1744-1756 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1725` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1778— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1778-1790 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1797-1809 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1778` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1808— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1808-1820 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1827-1839 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1808` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1839— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1839-1851 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1858-1870 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1839` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1874— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1874-1886 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1893-1905 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1874` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:575— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:575-587 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1214-1227 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:575` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1108— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1108-1120 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1132-1144 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1108` 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) LanguageExt.Core/Utility/IL.cs:1161— LanguageExt.Core/Utility/IL.cs:1161-1173 | LanguageExt.Core/Utility/IL.cs:1212-1224 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Utility/IL.cs:1161` 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) LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:60— LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:60-72 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:63-75 — 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 `LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:673— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:673-687 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:699-713 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:673` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:734— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:734-748 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:760-774 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:734` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:764— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:764-778 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:790-804 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:764` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:797— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:797-811 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:823-837 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:797` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:827— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:827-841 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:853-867 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:827` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:959— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:959-973 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:985-999 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:959` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1149— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1149-1163 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1175-1189 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1149` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1182— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1182-1196 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1208-1222 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1182` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1220— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1220-1234 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1246-1260 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1220` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1252— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1252-1266 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:1278-1292 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1252` 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) LanguageExt.Parsec/Parsers/Prim.cs:377— LanguageExt.Parsec/Parsers/Prim.cs:377-391 | LanguageExt.Parsec/Parsers/Prim.cs:435-449 — both copies are in the same file, so extract the 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 `LanguageExt.Parsec/Parsers/Prim.cs:377` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) LanguageExt.Core/DataTypes/Compositions/FoldCompositions.cs:12— LanguageExt.Core/DataTypes/Compositions/FoldCompositions.cs:12-17 | LanguageExt.Core/DataTypes/Compositions/FoldCompositions.cs:24-29 — both copies are in the same file, so extract the 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 `LanguageExt.Core/DataTypes/Compositions/FoldCompositions.cs:12` 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 (6 lines × 2) LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:42— LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Extensions.cs:42-47 | LanguageExt.Core/DataTypes/ValueTuple/Tuple6/ValueTuple6.Prelude.cs:43-48 — 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 (6 lines × 2) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:656— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:656-661 | LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:674-679 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:656` 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 (6 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1931— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1931-1936 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1949-1954 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1931` 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 (6 lines × 2) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:910— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:910-915 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:927-932 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:910` 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 (6 lines × 2) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2624— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2624-2629 | LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:1111-1116 — 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 (6 lines × 2) LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:17— LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:17-22 | LanguageExt.Streaming/SourceT/DSL/Reader4SourceT.cs:18-23 — 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 `LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:17` 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 (6 lines × 2) LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:19— LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:19-24 | LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:26-31 — both copies are in the same file, so extract the block into 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) LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:50— LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:50-55 | LanguageExt.Megaparsec/ParsecT/DSL/Apply.cs:57-62 — both copies are in the same file, so extract the block into 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) LanguageExt.Megaparsec/ParsecT/DSL/Bind.cs:19— LanguageExt.Megaparsec/ParsecT/DSL/Bind.cs:19-24 | LanguageExt.Megaparsec/ParsecT/DSL/Bind.cs:26-31 — both copies are in the same file, so extract the block into 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) LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:87— LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:87-97 | LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs:129-139 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Effects/IO/DSL/IOFoldWhile.cs: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. 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:72— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:72-82 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:298-308 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs: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 (11 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107-117 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:371-381 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:107` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:237— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:237-247 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:275-285 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:237` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:348— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:348-358 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:421-431 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:348` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:600— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:600-610 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:632-642 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:600` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1054— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1054-1064 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1078-1088 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1054` 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 (11 lines × 2) LanguageExt.Core/Traits/Resolve/EqResolver.cs:56— LanguageExt.Core/Traits/Resolve/EqResolver.cs:56-66 | LanguageExt.Core/Traits/Resolve/HashableResolver.cs:33-43 — 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) LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldUntilTransducer.cs:48— LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldUntilTransducer.cs:48-58 | LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldWhileTransducer.cs:57-68 — 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 `LanguageExt.Streaming/Transducers/TransducerM/DSL/FoldUntilTransducer.cs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (10 lines × 2) LanguageExt.Core/Effects/IO/DSL/IOActions.cs:21— LanguageExt.Core/Effects/IO/DSL/IOActions.cs:21-30 | LanguageExt.Core/Effects/IO/DSL/IOActions.cs:48-57 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Effects/IO/DSL/IOActions.cs:21` 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 (10 lines × 2) LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:83— LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:83-92 | LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs:122-131 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Effects/IO/DSL/IOFoldUntil.cs: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 (10 lines × 2) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:297— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:297-306 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:736-745 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:297` 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 (10 lines × 2) LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:84— LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:84-93 | LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs:112-121 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Monads/Alternative Monads/Validation/Extensions/Validation.Extensions.Apply.cs: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.
Duplicated block (10 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:781— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:781-790 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:814-823 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:781` 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 (10 lines × 2) LanguageExt.Core/Utility/Reflect.cs:106— LanguageExt.Core/Utility/Reflect.cs:106-115 | LanguageExt.Core/Utility/Reflect.cs:121-130 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Utility/Reflect.cs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) LanguageExt.Core/Utility/Reflect.cs:166— LanguageExt.Core/Utility/Reflect.cs:166-175 | LanguageExt.Core/Utility/Reflect.cs:182-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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Utility/Reflect.cs:166` 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) LanguageExt.Parsec/Parser.cs:120— LanguageExt.Parsec/Parser.cs:120-129 | LanguageExt.Parsec/Parser.cs:149-158 — both copies are in the same file, so extract the block into 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) LanguageExt.Parsec/ParserIO.cs:125— LanguageExt.Parsec/ParserIO.cs:125-134 | LanguageExt.Parsec/ParserIO.cs:154-163 — both copies are in the same file, so extract the block into 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) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Zip.cs:21— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Zip.cs:21-28 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Zip.cs:76-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Zip.cs:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1442— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1442-1449 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1498-1505 — both copies are in the same file, so extract the 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 (8 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1554— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1554-1561 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1610-1617 — both copies are in the same file, so extract the 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 (8 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1666— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1666-1673 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1722-1729 — both copies are in the same file, so extract the 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 (8 lines × 2) LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:31— LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:31-38 | LanguageExt.Benchmarks/HashMapRandomRemovalBenchmarks.cs:31-38 — 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 `LanguageExt.Benchmarks/HashMapContainsKeyBenchmarks.cs:31` 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) LanguageExt.Benchmarks/HashSetContainsBenchmarks.cs:27— LanguageExt.Benchmarks/HashSetContainsBenchmarks.cs:27-34 | LanguageExt.Benchmarks/HashSetIterationBenchmarks.cs:27-34 — 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 `LanguageExt.Benchmarks/HashSetContainsBenchmarks.cs:27` 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) LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:21— LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:21-28 | LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:51-58 — both copies are in the same file, so extract the 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 `LanguageExt.Megaparsec/ParsecT/DSL/Lift.cs:21` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:253— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:253-269 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:285-302 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:253` 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. 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) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:321— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:321-337 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:353-370 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:321` 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. 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) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1455— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1455-1471 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1511-1527 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1455` 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 (17 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1567— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1567-1583 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1623-1639 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1567` 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 (17 lines × 2) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1679— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1679-1695 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1735-1751 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1679` 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 (17 lines × 2) LanguageExt.Core/Utility/EnumerableOptimal.cs:168— LanguageExt.Core/Utility/EnumerableOptimal.cs:168-184 | LanguageExt.Core/Utility/EnumerableOptimal.cs:196-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Utility/EnumerableOptimal.cs:168` 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 (16 lines × 2) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:544— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:544-559 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:570-585 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:544` 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) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:579— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:579-594 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:605-620 — 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 `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:579` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:694— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:694-709 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:787-802 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:694` 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 (16 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:728— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:728-743 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:820-835 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:728` 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 (16 lines × 2) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1159— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1159-1174 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1190-1205 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1159` 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) LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:22— LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:22-37 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:71-86 — both copies are in the same file, so extract the 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 `LanguageExt.Streaming/Transducers/Transducer/DSL/FoldUntilTransducer.cs:22` 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) LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:59— LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:59-67 | LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:89-97 — both copies are in the same file, so extract the 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 `LanguageExt.Core/DataTypes/Compositions/Compositions.Module.cs:59` 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 (9 lines × 2) LanguageExt.Core/Utility/IL.cs:1185— LanguageExt.Core/Utility/IL.cs:1185-1193 | LanguageExt.Core/Utility/IL.cs:1228-1236 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Utility/IL.cs:1185` 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) LanguageExt.Parsec/ParserIOs/Expr.cs:100— LanguageExt.Parsec/ParserIOs/Expr.cs:100-108 | LanguageExt.Parsec/ParserIOs/Expr.cs:115-123 — both copies are in the same file, so extract the 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 `LanguageExt.Parsec/ParserIOs/Expr.cs:100` 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 (9 lines × 2) LanguageExt.Parsec/Parsers/Expr.cs:103— LanguageExt.Parsec/Parsers/Expr.cs:103-111 | LanguageExt.Parsec/Parsers/Expr.cs:118-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Parsec/Parsers/Expr.cs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Samples/DomainTypesExamples/Vector.cs:159— Samples/DomainTypesExamples/Vector.cs:159-167 | Samples/DomainTypesExamples/Vector.cs:181-189 — both copies are in the same file, so extract the 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 `Samples/DomainTypesExamples/Vector.cs:159` 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.
BarePragmaDisable LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Enumerable.cs:1— #pragma warning disable CS1998 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Singleton.cs:1— #pragma warning disable CS1998 // Async method lacks 'await' operators and will run synchronously — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.SingletonIO.cs:1— #pragma warning disable CS1998 // Async method lacks 'await' operators and will run synchronously — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Strict.cs:1— #pragma warning disable CS1998 // Async method lacks 'await' operators and will run synchronously — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
Duplicated block (19 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:444— LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:444-462 | LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:468-486 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:444` 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) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:507— LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:507-525 | LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:532-550 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:507` 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) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1261— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1261-1279 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1298-1316 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1261` 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 (19 lines × 2) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1335— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1335-1353 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1372-1390 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1335` 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) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1273— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1273-1284 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1295-1307 — both copies are in the same file, so extract the block into 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:665— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:665-676 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:757-768 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:665` 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) LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:499— LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:499-510 | LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:582-593 — both copies are in the same file, so extract the 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 `LanguageExt.Streaming/Pipes/PipeT/PipeT.Module.cs:499` 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) LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:26— LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:26-37 | LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:74-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 `LanguageExt.Streaming/Transducers/Transducer/DSL/FoldWhileTransducer.cs:26` 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) LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:42— LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Extensions.cs:42-48 | LanguageExt.Core/DataTypes/ValueTuple/Tuple7/ValueTuple7.Prelude.cs:43-49 — 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) LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:191— LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:191-197 | LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:201-209 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Arr/Trait/Arr.TraitImpl.cs:191` 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) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:479— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:479-485 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:554-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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:479` 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) LanguageExt.Core/Utility/IL.cs:773— LanguageExt.Core/Utility/IL.cs:773-780 | LanguageExt.Core/Utility/IL.cs:850-856 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: AtomHashMap (LCOM4 6) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:23— AtomHashMap's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: AtomHashMap (LCOM4 6) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:24— AtomHashMap's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: LstInternal (LCOM4 4) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:17— LstInternal's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: SeqLazy (LCOM4 4) LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:11— SeqLazy's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
VectorClock.relation (cyclomatic 19) LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:259— VectorClock.relation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VectorClock.relation (cyclomatic 19) LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:260— VectorClock.relation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Iterable.Bind (cyclomatic 16) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:432— Iterable.Bind has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Iterable.Bind (cyclomatic 16) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:495— Iterable.Bind has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Iterable.Bind (cognitive 41) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:432— Iterable.Bind has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Iterable.Bind (cognitive 41) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:495— Iterable.Bind has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
IterableAdd.FoldWhileIO (cognitive 31) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:80— IterableAdd.FoldWhileIO has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 85, 121). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
IterableAdd.FoldWhileIO (cognitive 31) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:158— IterableAdd.FoldWhileIO has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 160, 196). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
IterableAdd.FoldUntilIO (cognitive 31) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:233— IterableAdd.FoldUntilIO has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 238, 270). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
IterableAdd.FoldUntilIO (cognitive 31) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:304— IterableAdd.FoldUntilIO has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 306, 338). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
VectorClock.relation (cognitive 29) LanguageExt.Core/Concurrency/VectorClock/VectorClock.A.cs:259— VectorClock.relation has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
VectorClock.relation (cognitive 29) LanguageExt.Core/Concurrency/VectorClock/VectorClock.OrdA.NumB.A.B.cs:260— VectorClock.relation has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Entries.Update (cognitive 24) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2289— Entries.Update has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Entries.Update (cognitive 24) LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:779— Entries.Update has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Entries.Remove (cognitive 21) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2168— Entries.Remove has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Entries.Remove (cognitive 21) LanguageExt.Core/Immutable Collections/TrieSet/TrieSet.cs:664— Entries.Remove has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
IterableConcat.FoldWhileIO (cognitive 18) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:51— IterableConcat.FoldWhileIO has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 52). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
IterableConcat.FoldWhileIO (cognitive 18) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:84— IterableConcat.FoldWhileIO has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 85). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
IterableConcat.FoldUntilIO (cognitive 18) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:117— IterableConcat.FoldUntilIO has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 118). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
IterableConcat.FoldUntilIO (cognitive 18) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:149— IterableConcat.FoldUntilIO has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 150). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Change coupling: Try.Extensions.cs ↔ TryT.Extensions.cs LanguageExt.Core/Monads/Alternative Monads/Try/Extensions/Try.Extensions.cs— `LanguageExt.Core/Monads/Alternative Monads/Try/Extensions/Try.Extensions.cs` and `LanguageExt.Core/Monads/Alternative Monads/TryT/Extensions/TryT.Extensions.cs` change together 60% of the time (6 of the 10 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: Conduit.cs ↔ ConduitT.cs LanguageExt.Streaming/Conduit/Conduit.cs— `LanguageExt.Streaming/Conduit/Conduit.cs` and `LanguageExt.Streaming/ConduitT/ConduitT.cs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). 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 (20 lines × 2) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:101— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:101-120 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:137-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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:101` 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. 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) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:176— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:176-195 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:212-231 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:176` 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. 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) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2363— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2363-2380 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2400-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. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2363` 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) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2438— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2438-2455 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2474-2491 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2438` 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) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1167— LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1167-1183 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorK.cs:92-108 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorKV.cs:92-108 | LanguageExt.Core/Immutable Collections/Map/Map.EnumeratorV.cs:92-108 — 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 `LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:1167` 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 × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1388— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1388-1404 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1432-1448 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1476-1492 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1520-1536 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1388` 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) LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2302— LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2302-2315 | LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2491-2504 — both copies are in the same file, so extract the 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 `LanguageExt.Core/Immutable Collections/TrieMap/TrieMap.cs:2302` 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 (14 lines × 2) LanguageExt.Core/Utility/IL.cs:1030— LanguageExt.Core/Utility/IL.cs:1030-1043 | LanguageExt.Core/Utility/IL.cs:1108-1121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 3) LanguageExt.Core/Utility/Reflect.cs:252— LanguageExt.Core/Utility/Reflect.cs:252-261 | LanguageExt.Core/Utility/Reflect.cs:267-276 | LanguageExt.Core/Utility/Reflect.cs:283-292 — 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 `LanguageExt.Core/Utility/Reflect.cs:252` 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) Samples/DomainTypesExamples/Vector.cs:84— Samples/DomainTypesExamples/Vector.cs:84-93 | Samples/DomainTypesExamples/Vector.cs:108-117 | Samples/DomainTypesExamples/Vector.cs:135-144 — 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 `Samples/DomainTypesExamples/Vector.cs: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.
Internal.chaini (cyclomatic 29) LanguageExt.Parsec/Parsec.Internal.cs:85— Internal.chaini has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 88). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
InternalIO.chaini (cyclomatic 29) LanguageExt.Parsec/ParsecIO.Internal.cs:79— InternalIO.chaini has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 82). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Patch.Combine (cyclomatic 21) LanguageExt.Core/DataTypes/Patch/Patch.cs:105— Patch.Combine has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Patch.composable (cyclomatic 21) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:137— Patch.composable has cyclomatic complexity 21 (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.
TaskExtensions.WindowMap (cyclomatic 19) LanguageExt.Core/Concurrency/Task/Task.Extensions.cs:303— TaskExtensions.WindowMap has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Patch.transformWith (cyclomatic 19) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:374— Patch.transformWith has cyclomatic complexity 19 (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.
ParserExtensions.SelectMany (cyclomatic 19) LanguageExt.Parsec/Parser.cs:107— ParserExtensions.SelectMany has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 111). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ParserIOExtensions.SelectMany (cyclomatic 19) LanguageExt.Parsec/ParserIO.cs:112— ParserIOExtensions.SelectMany has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 116). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
IO.RunAsyncInternal (cyclomatic 17) LanguageExt.Core/Effects/IO/IO.cs:917— IO.RunAsyncInternal has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ListModule.Remove (cyclomatic 17) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:848— ListModule.Remove has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ListModule.Remove (cyclomatic 16) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:799— ListModule.Remove has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BarePragmaDisable repeated across 24 files LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:1— The identical BarePragmaDisable (`#pragma warning disable CS0693 // Type parameter has the same name as the type parameter from outer type`) appears in 24 files (24 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 24 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
Internal.chaini (cognitive 74) LanguageExt.Parsec/Parsec.Internal.cs:85— Internal.chaini has cognitive complexity 74 (threshold 15). Most of this is not in the body itself: 1 of the 74 points is its own statement and the rest belongs to one function literal inside it that branches (line 88). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
InternalIO.chaini (cognitive 74) LanguageExt.Parsec/ParsecIO.Internal.cs:79— InternalIO.chaini has cognitive complexity 74 (threshold 15). Most of this is not in the body itself: 1 of the 74 points is its own statement and the rest belongs to one function literal inside it that branches (line 82). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
IO.RunAsyncInternal (cognitive 31) LanguageExt.Core/Effects/IO/IO.cs:917— IO.RunAsyncInternal has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Patch.Combine (cognitive 29) LanguageExt.Core/DataTypes/Patch/Patch.cs:105— Patch.Combine has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskExtensions.WindowMap (cognitive 28) LanguageExt.Core/Concurrency/Task/Task.Extensions.cs:303— TaskExtensions.WindowMap has cognitive complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
Iterable.CompareToIO (cognitive 27) LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs:1029— Iterable.CompareToIO has cognitive complexity 27 (threshold 15). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1036, 1060). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ParserExtensions.SelectMany (cognitive 24) LanguageExt.Parsec/Parser.cs:107— ParserExtensions.SelectMany has cognitive complexity 24 (threshold 15). Most of this is not in the body itself: 0 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 111). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ParserIOExtensions.SelectMany (cognitive 24) LanguageExt.Parsec/ParserIO.cs:112— ParserIOExtensions.SelectMany has cognitive complexity 24 (threshold 15). Most of this is not in the body itself: 0 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 116). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Reach.offset (cognitive 24) LanguageExt.Megaparsec/Reach.cs:18— Reach.offset has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ListModule.Remove (cognitive 22) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:848— ListModule.Remove has cognitive complexity 22 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
IL.ToString (cognitive 22) LanguageExt.Core/Utility/IL.cs:837— IL.ToString has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Common.mergeError (cognitive 22) LanguageExt.Parsec/Common.cs:16— Common.mergeError has cognitive complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Patch.transformWith (cognitive 21) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:374— Patch.transformWith has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ListModule.Remove (cognitive 21) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:799— ListModule.Remove has cognitive complexity 21 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BindIter.MoveNext (cognitive 20) LanguageExt.Core/Utility/EnumerableOptimal.cs:163— BindIter.MoveNext has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Prim.manyn0 (cognitive 19) LanguageExt.Parsec/Parsers/Prim.cs:432— Prim.manyn0 has cognitive complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 435). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
IO.RunAsync (cognitive 18) LanguageExt.Core/Effects/IO/IO.cs:835— IO.RunAsync has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ListModule.Remove (cognitive 17) LanguageExt.Core/Immutable Collections/List/Internal/Lst.Internal.cs:897— ListModule.Remove has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SeqLazy.Take (cognitive 17) LanguageExt.Core/Immutable Collections/Seq/DSL/SeqLazy.cs:393— SeqLazy.Take has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Patch.apply (cognitive 16) LanguageExt.Core/DataTypes/Patch/Patch.Module.cs:273— Patch.apply has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConsValueEnum.TailAsync (cognitive 16) LanguageExt.Core/Immutable Collections/IteratorAsync/DSL/IteratorAsync.ConsValueEnum.cs:76— ConsValueEnum.TailAsync has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ClassTooLong: IL LanguageExt.Core/Utility/IL.cs:0— ClassTooLong — 776 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Duplicated block (15 lines × 4) LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:384— LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:384-398 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:922-936 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:410-424 | LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.Eq.cs:948-962 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `LanguageExt.Core/Concurrency/AtomHashMap/AtomHashMap.cs:384` 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 × 5) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:375— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:375-388 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:132-145 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Cast.cs:65-78 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:182-195 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Enumerable.cs:115-128 — 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 `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:375` 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 × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:849— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:849-862 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:878-891 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:907-920 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:936-949 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:849` 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 × 5) LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:397— LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:397-409 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.AsyncEnumerable.cs:157-169 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Cast.cs:84-96 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Concat.cs:201-213 | LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Enumerable.cs:151-163 — 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 `LanguageExt.Core/Immutable Collections/Iterable/DSL/Iterable.Add.cs:397` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 4) LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1558— LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1558-1569 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1588-1599 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1618-1629 | LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1648-1659 — 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 `LanguageExt.Core/Traits/Foldable/Foldable.Trait.cs:1558` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 4) LanguageExt.Core/Utility/Reflect.cs:238— LanguageExt.Core/Utility/Reflect.cs:238-246 | LanguageExt.Core/Utility/Reflect.cs:252-260 | LanguageExt.Core/Utility/Reflect.cs:267-275 | LanguageExt.Core/Utility/Reflect.cs:283-291 — 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 `LanguageExt.Core/Utility/Reflect.cs:238` 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 × 3) LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:973— LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:973-981 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:995-1003 | LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:1017-1025 — 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 `LanguageExt.Core/Immutable Collections/Set/Internal/Set.Internal.cs:973` 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 (6 lines × 3) LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1993— LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1993-1998 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2059-2064 | LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:2081-2086 — 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 `LanguageExt.Core/Immutable Collections/Map/Map.Internal.cs:1993` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) LanguageExt.Streaming/SourceT/DSL/Reader2SourceT.cs:14— LanguageExt.Streaming/SourceT/DSL/Reader2SourceT.cs:14-18 | LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:17-21 | LanguageExt.Streaming/SourceT/DSL/Reader4SourceT.cs:18-22 — 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 `LanguageExt.Streaming/SourceT/DSL/Reader2SourceT.cs: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. 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) LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:25— LanguageExt.Streaming/SourceT/DSL/Reader3SourceT.cs:25-29 | LanguageExt.Streaming/SourceT/DSL/Reader4SourceT.cs:27-31 — 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. 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.
Off the main sequence: LanguageExt.Core — LanguageExt.Core: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
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 — 9 finding(s)
D11 · Test Reliability· Test runner surfaced no tests · ×1
Test runner surfaced no tests — Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 1434 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 104 significant file(s) lose their only recent owner: LanguageExt.Core/Immutable Collections/Map/Map.cs, LanguageExt.Core/Immutable Collections/Iterable/Iterable.cs, LanguageExt.Core/Immutable Collections/List/Lst.Module.cs, LanguageExt.Core/Monads/Alternative Monads/Option/Option.cs, LanguageExt.Core/Immutable Collections/Prelude.Collections.cs, LanguageExt.Core/Immutable Collections/Seq/Seq.cs, LanguageExt.Core/Monads/Alternative Monads/Validation/Validation.cs, LanguageExt.Core/Monads/Alternative Monads/Either/Either.cs (+96 more). Pair on, review, or document these before any departure.
Thin analysable surface across projects — 3 project(s) carry only a thin slice of real code (e.g. `TestBed.Web.Runner` with 19 significant line(s)). The mean analysable-surface weight is 90 %, lowering Solution Shape by about 0.79 point(s). Consolidate thin projects or grow them into substantial, well-scoped assemblies.
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 169641 LoC spread over 23 projects the codebase is large and multi-module, so explicit bounded contexts are needed. Name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
Split LanguageExt.Core — A .NET library whose core namespace is already huge (19 namespaces) and whose name implies a single cohesive domain. Suggested: by namespace: LanguageExt.Text, LanguageExt.Collections, LanguageExt.Math
Scattered collaborators — 56 % of calls cross a namespace and only 46 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 2 of 600 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — largest first: LanguageExt.Core/Effects/Schedule/Duration.cs, LanguageExt.Core/Prism/Prelude_Prism.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Build status unknown — The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
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.
dotnet: not applicable — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies 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 019fd2c5-c759-76fc-b9ed-056e2adcf904 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 6 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by name with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.
Issues: 15 · Warnings: 369 · Recommendations: 9 · Info: 11 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 05-08-2026 @ 16:33 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.