Public report — subtitleedit, 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.
2723findings with an exact file:lineof 2755 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
53/93dimensions across the health lenses449254 LoC · 9 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.
SubtitleEdit/subtitleedit carries serious gaps (48%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
The area that most needs attention is Security (31%) — exposure to security and compliance incidents is elevated. Readiness (57%) is the next concern — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade.
Leadership focus, highest impact first: Encrypt sensitive data at rest (ASP.NET Core Data Protection /… (Data Protection); 50 High finding(s) (Static Analysis (SAST)); Review each MD5/SHA1 use by what it protects (Cryptographic Hygiene).
For scale: Large (~449,254 production lines); rebuilding it from scratch would take roughly ~22.1 person-years (~12–43 engineers). Approximate, ±~30%.
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 ~22.1 person-years of build effort (about ~€3,200,000 to rebuild). Its weakest lens is Security at 31% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.4) — desktop/game, CQRS, high decision density × 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
Resolve the 6 Secret finding(s) in Secrets (history) — start with Settings.cs (4), Constants.cs (2).
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.).
Value concentrated against a weak lens · High · Value at risk
This is a Large asset (~22.1 person-years to rebuild), and its weakest lens is Security at 31%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Security first — highest risk-reduction per euro on an asset this size.
The top fix pays for itself · High · Economics
The top-ranked fix costs roughly 1–3 engineer-days once. Not doing it costs about 126.3–757.8 engineer-days every year, paid as drag on the ~1,020,974 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 1–2 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 5–11% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.
Evidence: D15 churn: 251,747 line(s) changed over a 90-day window ⇒ ~1,020,974/year · D1/D2/D4/D6 code quality: averaging 6.0/10 ⇒ a 5–11% drag on each change · top-ranked remediation: Low effort ⇒ about 1–3 engineer-day(s)
→ Do the top-ranked fix now if this code will still be yours in 2 months.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: 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.). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ 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.).
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 6.0/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 5–11% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4/D6 code quality: averaging 6.0/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
Architecture — module dependency 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
277 modules, 780 dependencies — 5 dependency cycles, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 70% · Adequate · gated by D1, D2
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
50
High / Critical
A02:2021 — Cryptographic Failures
8
High / Critical
Roadmap
Begin by encrypting sensitive data at rest and managing keys in a vault, or confirm this is handled by infrastructure. Next, resolve the 50 high-severity static analysis findings, prioritizing the build pipelines for seconv, UI, and Flatpak. Simultaneously, replace weak MD5 and SHA-1 hashes with SHA-256 or non-cryptographic alternatives where appropriate, and address the six historical secret exposures in Settings.cs and Constants.cs. Finally, integrate a security scanning step into the CI pipeline to fail builds on new vulnerabilities, ensuring security regressions are caught early.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 Secret finding(s) in Secrets (history) — start with Settings.cs (4), Constants.cs (2).
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.).
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
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. 50 of 53 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.7 — 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 — 53 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, 2723 of 2755 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D24 Comment Value — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D20, D21, D22, 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.
663 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RemoveTextForHI.RemoveColon at 279. A further 29 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 HtmlUtil.EncodeNamed at 89 — they are counted neither in the figure above nor in this dimension's score.
+ 657 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 DialogSplitMerge.FixDashes (cyclomatic 35) finding(s) in Cyclomatic Complexity — start with DialogSplitMerge.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 RemoveTextForHI.RemoveColon (cyclomatic 279) finding(s) in Cyclomatic Complexity — start with RemoveTextForHI.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 RemoveInterjection.Invoke (cyclomatic 268) finding(s) in Cyclomatic Complexity — start with RemoveInterjection.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 1084 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 DialogSplitMerge.FixDashes (cognitive 52) finding(s) in Cognitive Complexity — start with DialogSplitMerge.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 DvbSubPes.DvbSubPes.ctor (cognitive 16) finding(s) in Cognitive Complexity — start with DvbSubPes.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 RemoveTextForHI.RemoveColon (cognitive 552) finding(s) in Cognitive Complexity — start with RemoveTextForHI.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 84 FileTooLong finding(s) in God Classes — start with MainViewModel.cs, OcrViewModel.cs, SpeechToTextViewModel.cs. — One of this dimension's main actionable groups (84 warning-level).
Resolve the 63 ClassTooLong finding(s) in God Classes — start with Ebu.cs (2), LanguageGeneral.cs, DownloadHashManager.cs. — One of this dimension's main actionable groups (63 warning-level).
Resolve the 56 TooManyMethods finding(s) in God Classes — start with MainViewModel.cs, OcrViewModel.cs, BinaryEditViewModel.cs. — One of this dimension's main actionable groups (56 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 69 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 · Coupling10.0 / 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.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Per-file coverage withheld — the coverage run did not finish
What to do
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_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.
1658 test methods: 1658 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 Quality10.0 / 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.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1658 tests.
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md.
Do you agree with this assessment?
D11 · Test Reliability8.0 / 10Strong✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
Resolve the 3 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with Constants.cs. — One of this dimension's main actionable groups (1 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainViewModel.cs, SpeechToTextViewModel.cs, DownloadTtsViewModel.cs. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor6.6 / 10Adequate✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
461 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/ui/Features/Video/TextToSpeech/TextToSpeechViewModel.cs.
Off-boarding risk: anonymized user #1 · ×4
Further sole-owners (lower concentration)
What to do
Resolve the 4 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (4 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) 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.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API Consistency / 10Weak◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
3 API inconsistencies across a 400-member sample of 1636 exposed types.
Redundant/Conflicting Position Representation: PcsObject uses a custom struct `BluRayPoint` for its origin, while PcsData (which likely contains the same logical data) exposes a different type `Position` via a method. This creates confusion about which type to use for positioning.
Inconsistent Exposure of Frame Rates: Frame rate constants are exposed as public static fields (e.g., `Fps24P`), but there is no corresponding method or property to retrieve them, and the naming convention (`Fps` prefix) is inconsistent with other utility classes like `ToolBox` which use methods. Additionally, `FpsTrg` is a field while others are fields, but the lack of a unified `GetFrameRate(string type)` or similar API makes them feel like scattered constants rather than a cohesive API.
Inconsistent Parsing Method Signatures: The parser uses multiple methods with identical signatures `(int a, int b)` for different parsing tasks (`ParseChars`, `ParseCmd`, etc.). This is a code smell indicating that the parser is likely a state machine or switch-case block internally, but exposed as distinct public methods. It makes the API feel like an implementation detail rather than a clean interface.
What to do
Resolve the 1 Redundant/Conflicting Position Representation finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent Exposure of Frame Rates finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent Parsing Method Signatures finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion2.5 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
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.
71 % of calls cross a namespace and 2 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
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.
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: generic-api-key · ×6src/UI/Logic/Ocr/GoogleLens/Constants.cs:8detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 6 Secret finding(s) in Secrets (history) — start with Settings.cs (4), Constants.cs (2). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: github-actions-mutable-action-tag · ×50.github/workflows/build-flatpak.yml:28detected by semgrep finding
What to do
Resolve the 50 High finding(s) in Static Analysis (SAST) — start with build-seconv.yml (22), build-ui.yml (21), build-flatpak.yml (7). — One of this dimension's main actionable groups (50 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
5 of 1530 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/libse/Common/ConvertColorsToDialogUtils.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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Secret passed as a command-line argument finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D39 · IL Efficiency9.0 / 10Strong✓ Tool-verified
Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.
328 of 6464 first-party methods have an oversized IL body.
IL efficiency: 328 authored method(s) exceed the IL budgetsrc/libse/SubtitleFormats/Cavena890.cs:1693
What to do
Resolve the 1 IL efficiency finding(s) in IL Efficiency — start with Cavena890.cs. — One of this dimension's main actionable groups (1 recommendation-level).
Enforce IL Efficiency in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d39_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
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 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.
`ITextBoxWrapper` declares 24 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. — ITextBoxWrapper.cs:9
`ISpellCheckManager` 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. — ISpellCheckManager.cs:8
`ISpeechToTextEngine` 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. — ISpeechToTextEngine.cs:8
`ITtsEngine` 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. — ITtsEngine.cs:7
`IFindService` 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. — IFindService.cs:6
`ITtsDownloadService` 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. — TtsDownloadService.cs:21
`IVideoPlayer` 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. — IVideoPlayer.cs:6
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`PreviewItem` (slice 'Edit') depends on `SubtitleLineViewModel` from slice 'Main'. — PreviewItem.cs:6
`SettingsViewModel` (slice 'Options') depends on `AlignmentItem` from slice 'Video'. — SettingsViewModel.cs:45
`ShortcutsViewModel` (slice 'Options') depends on `MainViewModel` from slice 'Main'. — ShortcutsViewModel.cs:24
`ExportImageBasedViewModel` (slice 'Files') depends on `SubtitleLineViewModel` from slice 'Main'. — ExportImageBasedViewModel.cs:33
`ImportPlainTextViewModel` (slice 'Files') depends on `SubtitleLineViewModel` from slice 'Main'. — ImportPlainTextViewModel.cs:26
`ForcedAlignerSetupViewModel` (slice 'Files') depends on `ForcedAlignerOption` from slice 'Video'. — ForcedAlignerSetupViewModel.cs:18
`MainViewModel` (slice 'Main') depends on `VideoPlayerUndockedViewModel` from slice 'Shared'. — MainViewModel.cs:191
`AiAssistantViewModel` (slice 'Main') depends on `LlamaCppModelDisplay` from slice 'Translate'. — AiAssistantViewModel.cs:29
`OcrViewModel` (slice 'Ocr') depends on `LlamaCppModelDisplay` from slice 'Translate'. — OcrViewModel.cs:66
`DownloadPaddleOcrViewModel` (slice 'Ocr') depends on `IndeterminateProgressHelper` from slice 'Shared'. — DownloadPaddleOcrViewModel.cs:23
`BinaryEditViewModel` (slice 'Shared') depends on `IOcrSubtitle` from slice 'Ocr'. — BinaryEditViewModel.cs:39
`BookmarksListViewModel` (slice 'Shared') depends on `SubtitleLineViewModel` from slice 'Main'. — BookmarksListViewModel.cs:16
`ErrorListItem` (slice 'Shared') depends on `SubtitleLineViewModel` from slice 'Main'. — ErrorListItem.cs:5
`FindTextViewModel` (slice 'Shared') depends on `SubtitleLineViewModel` from slice 'Main'. — FindTextViewModel.cs:16
`AudioClip` (slice 'Shared') depends on `SubtitleLineViewModel` from slice 'Main'. — AudioClip.cs:6
`PickRuleProfileViewModel` (slice 'Shared') depends on `ProfileDisplay` from slice 'Options'. — PickRuleProfileViewModel.cs:15
`PickSpellCheckDictionaryViewModel` (slice 'Shared') depends on `ISpellCheckManager` from slice 'SpellCheck'. — PickSpellCheckDictionaryViewModel.cs:22
`AudioVisualizerUndockedViewModel` (slice 'Shared') depends on `MainViewModel` from slice 'Main'. — AudioVisualizerUndockedViewModel.cs:11
`VideoPlayerUndockedViewModel` (slice 'Shared') depends on `MainViewModel` from slice 'Main'. — VideoPlayerUndockedViewModel.cs:15
`SpellCheckResult` (slice 'SpellCheck') depends on `SubtitleLineViewModel` from slice 'Main'. — SpellCheckResult.cs:8
`SpellCheckViewModel` (slice 'SpellCheck') depends on `SubtitleLineViewModel` from slice 'Main'. — SpellCheckViewModel.cs:37
`SpellCheckWordChangedEvent` (slice 'SpellCheck') depends on `SubtitleLineViewModel` from slice 'Main'. — SpellCheckWordChangedEvent.cs:7
`DoubleLineItem` (slice 'SpellCheck') depends on `SubtitleLineViewModel` from slice 'Main'. — DoubleLineItem.cs:5
`DoubleWordItem` (slice 'SpellCheck') depends on `SubtitleLineViewModel` from slice 'Main'. — DoubleWordItem.cs:5
`PointSyncViewModel` (slice 'Sync') depends on `SubtitleLineViewModel` from slice 'Main'. — PointSyncViewModel.cs:20
`SubtitleDisplayItem` (slice 'Sync') depends on `SubtitleLineViewModel` from slice 'Main'. (×2) — SubtitleDisplayItem.cs:7, SubtitleDisplayItem.cs:7
`PointSyncViaOtherViewModel` (slice 'Sync') depends on `SubtitleLineViewModel` from slice 'Main'. — PointSyncViaOtherViewModel.cs:22
`AiReviewViewModel` (slice 'Tools') depends on `LlamaCppModelDisplay` from slice 'Translate'. — AiReviewViewModel.cs:26
`ApplyDurationLimitItem` (slice 'Tools') depends on `SubtitleLineViewModel` from slice 'Main'. — ApplyDurationLimitItem.cs:6
`ApplyDurationLimitsViewModel` (slice 'Tools') depends on `SubtitleLineViewModel` from slice 'Main'. — ApplyDurationLimitsViewModel.cs:18
`ApplyMinGapItem` (slice 'Tools') depends on `SubtitleLineViewModel` from slice 'Main'. — ApplyMinGapItem.cs:7
`BatchConvertAssaViewModel` (slice 'Tools') depends on `ITextBoxWrapper` from slice 'Shared'. — BatchConvertAssaViewModel.cs:22
`TransportStreamResult` (slice 'Tools') depends on `IOcrSubtitle` from slice 'Ocr'. — BatchConverter.cs:412
`BatchConvertSettingsViewModel` (slice 'Tools') depends on `TesseractEngineModeItem` from slice 'Ocr'. — BatchConvertSettingsViewModel.cs:24
`BatchConvertViewModel` (slice 'Tools') depends on `SpeechToTextModelDisplay` from slice 'Video'. — BatchConvertViewModel.cs:52
`BatchErrorListItem` (slice 'Tools') depends on `SubtitleLineViewModel` from slice 'Main'. — BatchErrorListItem.cs:5
`BridgeGapDisplayItem` (slice 'Tools') depends on `SubtitleLineViewModel` from slice 'Main'. — BridgeGapDisplayItem.cs:7
`ChangeFormattingDisplayItem` (slice 'Tools') depends on `SubtitleLineViewModel` from slice 'Main'. — ChangeFormattingDisplayItem.cs:7
`ConvertActorsDisplayItem` (slice 'Tools') depends on `SubtitleLineViewModel` from slice 'Main'. — ConvertActorsDisplayItem.cs:7
15 further occurrence(s) are not listed individually; the score already reflects all 55.
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
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 Protection0.0 / 10Critical✓ 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.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
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. (×23) — EditCategoryViewModel.cs:53, CompareWindow.cs:158, ColorToBrushConverter.cs:20, …
A placeholder string ("Lorem ipsum dolor sit amet
consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in. — ContinuationUtilities.cs:1349
A placeholder string ("Lorem ipsum dolor sit amet.") is still in shipped code — typical of generated boilerplate that was never filled in. — DialogSplitMerge.cs:415
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.
`GetSubtitleFormatByFriendlyName` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Utilities.cs:3784
`DoSpell` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — EmptyFixCallback.cs:74
`ToText` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×10) — AdobePremierePrProj.cs:31, AribB36.cs:367, Ayato.cs:34, …
`Save` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — AribB36.cs:372, NciCaption.cs:17
`GetIsForced` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — PlayStationSubs.cs:211
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 5 of 8 project(s) that lack one — worth up to 1.3 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.
Only 4/9 projects share a common root namespace — the code's module identity is inconsistent.
What to do
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.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries. Exhaustive, deterministic.
3408/4233 types (81%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
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) as a CI step.
What to do
Add a SAST step to CI running 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 — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.
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 100 use(s) across 449,369 production line(s) (~0.2/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.
12 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 · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored.
MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — BaiduTranslate.cs:133
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
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 — 40 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.
AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
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.
D19 Documentation Quality — LLM evaluation failed
D23 Boundary Type-Coupling — Bounded contexts not declared
D24 Comment Value — LLM evaluation failed
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
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.
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.
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
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this check looks for (2 value object(s))
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this check looks for (2 CQRS handler(s))
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 — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — coverage data present but no domain-layer files were identified (no /Domain//Aggregates/ paths)
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
EmptyCatchBlock src/libse/Common/DvdSubtitleLanguage.cs:295— 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 src/libse/Common/FileUtil.cs:831— 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 src/libse/Common/FileUtil.cs:863— 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 src/libse/Common/LanguageAutoDetect.cs:1984— 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 src/libse/Common/SeLogger.cs:45— 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 src/libse/Common/SeLogger.cs:68— 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 src/libse/Common/UnknownFormatImporterJson.cs:40— 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 src/libse/Common/UnknownFormatImporterJson.cs:59— 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 src/libse/Common/UnknownFormatImporterJson.cs:78— 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 src/libse/SubtitleFormats/AdvancedSubStationAlpha.cs:564— 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 src/libse/SubtitleFormats/CapMakerPlus.cs:160— 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 src/libse/SubtitleFormats/DCinemaInterop.cs:578— 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 src/libse/SubtitleFormats/FinalCutProImage.cs:45— 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 src/libse/SubtitleFormats/FinalCutProTest2Xml.cs:108— 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 src/libse/SubtitleFormats/FinalCutProTextXml.cs:191— 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 src/libse/SubtitleFormats/FinalCutProXml.cs:403— 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 src/libse/SubtitleFormats/ItunesTimedText.cs:83— 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 src/libse/SubtitleFormats/NetflixTimedText.cs:93— 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 src/libse/SubtitleFormats/Pac.cs:2156— 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 src/libse/SubtitleFormats/PlayCaptionsFreeEditor.cs:41— 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 src/libse/SubtitleFormats/SmpteTt2052.cs:90— 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 src/libse/SubtitleFormats/SubStationAlpha.cs:283— 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 src/libse/SubtitleFormats/TimedText10.cs:187— 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 src/libse/SubtitleFormats/TimedText10.cs:427— 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 src/libse/SubtitleFormats/TimedText10.cs:847— 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.
High: github-actions-mutable-action-tag .github/workflows/build-flatpak.yml:28— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v5`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-flatpak.yml:31— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-flatpak.yml:50— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v5`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-flatpak.yml:65— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v5`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-flatpak.yml:68— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/download-artifact@<40-character SHA>`. This step references `actions/download-artifact@v5`; resolve the SHA it points at today with `gh api repos/actions/download-artifact/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-flatpak.yml:77— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: flatpak/flatpak-github-actions/flatpak-builder@<40-character SHA>`. This step references `flatpak/flatpak-github-actions/flatpak-builder@v6`; resolve the SHA it points at today with `gh api repos/flatpak/flatpak-github-actions/commits/v6 --jq .sha`. `flatpak/flatpak-github-actions/flatpak-builder` is hosted INSIDE the `flatpak/flatpak-github-actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `flatpak/flatpak-github-actions/flatpak-builder` path in `uses:` and query only `flatpak/flatpak-github-actions`.
High: github-actions-mutable-action-tag .github/workflows/build-flatpak.yml:85— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v5`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:54— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:57— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: run-shell-injection .github/workflows/build-seconv.yml:88— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-seconv.yml:91— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-seconv.yml:100— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:122— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:132— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:134— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: run-shell-injection .github/workflows/build-seconv.yml:162— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-seconv.yml:165— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-seconv.yml:175— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:193— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:204— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:207— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: run-shell-injection .github/workflows/build-seconv.yml:238— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-seconv.yml:241— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-seconv.yml:250— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/build-seconv.yml:272— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
Leaked secret: gcp-api-key src/ui/Logic/Ocr/GoogleLens/Constants.cs:8— gcp-api-key detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
NoWarnInCsproj tests/benchmarks/UiBenchmarks.csproj:17— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
FileTooLong: Main/MainViewModel.cs src/ui/Features/Main/MainViewModel.cs:0— FileTooLong — 12587 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: Ocr/OcrViewModel.cs src/ui/Features/Ocr/OcrViewModel.cs:0— FileTooLong — 3014 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: SpeechToText/SpeechToTextViewModel.cs src/ui/Features/Video/SpeechToText/SpeechToTextViewModel.cs:0— FileTooLong — 2621 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: Common/Utilities.cs src/libse/Common/Utilities.cs:0— FileTooLong — 2029 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: AudioVisualizerControl/AudioVisualizer.cs src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:0— FileTooLong — 2016 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: SubtitleFormats/Pac.cs src/libse/SubtitleFormats/Pac.cs:0— FileTooLong — 2001 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: TextToSpeech/TextToSpeechViewModel.cs src/ui/Features/Video/TextToSpeech/TextToSpeechViewModel.cs:0— FileTooLong — 1946 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: Settings/SettingsViewModel.cs src/ui/Features/Options/Settings/SettingsViewModel.cs:0— FileTooLong — 1833 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: Logic/UiUtil.cs src/ui/Logic/UiUtil.cs:0— FileTooLong — 1767 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: Download/DownloadHashManager.cs src/ui/Logic/Download/DownloadHashManager.cs:0— FileTooLong — 1572 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: BatchConvert/BatchConverter.cs src/ui/Features/Tools/BatchConvert/BatchConverter.cs:0— FileTooLong — 1571 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: SubtitleFormats/AdvancedSubStationAlpha.cs src/libse/SubtitleFormats/AdvancedSubStationAlpha.cs:0— FileTooLong — 1559 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: BatchConvert/BatchConvertViewModel.cs src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:0— FileTooLong — 1558 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: BinaryEdit/BinaryEditViewModel.cs src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:0— FileTooLong — 1554 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: SubtitleFormats/Ebu.cs src/libse/SubtitleFormats/Ebu.cs:0— FileTooLong — 1474 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: Language/LanguageGeneral.cs src/ui/Logic/Config/Language/LanguageGeneral.cs:0— FileTooLong — 1474 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: Translate/AutoTranslateViewModel.cs src/ui/Features/Translate/AutoTranslateViewModel.cs:0— FileTooLong — 1377 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: BurnIn/BurnInViewModel.cs src/ui/Features/Video/BurnIn/BurnInViewModel.cs:0— FileTooLong — 1339 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: SubtitleFormats/Cavena890.cs src/libse/SubtitleFormats/Cavena890.cs:0— FileTooLong — 1331 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: Common/LanguageAutoDetect.cs src/libse/Common/LanguageAutoDetect.cs:0— FileTooLong — 1307 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: DownloadTts/DownloadTtsViewModel.cs src/ui/Features/Video/TextToSpeech/DownloadTts/DownloadTtsViewModel.cs:0— FileTooLong — 1283 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: Layout/InitListViewAndEditBox.cs src/ui/Features/Main/Layout/InitListViewAndEditBox.cs:0— FileTooLong — 1175 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: ReviewSpeech/ReviewSpeechViewModel.cs src/ui/Features/Video/TextToSpeech/ReviewSpeech/ReviewSpeechViewModel.cs:0— FileTooLong — 1002 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: SyntaxTextEditorControl/SyntaxTextView.cs src/ui/Controls/SyntaxTextEditorControl/SyntaxTextView.cs:0— FileTooLong — 990 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: Common/HtmlUtil.cs src/libse/Common/HtmlUtil.cs:0— FileTooLong — 955 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.
ClassTooLong: LanguageGeneral src/ui/Logic/Config/Language/LanguageGeneral.cs:0— ClassTooLong — 1472 significant lines (blank, comment-only and punctuation-only lines excluded), 1 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.
ClassTooLong: DownloadHashManager src/ui/Logic/Download/DownloadHashManager.cs:0— ClassTooLong — 1421 significant lines (blank, comment-only and punctuation-only lines excluded), 28 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.
ClassTooLong: Cavena890 src/libse/SubtitleFormats/Cavena890.cs:0— ClassTooLong — 1322 significant lines (blank, comment-only and punctuation-only lines excluded), 13 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.
ClassTooLong: LanguageAutoDetect src/libse/Common/LanguageAutoDetect.cs:0— ClassTooLong — 1273 significant lines (blank, comment-only and punctuation-only lines excluded), 19 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.
ClassTooLong: InitListViewAndEditBox src/ui/Features/Main/Layout/InitListViewAndEditBox.cs:0— ClassTooLong — 1140 significant lines (blank, comment-only and punctuation-only lines excluded), 8 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.
ClassTooLong: HtmlUtil src/libse/Common/HtmlUtil.cs:0— ClassTooLong — 947 significant lines (blank, comment-only and punctuation-only lines excluded), 26 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.
ClassTooLong: TimedText10 src/libse/SubtitleFormats/TimedText10.cs:0— ClassTooLong — 900 significant lines (blank, comment-only and punctuation-only lines excluded), 27 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.
ClassTooLong: ScenaristClosedCaptions src/libse/SubtitleFormats/ScenaristClosedCaptions.cs:0— ClassTooLong — 878 significant lines (blank, comment-only and punctuation-only lines excluded), 23 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.
ClassTooLong: ShortcutsMain src/ui/Logic/ShortcutsMain.cs:0— ClassTooLong — 865 significant lines (blank, comment-only and punctuation-only lines excluded), 9 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.
ClassTooLong: RemoveTextForHI src/libse/Forms/RemoveTextForHI.cs:0— ClassTooLong — 837 significant lines (blank, comment-only and punctuation-only lines excluded), 22 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.
ClassTooLong: SeJsonParser src/libse/Common/SeJsonParser.cs:0— ClassTooLong — 834 significant lines (blank, comment-only and punctuation-only lines excluded), 5 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.
ClassTooLong: SettingsPage src/ui/Features/Options/Settings/SettingsPage.cs:0— ClassTooLong — 802 significant lines (blank, comment-only and punctuation-only lines excluded), 24 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.
ClassTooLong: OcrWindow src/ui/Features/Ocr/OcrWindow.cs:0— ClassTooLong — 758 significant lines (blank, comment-only and punctuation-only lines excluded), 12 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.
ClassTooLong: Ebu src/libse/SubtitleFormats/Ebu.cs:0— ClassTooLong — 740 significant lines (blank, comment-only and punctuation-only lines excluded), 17 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.
ClassTooLong: BinaryEditWindow src/ui/Features/Shared/BinaryEdit/BinaryEditWindow.cs:0— ClassTooLong — 734 significant lines (blank, comment-only and punctuation-only lines excluded), 8 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.
ClassTooLong: InitWaveform src/ui/Features/Main/Layout/InitWaveform.cs:0— ClassTooLong — 687 significant lines (blank, comment-only and punctuation-only lines excluded), 4 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.
ClassTooLong: InitMenu src/ui/Features/Main/Layout/InitMenu.cs:0— ClassTooLong — 661 significant lines (blank, comment-only and punctuation-only lines excluded), 6 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.
ClassTooLong: SccPositionAndStyleTable src/libse/Common/SccPositionAndStyleTable.cs:0— ClassTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded), 0 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.
ClassTooLong: SpeechToTextWindow src/ui/Features/Video/SpeechToText/SpeechToTextWindow.cs:0— ClassTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded), 10 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.
ClassTooLong: BurnInWindow src/ui/Features/Video/BurnIn/BurnInWindow.cs:0— ClassTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded), 13 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.
ClassTooLong: WebVTT src/libse/SubtitleFormats/WebVTT.cs:0— ClassTooLong — 629 significant lines (blank, comment-only and punctuation-only lines excluded), 26 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.
ClassTooLong: RosettaPropertiesViewModel src/ui/Features/Files/FormatProperties/RosettaProperties/RosettaPropertiesViewModel.cs:0— ClassTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded), 11 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.
ClassTooLong: DCinemaInterop src/libse/SubtitleFormats/DCinemaInterop.cs:0— ClassTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded), 11 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.
ClassTooLong: UnknownFormatImporter src/libse/Common/UnknownFormatImporter.cs:0— ClassTooLong — 603 significant lines (blank, comment-only and punctuation-only lines excluded), 15 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.
ClassTooLong: OcrFixReplaceList2 src/libuilogic/Ocr/FixEngine/OcrFixReplaceList2.cs:0— ClassTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded), 26 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.
TodoComment src/libse/Cea708/Cea708.cs:574— //TODO: ??? — 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 src/libse/Cea708/VancDataWriter.cs:46— //TODO: improve italic support — 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 src/libse/ContainerFormats/Mp4/Boxes/Mdia.cs:64— // TODO: How to find 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 src/libse/ContainerFormats/Mp4/Boxes/Stbl.cs:313— //TODO: cea 608 or 708 cc? What is the content? — 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 src/libse/ContainerFormats/Mp4/Mp4Parser.cs:764— //TODO: can there be more than one? — 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 src/libse/ContainerFormats/TransportStream/DvbSubPes.cs:408— // TODO: Return default clut — 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 src/libse/ContainerFormats/TransportStream/Teletext.cs:647— // TODO: — 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 src/libse/ContainerFormats/TransportStream/Teletext.cs:674— // TODO: — 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 src/libse/ContainerFormats/TransportStream/TeletextHamming.cs:72— //TODO: Cast exception??? — 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 src/libse/Forms/FixCommonErrors/AddMissingQuotes.cs:28— //TODO: extract to own rule — 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 src/libse/SubtitleFormats/AdvancedSubStationAlpha.cs:1983— // TODO: Alignment tags — 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 src/libse/SubtitleFormats/Ebu.cs:481— //TODO: Use bytes directly and not encoding — 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 src/libse/SubtitleFormats/Ebu.cs:775— //TODO: Use bytes directly and not encoding — 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 src/libse/SubtitleFormats/Ebu.cs:561— //TODO: we use new byte list - remove old code — 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 src/libse/SubtitleFormats/Idx.cs:10— // TODO: Working on added edit capabilities for idx files... — 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 src/libse/SubtitleFormats/IssXml.cs:61— // TODO: Set variables... — 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 src/libse/SubtitleFormats/Pac.cs:1519— // These bytes seems to be PAC files... TODO: Verify! — 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 src/libse/SubtitleFormats/SpruceWithSpace.cs:176— // TODO: Improve end tags — 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 src/libse/SubtitleFormats/SwiftInterchange2.cs:46— //TODO: Frame rate — 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 src/libse/SubtitleFormats/TextST.cs:18— //TODO: check max — 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 src/libse/SubtitleFormats/TextST.cs:40— //TODO: check max — 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 src/libse/SubtitleFormats/TextST.cs:47— //TODO: check max — 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 src/libse/SubtitleFormats/TextST.cs:60— //TODO: check max — 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 src/libse/SubtitleFormats/TextST.cs:1146— //TODO: merge ts packets — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/libse/SubtitleFormats/TimelineMvt.cs:132— //TODO: figure out how to get time code from these 7 bytes! — 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.
TooManyMethods: MainViewModel src/ui/Features/Main/MainViewModel.cs:0— TooManyMethods — 12399 significant lines (blank, comment-only and punctuation-only lines excluded), 820 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: OcrViewModel src/ui/Features/Ocr/OcrViewModel.cs:0— TooManyMethods — 2945 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: BinaryEditViewModel src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:0— TooManyMethods — 1518 significant lines (blank, comment-only and punctuation-only lines excluded), 132 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: SpeechToTextViewModel src/ui/Features/Video/SpeechToText/SpeechToTextViewModel.cs:0— TooManyMethods — 2581 significant lines (blank, comment-only and punctuation-only lines excluded), 99 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: Utilities src/libse/Common/Utilities.cs:0— TooManyMethods — 2012 significant lines (blank, comment-only and punctuation-only lines excluded), 94 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: SettingsViewModel src/ui/Features/Options/Settings/SettingsViewModel.cs:0— TooManyMethods — 1791 significant lines (blank, comment-only and punctuation-only lines excluded), 90 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: TextToSpeechViewModel src/ui/Features/Video/TextToSpeech/TextToSpeechViewModel.cs:0— TooManyMethods — 1872 significant lines (blank, comment-only and punctuation-only lines excluded), 82 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: AudioVisualizer src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:0— TooManyMethods — 1908 significant lines (blank, comment-only and punctuation-only lines excluded), 79 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: SyntaxTextView src/ui/Controls/SyntaxTextEditorControl/SyntaxTextView.cs:0— TooManyMethods — 945 significant lines (blank, comment-only and punctuation-only lines excluded), 79 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: BurnInViewModel src/ui/Features/Video/BurnIn/BurnInViewModel.cs:0— TooManyMethods — 1306 significant lines (blank, comment-only and punctuation-only lines excluded), 72 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: AssaStylesViewModel src/ui/Features/Assa/AssaStylesViewModel.cs:0— TooManyMethods — 796 significant lines (blank, comment-only and punctuation-only lines excluded), 71 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: BatchConvertViewModel src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:0— TooManyMethods — 1509 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NikseBitmap src/libse/Common/NikseBitmap.cs:0— TooManyMethods — 904 significant lines (blank, comment-only and punctuation-only lines excluded), 67 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: BatchConverter src/ui/Features/Tools/BatchConvert/BatchConverter.cs:0— TooManyMethods — 1524 significant lines (blank, comment-only and punctuation-only lines excluded), 65 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: ReviewSpeechViewModel src/ui/Features/Video/TextToSpeech/ReviewSpeech/ReviewSpeechViewModel.cs:0— TooManyMethods — 967 significant lines (blank, comment-only and punctuation-only lines excluded), 57 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: FixCommonErrorsViewModel src/ui/Features/Tools/FixCommonErrors/FixCommonErrorsViewModel.cs:0— TooManyMethods — 560 significant lines (blank, comment-only and punctuation-only lines excluded), 57 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: AutoTranslateViewModel src/ui/Features/Translate/AutoTranslateViewModel.cs:0— TooManyMethods — 1342 significant lines (blank, comment-only and punctuation-only lines excluded), 56 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: SsaStylesViewModel src/ui/Features/Ssa/SsaStylesViewModel.cs:0— TooManyMethods — 615 significant lines (blank, comment-only and punctuation-only lines excluded), 56 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: TransparentSubtitlesViewModel src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:0— TooManyMethods — 817 significant lines (blank, comment-only and punctuation-only lines excluded), 53 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: LibMpvDynamicPlayer src/ui/Logic/VideoPlayers/LibMpvDynamic/LibMpvDynamicPlayer.cs:0— TooManyMethods — 849 significant lines (blank, comment-only and punctuation-only lines excluded), 50 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: CutVideoViewModel src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:0— TooManyMethods — 748 significant lines (blank, comment-only and punctuation-only lines excluded), 49 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: ContinuationUtilities src/libse/Common/ContinuationUtilities.cs:0— TooManyMethods — 724 significant lines (blank, comment-only and punctuation-only lines excluded), 49 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: MultipleReplaceViewModel src/ui/Features/Edit/MultipleReplace/MultipleReplaceViewModel.cs:0— TooManyMethods — 708 significant lines (blank, comment-only and punctuation-only lines excluded), 49 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: Qwen3TtsCrispAsr src/ui/Features/Video/TextToSpeech/Engines/Qwen3TtsCrispAsr.cs:0— TooManyMethods — 537 significant lines (blank, comment-only and punctuation-only lines excluded), 49 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: AssaDrawViewModel src/ui/Features/Assa/AssaDraw/AssaDrawViewModel.cs:0— TooManyMethods — 736 significant lines (blank, comment-only and punctuation-only lines excluded), 48 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.
Dead code: GetSpectrogram src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:3438— Method GetSpectrogram — no references found in solution.
Dead code: RemoveAfterParenthesisAndTrim src/ui/Features/Files/ExportEbuStl/ExportEbuStlViewModel.cs:503— Method RemoveAfterParenthesisAndTrim — no references found in solution.
Dead code: SubtitleTextOriginalChanged src/ui/Features/Main/MainViewModel.cs:23247— Method SubtitleTextOriginalChanged — no references found in solution.
Dead code: AudioVisualizerOnStatus src/ui/Features/Main/MainViewModel.cs:23556— Method AudioVisualizerOnStatus — no references found in solution.
Dead code: OnWaveformDoubleTapped src/ui/Features/Main/MainViewModel.cs:24558— Method OnWaveformDoubleTapped — no references found in solution.
Dead code: MakeTransparentBlack src/ui/Features/Ocr/Engines/PaddleOcr.cs:160— Method MakeTransparentBlack — no references found in solution.
Dead code: OutputHandler src/ui/Features/Ocr/Engines/PaddleOcr.cs:1002— Method OutputHandler — no references found in solution.
Dead code: DrawModeChanged src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:638— Method DrawModeChanged — no references found in solution.
Dead code: TextBoxDatabaseNameKeyDown src/ui/Features/Ocr/NOcr/NOcrDbEditViewModel.cs:212— Method TextBoxDatabaseNameKeyDown — no references found in solution.
Dead code: DrawModeChanged src/ui/Features/Ocr/NOcr/NOcrDbEditViewModel.cs:297— Method DrawModeChanged — no references found in solution.
Dead code: ApplyCustomColors src/ui/Features/Ocr/OcrSubtitle/OcrSubtitleBdn.cs:241— Method ApplyCustomColors — no references found in solution.
Dead code: DataGridTracksSelectionChanged src/ui/Features/Ocr/OcrViewModel.cs:4545— Method DataGridTracksSelectionChanged — no references found in solution.
Dead code: SplitImageToLines src/ui/Features/Ocr/OcrViewModel.cs:5342— Method SplitImageToLines — no references found in solution.
Dead code: GetTranslationModifierFromSetting src/ui/Features/Options/Settings/SettingsViewModel.cs:1131— Method GetTranslationModifierFromSetting — no references found in solution.
Dead code: ValueChanged src/ui/Features/Tools/SortBy/SortByViewModel.cs:411— Method ValueChanged — no references found in solution.
Dead code: SplitHelper src/ui/Features/Translate/SplitHelper.cs:7— NamedType SplitHelper — no references found in solution.
Dead code: TextBoxChanged src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1984— Method TextBoxChanged — no references found in solution.
Dead code: OutputHandlerKeyFrames src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditViewModel.cs:110— Method OutputHandlerKeyFrames — no references found in solution.
Dead code: TextBoxChanged src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1467— Method TextBoxChanged — no references found in solution.
Dead code: RegisterClipboardFormatW src/ui/Logic/ClipboardHelper.cs:27— Method RegisterClipboardFormatW — no references found in solution.
Dead code: CreateCompatibleDC src/ui/Logic/ClipboardHelper.cs:42— Method CreateCompatibleDC — no references found in solution.
Dead code: CreateDIBSection src/ui/Logic/ClipboardHelper.cs:45— Method CreateDIBSection — no references found in solution.
Dead code: SelectObject src/ui/Logic/ClipboardHelper.cs:48— Method SelectObject — no references found in solution.
Dead code: DeleteDC src/ui/Logic/ClipboardHelper.cs:54— Method DeleteDC — no references found in solution.
Dead code: GetDC src/ui/Logic/ClipboardHelper.cs:57— Method GetDC — no references found in solution.
Duplicated block (14 lines × 2) src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:1538— src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:1538-1551 | src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:1557-1570 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:1538` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ui/Features/Assa/AssaAttachmentItem.cs:28— src/ui/Features/Assa/AssaAttachmentItem.cs:28-41 | src/ui/Features/Ssa/SsaAttachmentItem.cs:28-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaAttachmentItem.cs:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ui/Features/Assa/AssaStylesViewModel.cs:308— src/ui/Features/Assa/AssaStylesViewModel.cs:308-321 | src/ui/Features/Ssa/SsaStylesViewModel.cs:196-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:308` 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) src/ui/Features/Assa/AssaStylesViewModel.cs:347— src/ui/Features/Assa/AssaStylesViewModel.cs:347-360 | src/ui/Features/Ssa/SsaStylesViewModel.cs:235-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:347` 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) src/ui/Features/Assa/AssaStylesViewModel.cs:429— src/ui/Features/Assa/AssaStylesViewModel.cs:429-442 | src/ui/Features/Ssa/SsaStylesViewModel.cs:317-330 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:429` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ui/Features/Assa/AssaStylesViewModel.cs:742— src/ui/Features/Assa/AssaStylesViewModel.cs:742-755 | src/ui/Features/Ssa/SsaStylesViewModel.cs:560-573 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:742` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ui/Features/Edit/Find/FindViewModel.cs:131— src/ui/Features/Edit/Find/FindViewModel.cs:131-144 | src/ui/Features/Edit/Replace/ReplaceViewModel.cs:144-157 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Edit/Find/FindViewModel.cs:131` 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) src/ui/Features/Files/FormatProperties/RosettaProperties/RosettaPropertiesViewModel.cs:587— src/ui/Features/Files/FormatProperties/RosettaProperties/RosettaPropertiesViewModel.cs:587-600 | src/ui/Features/Files/FormatProperties/WebVttProperties/WebVttPropertiesViewModel.cs:91-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) src/ui/Features/Main/MainViewModel.cs:1378— src/ui/Features/Main/MainViewModel.cs:1378-1391 | src/ui/Features/Main/MainViewModel.cs:1439-1452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:1378` 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) src/ui/Features/Main/MainViewModel.cs:3516— src/ui/Features/Main/MainViewModel.cs:3516-3529 | src/ui/Features/Main/MainViewModel.cs:3577-3590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/ui/Features/Main/MainViewModel.cs:14534— src/ui/Features/Main/MainViewModel.cs:14534-14547 | src/ui/Features/Main/MainViewModel.cs:14557-14570 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:14534` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ui/Features/Main/MainViewModel.cs:14882— src/ui/Features/Main/MainViewModel.cs:14882-14895 | src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:605-618 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) src/ui/Features/Main/MainViewModel.cs:14907— src/ui/Features/Main/MainViewModel.cs:14907-14920 | src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:625-638 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) src/ui/Features/Main/MainViewModel.cs:16138— src/ui/Features/Main/MainViewModel.cs:16138-16151 | src/ui/Features/Main/MainViewModel.cs:16186-16199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:16138` 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) src/ui/Features/Main/MainViewModel.cs:18861— src/ui/Features/Main/MainViewModel.cs:18861-18874 | src/ui/Features/Main/MainViewModel.cs:18882-18895 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:18861` 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) src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:154— src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:154-167 | src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:198-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:154` 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) src/ui/Features/Ocr/OcrViewModel.cs:4132— src/ui/Features/Ocr/OcrViewModel.cs:4132-4145 | src/ui/Features/Ocr/OcrViewModel.cs:4207-4220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) src/ui/Features/Shared/BinaryEdit/BinaryAdjustAllTimes/BinaryAdjustAllTimesViewModel.cs:49— src/ui/Features/Shared/BinaryEdit/BinaryAdjustAllTimes/BinaryAdjustAllTimesViewModel.cs:49-62 | src/ui/Features/Sync/AdjustAllTimes/AdjustAllTimesViewModel.cs:74-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Shared/BinaryEdit/BinaryAdjustAllTimes/BinaryAdjustAllTimesViewModel.cs:49` 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) src/ui/Features/Sync/ChangeFrameRate/ChangeFrameRateViewModel.cs:88— src/ui/Features/Sync/ChangeFrameRate/ChangeFrameRateViewModel.cs:88-101 | src/ui/Features/Sync/ChangeFrameRate/ChangeFrameRateViewModel.cs:114-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/ui/Features/Tools/BatchConvert/BatchConverter.cs:749— src/ui/Features/Tools/BatchConvert/BatchConverter.cs:749-762 | src/ui/Features/Tools/BatchConvert/BatchConverter.cs:943-956 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/BatchConvert/BatchConverter.cs:749` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2577— src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2577-2590 | src/ui/Features/Translate/AutoTranslateViewModel.cs:636-649 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2577` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1018— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1018-1031 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:761-774 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1018` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1877— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1877-1890 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1156-1169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1877` 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) src/ui/Features/Video/SpeechToText/Engines/WhisperEngineCppCuBlas.cs:62— src/ui/Features/Video/SpeechToText/Engines/WhisperEngineCppCuBlas.cs:62-75 | src/ui/Features/Video/SpeechToText/Engines/WhisperEngineCppVulkan.cs:66-79 — 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 `src/ui/Features/Video/SpeechToText/Engines/WhisperEngineCppCuBlas.cs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/ui/Features/Video/SpeechToText/EngineSettings/SpeechToTextEngineSettingsViewModel.cs:238— src/ui/Features/Video/SpeechToText/EngineSettings/SpeechToTextEngineSettingsViewModel.cs:238-251 | src/ui/Features/Video/SpeechToText/SpeechToTextViewModel.cs:4743-4758 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/SpeechToText/EngineSettings/SpeechToTextEngineSettingsViewModel.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 (13 lines × 2) src/ui/Features/Assa/AssaPropertiesViewModel.cs:52— src/ui/Features/Assa/AssaPropertiesViewModel.cs:52-64 | src/ui/Features/Ssa/SsaPropertiesViewModel.cs:51-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaPropertiesViewModel.cs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ui/Features/Assa/AssaPropertiesViewModel.cs:280— src/ui/Features/Assa/AssaPropertiesViewModel.cs:280-292 | src/ui/Features/Ssa/SsaPropertiesViewModel.cs:268-280 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaPropertiesViewModel.cs:280` 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) src/ui/Features/Assa/AssaStylesViewModel.cs:91— src/ui/Features/Assa/AssaStylesViewModel.cs:91-103 | src/ui/Features/Ssa/SsaStylesViewModel.cs:75-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) src/ui/Features/Assa/AssaStylesViewModel.cs:327— src/ui/Features/Assa/AssaStylesViewModel.cs:327-339 | src/ui/Features/Ssa/SsaStylesViewModel.cs:215-227 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) src/ui/Features/Assa/AssaStylesViewModel.cs:485— src/ui/Features/Assa/AssaStylesViewModel.cs:485-497 | src/ui/Features/Ssa/SsaStylesViewModel.cs:375-387 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:485` 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) src/ui/Features/Assa/AssaStylesViewModel.cs:619— src/ui/Features/Assa/AssaStylesViewModel.cs:619-631 | src/ui/Features/Ssa/SsaStylesViewModel.cs:437-449 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) src/ui/Features/Assa/AssaStylesViewModel.cs:1231— src/ui/Features/Assa/AssaStylesViewModel.cs:1231-1243 | src/ui/Features/Ssa/SsaStylesViewModel.cs:848-860 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:1231` 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) src/ui/Features/Files/FormatProperties/TimedText10Properties/TimedText10PropertiesViewModel.cs:146— src/ui/Features/Files/FormatProperties/TimedText10Properties/TimedText10PropertiesViewModel.cs:146-158 | src/ui/Features/Files/FormatProperties/TimedTextImsc11Properties/TimedTextImsc11PropertiesViewModel.cs:118-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Files/FormatProperties/TimedText10Properties/TimedText10PropertiesViewModel.cs:146` 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) src/ui/Features/Files/Statistics/StatisticsViewModel.cs:803— src/ui/Features/Files/Statistics/StatisticsViewModel.cs:803-815 | src/ui/Features/Files/Statistics/StatisticsViewModel.cs:847-859 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Files/Statistics/StatisticsViewModel.cs:803` 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) src/ui/Features/Main/Layout/InitLayout.cs:91— src/ui/Features/Main/Layout/InitLayout.cs:91-103 | src/ui/Features/Main/Layout/InitLayout.cs:138-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/Layout/InitLayout.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ui/Features/Main/Layout/InitLayout.cs:112— src/ui/Features/Main/Layout/InitLayout.cs:112-124 | src/ui/Features/Main/Layout/InitLayout.cs:159-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/Layout/InitLayout.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ui/Features/Main/MainViewModel.cs:7791— src/ui/Features/Main/MainViewModel.cs:7791-7803 | src/ui/Features/Main/MainViewModel.cs:7938-7950 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/ui/Features/Main/MainViewModel.cs:8936— src/ui/Features/Main/MainViewModel.cs:8936-8948 | src/ui/Features/Main/MainViewModel.cs:9071-9083 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:8936` 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) src/ui/Features/Main/MainViewModel.cs:9528— src/ui/Features/Main/MainViewModel.cs:9528-9540 | src/ui/Features/Main/MainViewModel.cs:13076-13088 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:9528` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ui/Features/Main/MainViewModel.cs:13813— src/ui/Features/Main/MainViewModel.cs:13813-13825 | src/ui/Features/Main/MainViewModel.cs:13854-13866 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:13813` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ui/Features/Ocr/BinaryOcr/BinaryOcrDbEditViewModel.cs:233— src/ui/Features/Ocr/BinaryOcr/BinaryOcrDbEditViewModel.cs:233-245 | src/ui/Features/Ocr/NOcr/NOcrDbEditViewModel.cs:270-282 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) src/ui/Features/Shared/BinaryEdit/BinaryEditWindow.cs:569— src/ui/Features/Shared/BinaryEdit/BinaryEditWindow.cs:569-581 | src/ui/Features/Shared/BinaryEdit/BinaryEditWindow.cs:642-654 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/ui/Features/Shared/PickSpellCheckDictionary/PickSpellCheckDictionaryViewModel.cs:87— src/ui/Features/Shared/PickSpellCheckDictionary/PickSpellCheckDictionaryViewModel.cs:87-99 | src/ui/Features/SpellCheck/SpellCheckViewModel.cs:257-269 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Shared/PickSpellCheckDictionary/PickSpellCheckDictionaryViewModel.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.
Duplicated block (13 lines × 2) src/ui/Features/Ssa/SsaStylesViewModel.cs:324— src/ui/Features/Ssa/SsaStylesViewModel.cs:324-336 | src/ui/Features/Ssa/SsaStylesViewModel.cs:567-579 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/ui/Features/Sync/PointSync/SetSyncPoint/SetSyncPointViewModel.cs:275— src/ui/Features/Sync/PointSync/SetSyncPoint/SetSyncPointViewModel.cs:275-287 | src/ui/Features/Sync/VisualSync/VisualSyncViewModel.cs:302-314 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Sync/PointSync/SetSyncPoint/SetSyncPointViewModel.cs:275` 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) src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2622— src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2622-2634 | src/ui/Features/Translate/AutoTranslateViewModel.cs:691-703 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2622` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/ui/Features/Translate/AutoTranslateViewModel.cs:977— src/ui/Features/Translate/AutoTranslateViewModel.cs:977-989 | src/ui/Features/Video/VideoOcr/VideoOcrViewModel.cs:249-261 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Translate/AutoTranslateViewModel.cs:977` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1467— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1467-1479 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1060-1072 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1467` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ui/Features/Video/ReEncodeVideo/ReEncodeVideoViewModel.cs:221— src/ui/Features/Video/ReEncodeVideo/ReEncodeVideoViewModel.cs:221-233 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:370-382 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/ReEncodeVideo/ReEncodeVideoViewModel.cs:221` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/ui/Features/Video/SpeechToText/SpeechToTextTimingFixer.cs:61— src/ui/Features/Video/SpeechToText/SpeechToTextTimingFixer.cs:61-73 | src/ui/Features/Video/SpeechToText/SpeechToTextTimingFixer.cs:124-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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:2093— src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:2093-2104 | src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:2272-2294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Controls/AudioVisualizerControl/AudioVisualizer.cs:2093` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/ui/Features/Assa/AssaApplyAdvancedEffect/Effects/AdvancedEffectSlowZoomIn.cs:21— src/ui/Features/Assa/AssaApplyAdvancedEffect/Effects/AdvancedEffectSlowZoomIn.cs:21-32 | src/ui/Features/Assa/AssaApplyAdvancedEffect/Effects/AdvancedEffectSlowZoomOut.cs:21-32 — 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 `src/ui/Features/Assa/AssaApplyAdvancedEffect/Effects/AdvancedEffectSlowZoomIn.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.
Duplicated block (12 lines × 2) src/ui/Features/Assa/AssaStylesViewModel.cs:393— src/ui/Features/Assa/AssaStylesViewModel.cs:393-404 | src/ui/Features/Ssa/SsaStylesViewModel.cs:281-292 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:393` 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) src/ui/Features/Assa/AssaStylesViewModel.cs:708— src/ui/Features/Assa/AssaStylesViewModel.cs:708-719 | src/ui/Features/Ssa/SsaStylesViewModel.cs:526-537 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:708` 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) src/ui/Features/Files/ExportEbuStl/ExportEbuStlWindow.cs:298— src/ui/Features/Files/ExportEbuStl/ExportEbuStlWindow.cs:298-309 | src/ui/Features/Files/ExportEbuStl/ExportEbuStlWindow.cs:310-321 — both copies are in the same file, so extract the block into 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) src/ui/Features/Main/Layout/LayoutWindow.cs:140— src/ui/Features/Main/Layout/LayoutWindow.cs:140-152 | src/ui/Features/Main/Layout/LayoutWindow.cs:161-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/Layout/LayoutWindow.cs:140` 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 (12 lines × 2) src/ui/Features/Main/MainViewModel.cs:1130— src/ui/Features/Main/MainViewModel.cs:1130-1141 | src/ui/Features/Main/MainViewModel.cs:1206-1217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:1130` 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) src/ui/Features/Main/MainViewModel.cs:11614— src/ui/Features/Main/MainViewModel.cs:11614-11625 | src/ui/Features/Main/MainViewModel.cs:11660-11671 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:11614` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/ui/Features/Main/MainViewModel.cs:16893— src/ui/Features/Main/MainViewModel.cs:16893-16904 | src/ui/Features/Main/MainViewModel.cs:16914-16925 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:16893` 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) src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:200— src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:200-211 | src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:249-260 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:200` 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) src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:314— src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:314-325 | src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:485-496 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:314` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/ui/Features/Ocr/BinaryOcr/BinaryOcrInspectViewModel.cs:77— src/ui/Features/Ocr/BinaryOcr/BinaryOcrInspectViewModel.cs:77-88 | src/ui/Features/Ocr/NOcr/NOcrInspectViewModel.cs:86-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) src/ui/Features/Ocr/Download/DownloadCrispEmbedViewModel.cs:247— src/ui/Features/Ocr/Download/DownloadCrispEmbedViewModel.cs:247-258 | src/ui/Features/Video/SpeechToText/DownloadSpeechToTextEngineViewModel.cs:338-349 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/Download/DownloadCrispEmbedViewModel.cs:247` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:951— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:951-962 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:727-738 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:951` 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 (12 lines × 2) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1172— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1172-1183 | src/ui/Features/Video/ReEncodeVideo/ReEncodeVideoViewModel.cs:378-389 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1172` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:274— src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:274-285 | src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditViewModel.cs:111-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:274` 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) src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:578— src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:578-589 | src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditViewModel.cs:279-290 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:578` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) src/ui/Features/Video/SpeechToText/SpeechToTextPostProcessingWindow.cs:83— src/ui/Features/Video/SpeechToText/SpeechToTextPostProcessingWindow.cs:83-94 | src/ui/Features/Video/SpeechToText/SpeechToTextPostProcessingWindow.cs:95-106 — both copies are in the same file, so extract the block into 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) src/ui/Features/Video/SpeechToText/SpeechToTextTimingFixer.cs:79— src/ui/Features/Video/SpeechToText/SpeechToTextTimingFixer.cs:79-90 | src/ui/Features/Video/SpeechToText/SpeechToTextTimingFixer.cs:128-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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) src/ui/Features/Video/SpeechToText/SpeechToTextWindow.cs:452— src/ui/Features/Video/SpeechToText/SpeechToTextWindow.cs:452-463 | src/ui/Features/Video/SpeechToText/SpeechToTextWindow.cs:464-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.
Duplicated block (12 lines × 2) src/ui/Features/Video/TextToSpeech/Engines/AzureSpeech.cs:63— src/ui/Features/Video/TextToSpeech/Engines/AzureSpeech.cs:63-74 | src/ui/Features/Video/TextToSpeech/Engines/Murf.cs:74-85 — 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 `src/ui/Features/Video/TextToSpeech/Engines/AzureSpeech.cs:63` 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) src/ui/Features/Video/TextToSpeech/Engines/ElevenLabs.cs:61— src/ui/Features/Video/TextToSpeech/Engines/ElevenLabs.cs:61-72 | src/ui/Features/Video/TextToSpeech/Engines/GoogleSpeech.cs:65-76 — 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 `src/ui/Features/Video/TextToSpeech/Engines/ElevenLabs.cs:61` 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) src/ui/Features/Video/TextToSpeech/OmniVoiceSettings/OmniVoiceSettingsViewModel.cs:124— src/ui/Features/Video/TextToSpeech/OmniVoiceSettings/OmniVoiceSettingsViewModel.cs:124-135 | src/ui/Features/Video/TextToSpeech/Qwen3TtsSettings/Qwen3TtsSettingsViewModel.cs:124-135 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/TextToSpeech/OmniVoiceSettings/OmniVoiceSettingsViewModel.cs:124` 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) src/ui/Features/Video/TextToSpeech/TextToSpeechViewModel.cs:750— src/ui/Features/Video/TextToSpeech/TextToSpeechViewModel.cs:750-761 | src/ui/Features/Video/TextToSpeech/VoiceSettings/VoiceSettingsViewModel.cs:394-405 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/TextToSpeech/TextToSpeechViewModel.cs:750` 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) src/ui/Features/Assa/AssaAttachmentsViewModel.cs:151— src/ui/Features/Assa/AssaAttachmentsViewModel.cs:151-160 | src/ui/Features/Ssa/SsaAttachmentsViewModel.cs:119-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaAttachmentsViewModel.cs:151` 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) src/ui/Features/Assa/AssaAttachmentsViewModel.cs:361— src/ui/Features/Assa/AssaAttachmentsViewModel.cs:361-370 | src/ui/Features/Ssa/SsaAttachmentsViewModel.cs:329-338 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaAttachmentsViewModel.cs:361` 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) src/ui/Features/Assa/AssaProgressBar/AssaProgressBarWindow.cs:189— src/ui/Features/Assa/AssaProgressBar/AssaProgressBarWindow.cs:189-199 | src/ui/Features/Assa/AssaProgressBar/AssaProgressBarWindow.cs:200-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 `src/ui/Features/Assa/AssaProgressBar/AssaProgressBarWindow.cs:189` 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) src/ui/Features/Assa/AssaPropertiesViewModel.cs:229— src/ui/Features/Assa/AssaPropertiesViewModel.cs:229-238 | src/ui/Features/Ssa/SsaPropertiesViewModel.cs:217-226 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) src/ui/Features/Files/ExportImageBased/ExportImageBasedWindow.cs:321— src/ui/Features/Files/ExportImageBased/ExportImageBasedWindow.cs:321-330 | src/ui/Features/Files/ExportImageBased/ExportImageBasedWindow.cs:331-340 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/ui/Features/Main/MainViewModel.cs:3297— src/ui/Features/Main/MainViewModel.cs:3297-3306 | src/ui/Features/Main/MainViewModel.cs:3317-3326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:3297` 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) src/ui/Features/Main/MainViewModel.cs:10589— src/ui/Features/Main/MainViewModel.cs:10589-10598 | src/ui/Features/Main/MainViewModel.cs:10641-10650 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:10589` 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) src/ui/Features/Main/MainViewModel.cs:19874— src/ui/Features/Main/MainViewModel.cs:19874-19883 | src/ui/Features/Main/MainViewModel.cs:19911-19920 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:19874` 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) src/ui/Features/Main/MainViewModel.cs:20400— src/ui/Features/Main/MainViewModel.cs:20400-20409 | src/ui/Features/Ocr/OcrViewModel.cs:1818-1827 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:20400` 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) src/ui/Features/Main/MainViewModel.cs:20459— src/ui/Features/Main/MainViewModel.cs:20459-20468 | src/ui/Features/Ocr/OcrViewModel.cs:2122-2131 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:20459` 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) src/ui/Features/Main/MainViewModel.cs:24535— src/ui/Features/Main/MainViewModel.cs:24535-24544 | src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2714-2725 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:24535` 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) src/ui/Features/Ocr/Download/DownloadGoogleLensOcrViewModel.cs:148— src/ui/Features/Ocr/Download/DownloadGoogleLensOcrViewModel.cs:148-157 | src/ui/Features/Ocr/Download/DownloadPaddleOcrViewModel.cs:261-270 — 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 `src/ui/Features/Ocr/Download/DownloadGoogleLensOcrViewModel.cs:148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/ui/Features/Ocr/Engines/LlamaCppOcr.cs:110— src/ui/Features/Ocr/Engines/LlamaCppOcr.cs:110-119 | src/ui/Features/Ocr/Engines/OllamaOcr.cs:163-172 — 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 `src/ui/Features/Ocr/Engines/LlamaCppOcr.cs:110` 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) src/ui/Features/Ocr/PreProcessingSettings.cs:125— src/ui/Features/Ocr/PreProcessingSettings.cs:125-135 | src/ui/Features/Ocr/PreProcessingSettings.cs:209-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/PreProcessingSettings.cs:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:550— src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:550-559 | src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:2309-2318 — both copies are in the same file, so extract the 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 (10 lines × 2) src/ui/Features/Tools/FixCommonErrors/FixCommonErrorsWindow.cs:197— src/ui/Features/Tools/FixCommonErrors/FixCommonErrorsWindow.cs:197-206 | src/ui/Features/Tools/FixCommonErrors/FixCommonErrorsWindow.cs:207-216 — both copies are in the same file, so extract the block into 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) src/ui/Features/Translate/TranslateSettingsWindow.cs:101— src/ui/Features/Translate/TranslateSettingsWindow.cs:101-110 | src/ui/Features/Translate/TranslateSettingsWindow.cs:116-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.
Duplicated block (10 lines × 2) src/ui/Features/Video/BlankVideo/BlankVideoViewModel.cs:310— src/ui/Features/Video/BlankVideo/BlankVideoViewModel.cs:310-319 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:610-619 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BlankVideo/BlankVideoViewModel.cs:310` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:847— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:847-856 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:657-666 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:847` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1851— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1851-1860 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1127-1139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1851` 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) src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditMp4ViewModel.cs:169— src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditMp4ViewModel.cs:169-178 | src/ui/Features/Video/ReEncodeVideo/ReEncodeVideoViewModel.cs:192-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditMp4ViewModel.cs:169` 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) src/ui/Features/Video/SpeechToText/SpeechToTextAdvancedWindow.cs:157— src/ui/Features/Video/SpeechToText/SpeechToTextAdvancedWindow.cs:157-166 | src/ui/Features/Video/SpeechToText/SpeechToTextAdvancedWindow.cs:172-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/ui/Features/Assa/AssaAttachmentsViewModel.cs:263— src/ui/Features/Assa/AssaAttachmentsViewModel.cs:263-278 | src/ui/Features/Ssa/SsaAttachmentsViewModel.cs:231-246 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaAttachmentsViewModel.cs:263` 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) src/ui/Features/Assa/AssaStylesViewModel.cs:1199— src/ui/Features/Assa/AssaStylesViewModel.cs:1199-1214 | src/ui/Features/Ssa/SsaStylesViewModel.cs:816-831 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:1199` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ui/Features/Assa/AssaStylesViewModel.cs:1358— src/ui/Features/Assa/AssaStylesViewModel.cs:1358-1373 | src/ui/Features/Ssa/SsaStylesViewModel.cs:975-990 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:1358` 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) src/ui/Features/Edit/Find/FindViewModel.cs:105— src/ui/Features/Edit/Find/FindViewModel.cs:105-120 | src/ui/Features/Edit/Replace/ReplaceViewModel.cs:112-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Edit/Find/FindViewModel.cs:105` 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) src/ui/Features/Files/FormatProperties/DcinemaInteropProperties/DCinemaInteropPropertiesViewModel.cs:139— src/ui/Features/Files/FormatProperties/DcinemaInteropProperties/DCinemaInteropPropertiesViewModel.cs:139-154 | src/ui/Features/Files/FormatProperties/DcinemaSmpteProperties/DCinemaSmptePropertiesViewModel.cs:209-225 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) src/ui/Features/Files/FormatProperties/DcinemaInteropProperties/DCinemaInteropPropertiesViewModel.cs:258— src/ui/Features/Files/FormatProperties/DcinemaInteropProperties/DCinemaInteropPropertiesViewModel.cs:258-273 | src/ui/Features/Files/FormatProperties/DcinemaSmpteProperties/DCinemaSmptePropertiesViewModel.cs:354-369 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) src/ui/Features/Main/MainViewModel.cs:3336— src/ui/Features/Main/MainViewModel.cs:3336-3351 | src/ui/Features/Main/MainViewModel.cs:3402-3417 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:3336` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ui/Features/Main/MainViewModel.cs:5034— src/ui/Features/Main/MainViewModel.cs:5034-5049 | src/ui/Features/Main/MainViewModel.cs:5094-5109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:5034` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) src/ui/Features/Main/MainViewModel.cs:8008— src/ui/Features/Main/MainViewModel.cs:8008-8023 | src/ui/Features/Main/MainViewModel.cs:8054-8069 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:8008` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ui/Features/Main/MainViewModel.cs:14478— src/ui/Features/Main/MainViewModel.cs:14478-14493 | src/ui/Features/Main/MainViewModel.cs:14506-14521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:14478` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ui/Features/Ocr/BinaryOcr/BinaryOcrInspectViewModel.cs:489— src/ui/Features/Ocr/BinaryOcr/BinaryOcrInspectViewModel.cs:489-504 | src/ui/Features/Ocr/NOcr/NOcrInspectViewModel.cs:639-654 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/BinaryOcr/BinaryOcrInspectViewModel.cs:489` 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) src/ui/Features/Ocr/Download/DownloadPaddleOcrViewModel.cs:172— src/ui/Features/Ocr/Download/DownloadPaddleOcrViewModel.cs:172-187 | src/ui/Features/Shared/DownloadLibVlcViewModel.cs:105-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/Download/DownloadPaddleOcrViewModel.cs:172` 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) src/ui/Features/Ocr/Engines/GoogleLensOcr.cs:116— src/ui/Features/Ocr/Engines/GoogleLensOcr.cs:116-131 | src/ui/Features/Ocr/Engines/GoogleLensOcr.cs:197-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 `src/ui/Features/Ocr/Engines/GoogleLensOcr.cs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ui/Features/Ocr/Engines/PaddleOcr.cs:1012— src/ui/Features/Ocr/Engines/PaddleOcr.cs:1012-1027 | src/ui/Features/Ocr/Engines/PaddleOcr.cs:1071-1086 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/Engines/PaddleOcr.cs:1012` 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) src/ui/Features/Ocr/OcrViewModel.cs:1430— src/ui/Features/Ocr/OcrViewModel.cs:1430-1445 | src/ui/Features/Video/VideoOcr/VideoOcrViewModel.cs:242-257 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/OcrViewModel.cs:1430` 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) src/ui/Features/Tools/BatchConvert/BatchConverter.cs:1288— src/ui/Features/Tools/BatchConvert/BatchConverter.cs:1288-1304 | src/ui/Features/Tools/BatchConvert/BatchConverter.cs:1346-1361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/BatchConvert/BatchConverter.cs:1288` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:2163— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:2163-2178 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1291-1306 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:2163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:551— src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:551-566 | src/ui/Features/Video/ReEncodeVideo/ReEncodeVideoViewModel.cs:349-364 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:551` 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) src/ui/Features/Video/SpeechToText/DownloadSpeechToTextEngineViewModel.cs:380— src/ui/Features/Video/SpeechToText/DownloadSpeechToTextEngineViewModel.cs:380-395 | src/ui/Features/Video/SpeechToText/DownloadSpeechToTextEngineViewModel.cs:402-417 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/SpeechToText/DownloadSpeechToTextEngineViewModel.cs:380` 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) src/ui/Features/Assa/AssaStylesViewModel.cs:452— src/ui/Features/Assa/AssaStylesViewModel.cs:452-462 | src/ui/Features/Ssa/SsaStylesViewModel.cs:342-352 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:452` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) src/ui/Features/Assa/AssaStylesViewModel.cs:765— src/ui/Features/Assa/AssaStylesViewModel.cs:765-775 | src/ui/Features/Ssa/SsaStylesViewModel.cs:585-595 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaStylesViewModel.cs:765` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) src/ui/Features/Edit/MultipleReplace/MultipleReplaceViewModel.cs:814— src/ui/Features/Edit/MultipleReplace/MultipleReplaceViewModel.cs:814-824 | src/ui/Features/Edit/MultipleReplace/MultipleReplaceViewModel.cs:836-846 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Edit/MultipleReplace/MultipleReplaceViewModel.cs:814` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ui/Features/Files/ExportEbuStl/ExportEbuStlWindow.cs:168— src/ui/Features/Files/ExportEbuStl/ExportEbuStlWindow.cs:168-178 | src/ui/Features/Files/ExportEbuStl/ExportEbuStlWindow.cs:200-210 — both copies are in the same file, so extract the block into 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) src/ui/Features/Files/FormatProperties/DcinemaSmpteProperties/DCinemaSmptePropertiesViewModel.cs:122— src/ui/Features/Files/FormatProperties/DcinemaSmpteProperties/DCinemaSmptePropertiesViewModel.cs:122-132 | src/ui/Features/Files/FormatProperties/DcinemaSmpteProperties/DCinemaSmptePropertiesViewModel.cs:161-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Files/FormatProperties/DcinemaSmpteProperties/DCinemaSmptePropertiesViewModel.cs:122` 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) src/ui/Features/Main/AiAssistant/AiAssistantViewModel.cs:231— src/ui/Features/Main/AiAssistant/AiAssistantViewModel.cs:231-241 | src/ui/Features/Tools/AiReview/AiReviewViewModel.cs:632-642 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) src/ui/Features/Main/Layout/InitMenu.cs:545— src/ui/Features/Main/Layout/InitMenu.cs:545-555 | src/ui/Features/Main/Layout/InitMenu.cs:957-969 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/Layout/InitMenu.cs:545` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) src/ui/Features/Main/MainViewModel.cs:4339— src/ui/Features/Main/MainViewModel.cs:4339-4349 | src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:1193-1203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:4339` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ui/Features/Main/MainViewModel.cs:8306— src/ui/Features/Main/MainViewModel.cs:8306-8316 | src/ui/Features/Main/MainViewModel.cs:8335-8345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:8306` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ui/Features/Main/MainViewModel.cs:9099— src/ui/Features/Main/MainViewModel.cs:9099-9109 | src/ui/Features/Main/MainViewModel.cs:9196-9206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:9099` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ui/Features/Main/MainViewModel.cs:9138— src/ui/Features/Main/MainViewModel.cs:9138-9149 | src/ui/Features/Main/MainViewModel.cs:9191-9201 — both copies are in the same file, so extract the block into 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) src/ui/Features/Main/MainViewModel.cs:9994— src/ui/Features/Main/MainViewModel.cs:9994-10004 | src/ui/Features/Main/MainViewModel.cs:10030-10040 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:9994` 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) src/ui/Features/Ocr/OcrViewModel.cs:1010— src/ui/Features/Ocr/OcrViewModel.cs:1010-1020 | src/ui/Features/Ocr/OcrViewModel.cs:1063-1073 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/ui/Features/Sync/PointSync/SetSyncPoint/SetSyncPointViewModel.cs:108— src/ui/Features/Sync/PointSync/SetSyncPoint/SetSyncPointViewModel.cs:108-118 | src/ui/Features/Sync/VisualSync/VisualSyncViewModel.cs:139-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Sync/PointSync/SetSyncPoint/SetSyncPointViewModel.cs:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ui/Features/Tools/MergeSubtitlesWithSameText/MergeSameTextWindow.cs:143— src/ui/Features/Tools/MergeSubtitlesWithSameText/MergeSameTextWindow.cs:143-153 | src/ui/Features/Tools/MergeSubtitlesWithSameText/MergeSameTextWindow.cs:214-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/MergeSubtitlesWithSameText/MergeSameTextWindow.cs:143` 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) src/ui/Features/Tools/MergeSubtitlesWithSameTimeCodes/MergeSameTimeCodesWindow.cs:151— src/ui/Features/Tools/MergeSubtitlesWithSameTimeCodes/MergeSameTimeCodesWindow.cs:151-161 | src/ui/Features/Tools/MergeSubtitlesWithSameTimeCodes/MergeSameTimeCodesWindow.cs:222-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/MergeSubtitlesWithSameTimeCodes/MergeSameTimeCodesWindow.cs:151` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1199— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1199-1210 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:883-893 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1215— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1215-1226 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:898-908 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1215` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:2150— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:2150-2160 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1278-1288 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:2150` 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 (15 lines × 2) src/ui/Features/Assa/AssaAttachmentsViewModel.cs:174— src/ui/Features/Assa/AssaAttachmentsViewModel.cs:174-188 | src/ui/Features/Ssa/SsaAttachmentsViewModel.cs:142-156 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaAttachmentsViewModel.cs:174` 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) src/ui/Features/Assa/AssaAttachmentsViewModel.cs:419— src/ui/Features/Assa/AssaAttachmentsViewModel.cs:419-433 | src/ui/Features/Ssa/SsaAttachmentsViewModel.cs:387-401 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaAttachmentsViewModel.cs:419` 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) src/ui/Features/Assa/AssaPropertiesViewModel.cs:198— src/ui/Features/Assa/AssaPropertiesViewModel.cs:198-212 | src/ui/Features/Ssa/SsaPropertiesViewModel.cs:186-200 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaPropertiesViewModel.cs:198` 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) src/ui/Features/Main/MainViewModel.cs:4524— src/ui/Features/Main/MainViewModel.cs:4524-4538 | src/ui/Features/Main/MainViewModel.cs:4588-4602 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:4524` 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) src/ui/Features/Main/MainViewModel.cs:11586— src/ui/Features/Main/MainViewModel.cs:11586-11600 | src/ui/Features/Main/MainViewModel.cs:11633-11647 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/ui/Features/Main/MainViewModel.cs:13913— src/ui/Features/Main/MainViewModel.cs:13913-13927 | src/ui/Features/Main/MainViewModel.cs:13946-13960 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/ui/Features/Main/MainViewModel.cs:14212— src/ui/Features/Main/MainViewModel.cs:14212-14226 | src/ui/Features/Main/MainViewModel.cs:14243-14257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:259— src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:259-273 | src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:312-326 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:259` 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) src/ui/Features/Ocr/BinaryOcr/BinaryOcrDbEditViewModel.cs:77— src/ui/Features/Ocr/BinaryOcr/BinaryOcrDbEditViewModel.cs:77-91 | src/ui/Features/Ocr/NOcr/NOcrDbEditViewModel.cs:112-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) src/ui/Features/Ocr/OcrViewModel.cs:843— src/ui/Features/Ocr/OcrViewModel.cs:843-857 | src/ui/Features/Sync/PointSyncViaOther/PointSyncViaOtherViewModel.cs:149-163 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) src/ui/Features/Ocr/OcrViewModel.cs:2506— src/ui/Features/Ocr/OcrViewModel.cs:2506-2520 | src/ui/Features/Ocr/OcrViewModel.cs:2525-2539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2409— src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2409-2423 | src/ui/Features/Tools/JoinSubtitles/JoinSubtitlesViewModel.cs:579-593 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/BatchConvert/BatchConvertViewModel.cs:2409` 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 (15 lines × 2) src/ui/Features/Tools/MergeSubtitlesWithSameText/MergeSameTextViewModel.cs:272— src/ui/Features/Tools/MergeSubtitlesWithSameText/MergeSameTextViewModel.cs:272-286 | src/ui/Features/Tools/MergeSubtitlesWithSameTimeCodes/MergeSameTimeCodesViewModel.cs:317-331 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/MergeSubtitlesWithSameText/MergeSameTextViewModel.cs:272` 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) src/ui/Features/Tools/MergeTwoSubtitles/MergeTwoSubtitlesViewModel.cs:214— src/ui/Features/Tools/MergeTwoSubtitles/MergeTwoSubtitlesViewModel.cs:214-228 | src/ui/Features/Tools/MergeTwoSubtitles/MergeTwoSubtitlesViewModel.cs:239-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/MergeTwoSubtitles/MergeTwoSubtitlesViewModel.cs:214` 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) src/ui/Features/Video/BlankVideo/BlankVideoViewModel.cs:370— src/ui/Features/Video/BlankVideo/BlankVideoViewModel.cs:370-384 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:848-862 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BlankVideo/BlankVideoViewModel.cs:370` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:323— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:323-337 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:246-260 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:323` 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) src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditMp4ViewModel.cs:708— src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditMp4ViewModel.cs:708-722 | src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditViewModel.cs:712-726 — 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 (15 lines × 2) src/ui/Features/Video/TextToSpeech/DownloadTts/DownloadTtsViewModel.cs:344— src/ui/Features/Video/TextToSpeech/DownloadTts/DownloadTtsViewModel.cs:344-358 | src/ui/Features/Video/TextToSpeech/DownloadTts/DownloadTtsViewModel.cs:499-513 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) src/ui/Features/Assa/AssaAttachmentsViewModel.cs:198— src/ui/Features/Assa/AssaAttachmentsViewModel.cs:198-215 | src/ui/Features/Ssa/SsaAttachmentsViewModel.cs:166-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaAttachmentsViewModel.cs:198` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/ui/Features/Assa/AssaStylesViewModel.cs:181— src/ui/Features/Assa/AssaStylesViewModel.cs:181-198 | src/ui/Features/Assa/AssaStylesViewModel.cs:576-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 `src/ui/Features/Assa/AssaStylesViewModel.cs:181` 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) src/ui/Features/Main/MainViewModel.cs:1148— src/ui/Features/Main/MainViewModel.cs:1148-1165 | src/ui/Features/Main/MainViewModel.cs:1224-1241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:1148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/ui/Features/Main/MainViewModel.cs:8970— src/ui/Features/Main/MainViewModel.cs:8970-8987 | src/ui/Features/Main/MainViewModel.cs:9014-9031 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:8970` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/ui/Features/Main/MainViewModel.cs:20165— src/ui/Features/Main/MainViewModel.cs:20165-20182 | src/ui/Features/Main/MainViewModel.cs:20190-20207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:20165` 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) src/ui/Features/Main/MainViewModel.cs:20215— src/ui/Features/Main/MainViewModel.cs:20215-20232 | src/ui/Features/Main/MainViewModel.cs:20240-20257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:20215` 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) src/ui/Features/Main/MainViewModel.cs:20362— src/ui/Features/Main/MainViewModel.cs:20362-20379 | src/ui/Features/Main/MainViewModel.cs:20421-20438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:20362` 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) src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:367— src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:367-384 | src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:557-574 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/BinaryOcr/BinaryOcrCharacterAddViewModel.cs:367` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/ui/Features/Ocr/Download/DownloadTesseractModelViewModel.cs:65— src/ui/Features/Ocr/Download/DownloadTesseractModelViewModel.cs:65-82 | src/ui/Features/Ocr/Download/DownloadTesseractViewModel.cs:63-83 — 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 `src/ui/Features/Ocr/Download/DownloadTesseractModelViewModel.cs:65` 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) src/ui/Features/Ssa/SsaStylesViewModel.cs:160— src/ui/Features/Ssa/SsaStylesViewModel.cs:160-177 | src/ui/Features/Ssa/SsaStylesViewModel.cs:400-417 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ssa/SsaStylesViewModel.cs:160` 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) src/ui/Features/Tools/BatchConvert/BatchConverter.cs:785— src/ui/Features/Tools/BatchConvert/BatchConverter.cs:785-802 | src/ui/Features/Tools/BatchConvert/BatchConverter.cs:991-1008 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/BatchConvert/BatchConverter.cs:785` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/ui/Features/Tools/MergeTwoSubtitles/MergeTwoSubtitlesWindow.cs:256— src/ui/Features/Tools/MergeTwoSubtitles/MergeTwoSubtitlesWindow.cs:256-273 | src/ui/Features/Tools/MergeTwoSubtitles/MergeTwoSubtitlesWindow.cs:383-403 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/MergeTwoSubtitles/MergeTwoSubtitlesWindow.cs:256` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:907— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:907-924 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:684-701 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:907` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1558— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1558-1575 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1092-1109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18 lines × 2) src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:719— src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:719-737 | src/ui/Features/Video/ReEncodeVideo/ReEncodeVideoViewModel.cs:415-432 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18 lines × 2) src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditMp4ViewModel.cs:406— src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditMp4ViewModel.cs:406-423 | src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditViewModel.cs:466-484 — 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 `src/ui/Features/Video/EmbeddedSubtitlesEdit/EmbeddedSubtitlesEditMp4ViewModel.cs:406` 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) src/ui/Features/Video/TextToSpeech/OmniVoiceSettings/OmniVoiceSettingsViewModel.cs:198— src/ui/Features/Video/TextToSpeech/OmniVoiceSettings/OmniVoiceSettingsViewModel.cs:198-215 | src/ui/Features/Video/TextToSpeech/Qwen3TtsSettings/Qwen3TtsSettingsViewModel.cs:189-206 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/TextToSpeech/OmniVoiceSettings/OmniVoiceSettingsViewModel.cs:198` 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) src/ui/Features/Assa/AssaPropertiesViewModel.cs:135— src/ui/Features/Assa/AssaPropertiesViewModel.cs:135-151 | src/ui/Features/Ssa/SsaPropertiesViewModel.cs:123-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaPropertiesViewModel.cs:135` 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) src/ui/Features/Assa/AssaPropertiesViewModel.cs:161— src/ui/Features/Assa/AssaPropertiesViewModel.cs:161-177 | src/ui/Features/Ssa/SsaPropertiesViewModel.cs:149-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaPropertiesViewModel.cs:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/ui/Features/Files/Compare/CompareViewModel.cs:899— src/ui/Features/Files/Compare/CompareViewModel.cs:899-915 | src/ui/Features/Shared/PickLayerFilter/PickLayerFilterViewModel.cs:135-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Files/Compare/CompareViewModel.cs:899` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/ui/Features/Files/FormatProperties/DcinemaInteropProperties/DCinemaInteropPropertiesViewModel.cs:98— src/ui/Features/Files/FormatProperties/DcinemaInteropProperties/DCinemaInteropPropertiesViewModel.cs:98-114 | src/ui/Features/Files/FormatProperties/DcinemaSmpteProperties/DCinemaSmptePropertiesViewModel.cs:126-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) src/ui/Features/Files/FormatProperties/ItunesTimedTextProperties/ItunesTimedTextPropertiesViewModel.cs:123— src/ui/Features/Files/FormatProperties/ItunesTimedTextProperties/ItunesTimedTextPropertiesViewModel.cs:123-139 | src/ui/Features/Files/FormatProperties/TimedText10Properties/TimedText10PropertiesViewModel.cs:119-135 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) src/ui/Features/Files/FormatProperties/RosettaProperties/RosettaPropertiesViewModel.cs:563— src/ui/Features/Files/FormatProperties/RosettaProperties/RosettaPropertiesViewModel.cs:563-579 | src/ui/Features/Files/FormatProperties/WebVttProperties/WebVttPropertiesViewModel.cs:67-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Files/FormatProperties/RosettaProperties/RosettaPropertiesViewModel.cs:563` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/ui/Features/Main/MainViewModel.cs:12710— src/ui/Features/Main/MainViewModel.cs:12710-12727 | src/ui/Features/Main/MainViewModel.cs:12763-12779 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:12710` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:590— src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:590-606 | src/ui/Features/Ocr/NOcr/NOcrInspectViewModel.cs:655-671 — 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 `src/ui/Features/Ocr/NOcr/NOcrCharacterAddViewModel.cs:590` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) src/ui/Features/Ocr/OcrViewModel.cs:1807— src/ui/Features/Ocr/OcrViewModel.cs:1807-1823 | src/ui/Features/Ocr/OcrViewModel.cs:2111-2127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/OcrViewModel.cs:1807` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/ui/Features/Ocr/OcrViewModel.cs:3236— src/ui/Features/Ocr/OcrViewModel.cs:3236-3252 | src/ui/Features/Tools/BatchConvert/BatchConverter.cs:905-921 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Ocr/OcrViewModel.cs:3236` 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 (17 lines × 2) src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:486— src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:486-502 | src/ui/Features/Video/BurnIn/BurnInLogoViewModel.cs:137-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Shared/BinaryEdit/BinaryEditViewModel.cs:486` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/ui/Features/Tools/AiReview/AiReviewProtocol.cs:191— src/ui/Features/Tools/AiReview/AiReviewProtocol.cs:191-207 | src/ui/Features/Translate/LlamaCppAdvanced/LlamaCppAdvancedProtocol.cs:225-241 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Tools/AiReview/AiReviewProtocol.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 (17 lines × 2) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1240— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1240-1256 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:922-938 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1240` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1496— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1496-1512 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:534-550 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1496` 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 (17 lines × 2) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1903— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1903-1919 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1182-1198 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1903` 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) src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1941— src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1941-1957 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:1222-1238 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/BurnIn/BurnInViewModel.cs:1941` 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) src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:353— src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:353-369 | src/ui/Features/Video/TransparentSubtitles/TransparentSubtitlesViewModel.cs:346-362 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Video/CutVideo/CutVideoViewModel.cs:353` 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) src/ui/Features/Assa/AssaProgressBar/AssaProgressBarViewModel.cs:440— src/ui/Features/Assa/AssaProgressBar/AssaProgressBarViewModel.cs:440-448 | src/ui/Features/Assa/AssaProgressBar/AssaProgressBarViewModel.cs:451-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Assa/AssaProgressBar/AssaProgressBarViewModel.cs:440` 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) src/ui/Features/Main/MainViewModel.cs:19890— src/ui/Features/Main/MainViewModel.cs:19890-19898 | src/ui/Features/Main/MainViewModel.cs:19927-19935 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ui/Features/Main/MainViewModel.cs:19890` 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) src/ui/Features/Ocr/Download/DownloadCrispEmbedViewModel.cs:285— src/ui/Features/Ocr/Download/DownloadCrispEmbedViewModel.cs:285-293 | src/ui/Features/Video/SpeechToText/DownloadSpeechToTextEngineViewModel.cs:511-519 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) src/ui/Features/Ocr/Download/DownloadTesseractModelViewModel.cs:160— src/ui/Features/Ocr/Download/DownloadTesseractModelViewModel.cs:160-168 | src/ui/Features/SpellCheck/GetDictionaries/GetDictionariesViewModel.cs:397-405 — the copies span different director...
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.