Public report of watson-developer-cloud/dotnet-standard-sdk, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 03:00 UTC · Survey ID cd_454a7058bfa64990aa6e266ed51bc538
watson-developer-cloud/dotnet-standard-sdk
Measured 17 November 2026, 02:58 UTC, at code version 3d4d105
Code coverage is not measured: No coverage collector is wired up.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 60,005 lines of product code in 34 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Security and Compliance, 31.1
Findings by how serious they are
85 critical566 serious758 minor
2 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 02:58 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
53of 53 dimensions measured by tools.
1371of 1409 findings point to an exact file and line, so you can open each one in the code. The other 38 concern the repository as a whole, such as missing documentation.
53dimensions across 6 lenses, read from 60,005 lines of product code in 34 projects.
watson-developer-cloud/dotnet-standard-sdk falls short of our standard for production because it has passwords or keys in the code's history and pipeline tools referenced by a changeable name. It scores 38.7 out of 100 and is rated Weak, and 66 of its 85 critical findings are security problems.
Security and Compliance, at 31.1, is the weakest lens and counts most in the score. The best first step for the work it takes is improving the documentation, worth about 2.2 points. Replacing the 23 passwords or keys found in the code's history would lift Security and Compliance itself, worth about 4.4 points. Raising Security and Compliance to 70 would lift the score to about 45.3.
Thirty known security holes in the packages the code depends on can be used by attackers. Twenty-three passwords or keys are open to anyone who can read the repository, and nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, replacing each exposed password or key and pinning each tool to an exact version would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The 19 data fields that are written but never read need removing.
The product code is 60,005 lines, about €79,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 31.1 to 70, the lowest score rated Strong, the score would rise from 38.7 to about 45.3.
Code composition: what the lines of code are
Business logic 30%Supporting code 31%Tests 39%
Rebuild cost: about €79,000 · Estimate
Cost to rebuild
€26,000 to €130,000, for 433 to 1,398 hours of work, about 0.5 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 39. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 60,005 lines of product code
Comment lines
The estimate prices 30,160 lines. Comment lines count towards the size of 60,005 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €79,000 to build again, about 0.5 person-years of work. Its weakest lens is Security and Compliance, at 31.1 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Documentation finding(s) in Documentation Quality. Of all the actions in this report, it raises the score most for the work it takes: about 2.2 points for low effort, because it clears the 1 Documentation Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 10% on every change.
How this is estimated: It rests on an assumption of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4)
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
18 modules, with 8 dependencies between them. Every module uses only modules listed above it, so there are no loops.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
72 pairs of types, where a type in Watson.Assistant.v1 uses a type in Watson.Assistant.v1.Model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Watson.Assistant.v1 uses Watson.Assistant.v1.Model, so a change to Watson.Assistant.v1.Model can break Watson.Assistant.v1, while a change to Watson.Assistant.v1 can't break Watson.Assistant.v1.Model.
Position
Below the diagonal: Watson.Assistant.v1 uses a module listed above it, which is the healthy direction.
48 pairs of types, where a type in Watson.Assistant.v2 uses a type in Watson.Assistant.v2.Model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Watson.Assistant.v2 uses Watson.Assistant.v2.Model, so a change to Watson.Assistant.v2.Model can break Watson.Assistant.v2, while a change to Watson.Assistant.v2 can't break Watson.Assistant.v2.Model.
Position
Below the diagonal: Watson.Assistant.v2 uses a module listed above it, which is the healthy direction.
82 pairs of types, where a type in Watson.Discovery.v1 uses a type in Watson.Discovery.v1.Model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Watson.Discovery.v1 uses Watson.Discovery.v1.Model, so a change to Watson.Discovery.v1.Model can break Watson.Discovery.v1, while a change to Watson.Discovery.v1 can't break Watson.Discovery.v1.Model.
Position
Below the diagonal: Watson.Discovery.v1 uses a module listed above it, which is the healthy direction.
70 pairs of types, where a type in Watson.Discovery.v2 uses a type in Watson.Discovery.v2.Model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Watson.Discovery.v2 uses Watson.Discovery.v2.Model, so a change to Watson.Discovery.v2.Model can break Watson.Discovery.v2, while a change to Watson.Discovery.v2 can't break Watson.Discovery.v2.Model.
Position
Below the diagonal: Watson.Discovery.v2 uses a module listed above it, which is the healthy direction.
Watson.LanguageTranslator.v3 uses Watson.LanguageTranslator.v3.Model, so a change to Watson.LanguageTranslator.v3.Model can break Watson.LanguageTranslator.v3, while a change to Watson.LanguageTranslator.v3 can't break Watson.LanguageTranslator.v3.Model.
Position
Below the diagonal: Watson.LanguageTranslator.v3 uses a module listed above it, which is the healthy direction.
Watson.NaturalLanguageUnderstanding.v1 uses Watson.NaturalLanguageUnderstanding.v1.Model, so a change to Watson.NaturalLanguageUnderstanding.v1.Model can break Watson.NaturalLanguageUnderstanding.v1, while a change to Watson.NaturalLanguageUnderstanding.v1 can't break Watson.NaturalLanguageUnderstanding.v1.Model.
Position
Below the diagonal: Watson.NaturalLanguageUnderstanding.v1 uses a module listed above it, which is the healthy direction.
40 pairs of types, where a type in Watson.SpeechToText.v1 uses a type in Watson.SpeechToText.v1.Model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Watson.SpeechToText.v1 uses Watson.SpeechToText.v1.Model, so a change to Watson.SpeechToText.v1.Model can break Watson.SpeechToText.v1, while a change to Watson.SpeechToText.v1 can't break Watson.SpeechToText.v1.Model.
Position
Below the diagonal: Watson.SpeechToText.v1 uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in Watson.TextToSpeech.v1 uses a type in Watson.TextToSpeech.v1.Model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Watson.TextToSpeech.v1 uses Watson.TextToSpeech.v1.Model, so a change to Watson.TextToSpeech.v1.Model can break Watson.TextToSpeech.v1, while a change to Watson.TextToSpeech.v1 can't break Watson.TextToSpeech.v1.Model.
Position
Below the diagonal: Watson.TextToSpeech.v1 uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 36.1 · Weak · gated by D4, X1, X5, IC1 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
475
High / Critical
A03:2025 — Software Supply Chain Failures
53
High / Critical
A07:2025 — Authentication Failures
24
High / Critical
A02:2025 — Security Misconfiguration
2
High / Critical
Roadmap
Top priorities: Resolve the 23 REDACTED finding(s) in Secrets (history) — start with REDACTED (20), REDACTED (2), REDACTED; Resolve the 19 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED (15), DiscoveryIntegrationTests.cs (3), LanguageTranslatorServiceIntegrationTests.cs; Resolve the 27 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (27).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 85
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 566
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 758
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 2
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 53 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 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, 1371 of 1409 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 or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (24 contributor(s) across 2079 commit(s) sampled, automation and bot accounts excluded). One of them holds 81% of the history; the other 23 hold 0.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'REDACTED' with message: The referenced project ../IBM.Watson.CompareComply.v1/IBM.Watson.CompareComply.v1.csproj does not exist.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (59,923 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
P10 Library API & versioning — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 234 further occurrence(s) are not listed individually; the score already reflects all 274.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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 — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
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 on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
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.
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with SpeechToTextService.CreateJob (cyclomatic 36). — Refactoring it lifts Cyclomatic Complexity from 7.3 to about 7.5/10.
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.
+ 16 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 21 bodies over 15 down to 15 or less in Cognitive Complexity — start with SpeechToTextService.CreateJob (cognitive 35), DiscoveryService.Query (cognitive 31), DiscoveryService.QueryNotices (cognitive 30). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 21 together lifts Cognitive Complexity from 7.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.4 / 10Stronggated by 14 serious findings✓ 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 7 FileTooLong finding(s) in God Classes — start with DiscoveryService.cs (2), AssistantService.cs (2), SpeechToTextService.cs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 4 TooManyMethods finding(s) in God Classes — start with DiscoveryService.cs (2), AssistantService.cs, SpeechToTextService.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with AssistantService.cs, TextToSpeechService.cs, NaturalLanguageUnderstandingService.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
170 duplicated block group(s) detected. 25.6 % of the production lines (15,314 of 59,923) are in a reported copy. A further 57 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 13 of the 227 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 108 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 23 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with DiscoveryService.cs (8), AssistantService.cs (5), SpeechToTextService.cs (4). — One of this dimension's main actionable groups (23 warning-level).
Resolve the 21 Duplicated block (16 lines × 3) finding(s) in Code Duplication — start with DiscoveryService.cs (10), AssistantService.cs (8), NaturalLanguageUnderstandingService.cs. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 6 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with DiscoveryService.cs (3), ModelEvaluationMacroAverage.cs, SpeechToTextService.cs. — One of this dimension's main actionable groups (6 warning-level).
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.
D10 · Test Quality9.7 / 10Stronggated by 27 serious findings✓ 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.
Resolve the 12 Test cannot fail finding(s) in Test Quality — start with TextToSpeechServiceIntegrationTests.cs (6), NaturalLanguageUnderstandingIntegrationTests.cs (4), DiscoveryIntegrationTests.cs (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 No assertions finding(s) in Test Quality — start with SpeechToTextServiceGeneratedUnitTests.cs (7), TextToSpeechServiceGeneratedUnitTests.cs (4). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 4 Skipped test finding(s) in Test Quality — start with LanguageTranslatorServiceIntegrationTests.cs (3), DiscoveryIntegrationTests.cs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
Resolve the 68 Deprecated finding(s) in Dependency Hygiene — start with IBM.Watson.SpeechToText.v1.IntegrationTests.csproj (4), IBM.Watson.SpeechToText.v1.UnitTests.csproj (4), IBM.Watson.TextToSpeech.v1.IntegrationTests.csproj (4). — One of this dimension's main actionable groups (68 warning-level).
Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with IBM.Watson.Assistant.v1.IntegrationTests.csproj (6). — One of this dimension's main actionable groups (6 recommendation-level).
Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 349 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 13 direct `PackageReference`(s), and 131 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: 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.
23 deducted debt markers + unmeasured dead symbols across 59923 LoC in the .NET projects (0.3/KLoC) → score 9.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Resolve the 19 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED (15), DiscoveryIntegrationTests.cs (3), LanguageTranslatorServiceIntegrationTests.cs. — One of this dimension's main actionable groups (19 issue-level).
Resolve the 2 CommentedOutCode finding(s) in Explicit Debt — start with DiscoveryIntegrationTests.cs, SpeechToTextServiceIntegrationTest.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 DeadPreprocessorBranch finding(s) in Explicit Debt — start with AssistantServiceIntegrationTests.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
34 projects, 604 source files, 79081 hand-written lines of code (59923 production / 19158 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 32 inter-project edges.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F4 map. 2 document(s) read across 10 unit(s).
Documentation: no map of the repository's partsREADME.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×6src/IBM.Watson.Assistant.v1/AssistantService.cs:3051
What to do
Resolve the 27 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (27). — One of this dimension's main actionable groups (27 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 34 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×4REDACTED:1
What to do
Resolve the 4 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED, IBM.Watson.Discovery.v1.csproj, IBM.Watson.Discovery.v2.csproj. — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability4.2 / 10Weak✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
100 % of calls cross a namespace and 39 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
High interface indirection
What to do
Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
23 finding(s): 0 critical, 23 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 23 REDACTED finding(s) in Secrets (history) — start with REDACTED (20), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (23 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).
487 finding(s): 0 critical, 12 high, 19 medium, 456 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 25 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (20), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (25 issue-level).
Resolve the 11 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
183 of 196 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs. Counted over 196 of the 558 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1
Dormant codebase
What to do
Resolve the 180 Orphaned file finding(s) in Knowledge Freshness — start with RuntimeEntityInterpretation.cs (2), RuntimeResponseGeneric.cs (2), IAssistantService.cs (2). — One of this dimension's main actionable groups (180 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with SpeechToTextService.cs, DiscoveryService.cs, AssistantService.cs. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 34 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 20 End-of-life runtime finding(s) in Platform End-of-Life — start with IBM.Watson.Assistant.v1.Examples.csproj, IBM.Watson.Assistant.v1.IntegrationTests.csproj, IBM.Watson.Assistant.v1.UnitTests.csproj. — One of this dimension's main actionable groups (20 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
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.
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.
`Common` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (os, osVersion, frameworkDescription; e.g. `os` at line 54). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — REDACTED:25
What to do
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`IAssistantService` declares 49 members: `Message`, `BulkClassify`, `ListWorkspaces`, `CreateWorkspace`, `GetWorkspace`, `UpdateWorkspace`, `DeleteWorkspace`, `CreateWorkspaceAsync`, `UpdateWorkspaceAsync`, `ExportWorkspaceAsync`, `ListIntents`, `CreateIntent`, `GetIntent`, `UpdateIntent`, `DeleteIntent`, `ListExamples`, `CreateExample`, `GetExample`, `UpdateExample`, `DeleteExample`, `ListCounterexamples`, `CreateCounterexample`, `GetCounterexample`, `UpdateCounterexample`, `DeleteCounterexample`, `ListEntities`, `CreateEntity`, `GetEntity`, `UpdateEntity`, `DeleteEntity`, `ListMentions`, `ListValues`, `CreateValue`, `GetValue`, `UpdateValue`, `DeleteValue`, `ListSynonyms`, `CreateSynonym`, `GetSynonym`, `UpdateSynonym`, and 9 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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. — src/IBM.Watson.Assistant.v1/IAssistantService.cs:24
`IAssistantService` declares 23 members: `CreateAssistant`, `ListAssistants`, `DeleteAssistant`, `CreateSession`, `DeleteSession`, `Message`, `MessageStateless`, `BulkClassify`, `ListLogs`, `DeleteUserData`, `ListEnvironments`, `GetEnvironment`, `UpdateEnvironment`, `CreateRelease`, `ListReleases`, `GetRelease`, `DeleteRelease`, `DeployRelease`, `GetSkill`, `UpdateSkill`, `ExportSkills`, `ImportSkills`, `ImportSkillsStatus`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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. — src/IBM.Watson.Assistant.v2/IAssistantService.cs:25
`IDiscoveryService` declares 62 members: `CreateEnvironment`, `ListEnvironments`, `GetEnvironment`, `UpdateEnvironment`, `DeleteEnvironment`, `ListFields`, `CreateConfiguration`, `ListConfigurations`, `GetConfiguration`, `UpdateConfiguration`, `DeleteConfiguration`, `CreateCollection`, `ListCollections`, `GetCollection`, `UpdateCollection`, `DeleteCollection`, `ListCollectionFields`, `ListExpansions`, `CreateExpansions`, `DeleteExpansions`, `GetTokenizationDictionaryStatus`, `CreateTokenizationDictionary`, `DeleteTokenizationDictionary`, `GetStopwordListStatus`, `CreateStopwordList`, `DeleteStopwordList`, `AddDocument`, `GetDocumentStatus`, `UpdateDocument`, `DeleteDocument`, `Query`, `QueryNotices`, `FederatedQuery`, `FederatedQueryNotices`, `GetAutocompletion`, `ListTrainingData`, `AddTrainingData`, `DeleteAllTrainingData`, `GetTrainingData`, `DeleteTrainingData`, and 22 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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. — src/IBM.Watson.Discovery.v1/IDiscoveryService.cs:26
`IDiscoveryService` declares 50 members: `ListProjects`, `CreateProject`, `GetProject`, `UpdateProject`, `DeleteProject`, `ListFields`, `ListCollections`, `CreateCollection`, `GetCollection`, `UpdateCollection`, `DeleteCollection`, `ListDocuments`, `AddDocument`, `GetDocument`, `UpdateDocument`, `DeleteDocument`, `Query`, `GetAutocompletion`, `QueryCollectionNotices`, `QueryNotices`, `GetStopwordList`, `CreateStopwordList`, `DeleteStopwordList`, `ListExpansions`, `CreateExpansions`, `DeleteExpansions`, `GetComponentSettings`, `ListTrainingQueries`, `DeleteTrainingQueries`, `CreateTrainingQuery`, `GetTrainingQuery`, `UpdateTrainingQuery`, `DeleteTrainingQuery`, `ListEnrichments`, `CreateEnrichment`, `GetEnrichment`, `UpdateEnrichment`, `DeleteEnrichment`, `ListDocumentClassifiers`, `CreateDocumentClassifier`, and 10 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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. — src/IBM.Watson.Discovery.v2/IDiscoveryService.cs:24
`ISpeechToTextService` declares 41 members: `ListModels`, `GetModel`, `Recognize`, `RegisterCallback`, `UnregisterCallback`, `CreateJob`, `CheckJobs`, `CheckJob`, `DeleteJob`, `CreateLanguageModel`, `ListLanguageModels`, `GetLanguageModel`, `DeleteLanguageModel`, `TrainLanguageModel`, `ResetLanguageModel`, `UpgradeLanguageModel`, `ListCorpora`, `AddCorpus`, `GetCorpus`, `DeleteCorpus`, `ListWords`, `AddWords`, `AddWord`, `GetWord`, `DeleteWord`, `ListGrammars`, `AddGrammar`, `GetGrammar`, `DeleteGrammar`, `CreateAcousticModel`, `ListAcousticModels`, `GetAcousticModel`, `DeleteAcousticModel`, `TrainAcousticModel`, `ResetAcousticModel`, `UpgradeAcousticModel`, `ListAudio`, `AddAudio`, `GetAudio`, `DeleteAudio`, and 1 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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. — src/IBM.Watson.SpeechToText.v1/ISpeechToTextService.cs:24
`ITextToSpeechService` declares 23 members: `ListVoices`, `GetVoice`, `Synthesize`, `GetPronunciation`, `CreateCustomModel`, `ListCustomModels`, `UpdateCustomModel`, `GetCustomModel`, `DeleteCustomModel`, `AddWords`, `ListWords`, `AddWord`, `GetWord`, `DeleteWord`, `ListCustomPrompts`, `AddCustomPrompt`, `GetCustomPrompt`, `DeleteCustomPrompt`, `ListSpeakerModels`, `CreateSpeakerModel`, `GetSpeakerModel`, `DeleteSpeakerModel`, `DeleteUserData`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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. — src/IBM.Watson.TextToSpeech.v1/ITextToSpeechService.cs:24
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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.
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.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Control only reaches here when `string.IsNullOrEmpty(intent)` is false, because the guard on line 1245 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:1270
Control only reaches here when `string.IsNullOrEmpty(text)` is false, because the guard on line 1702 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:1727
Control only reaches here when `string.IsNullOrEmpty(text)` is false, because the guard on line 2142 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:2167
Control only reaches here when `string.IsNullOrEmpty(entity)` is false, because the guard on line 2555 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:2580
Control only reaches here when `string.IsNullOrEmpty(value)` is false, because the guard on line 3123 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:3148
Control only reaches here when `string.IsNullOrEmpty(synonym)` is false, because the guard on line 3649 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:3674
Control only reaches here when `string.IsNullOrEmpty(dialogNode)` is false, because the guard on line 4140 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:4165
Control only reaches here when `string.IsNullOrEmpty(filter)` is false, because the guard on line 4698 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:4716
Control only reaches here when `string.IsNullOrEmpty(customerId)` is false, because the guard on line 4773 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v1/AssistantService.cs:4791
Control only reaches here when `string.IsNullOrEmpty(customerId)` is false, because the guard on line 835 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v2/AssistantService.cs:853
Control only reaches here when `string.IsNullOrEmpty(environmentId)` is false, because the guard on line 1584 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Assistant.v2/AssistantService.cs:1609
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 83 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:104
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 465 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:486
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 695 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:716
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 851 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:872
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 1061 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1082
Control only reaches here when `string.IsNullOrEmpty(collectionIds)` is false, because the guard on line 2775 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2801
Control only reaches here when `string.IsNullOrEmpty(prefix)` is false, because the guard on line 3091 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3109
Control only reaches here when `string.IsNullOrEmpty(customerId)` is false, because the guard on line 3930 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3947
Control only reaches here when `string.IsNullOrEmpty(type)` is false, because the guard on line 3984 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4009
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 129 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:154
Control only reaches here when `string.IsNullOrEmpty(type)` is false, because the guard on line 133 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:158
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 512 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:533
Control only reaches here when `string.IsNullOrEmpty(prefix)` is false, because the guard on line 1618 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1636
Control only reaches here when `string.IsNullOrEmpty(naturalLanguageQuery)` is false, because the guard on line 2483 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2508
Control only reaches here when `string.IsNullOrEmpty(naturalLanguageQuery)` is false, because the guard on line 2640 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2665
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 3000 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3021
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 3626 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3647
Control only reaches here when `string.IsNullOrEmpty(customerId)` is false, because the guard on line 4097 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.Discovery.v2/DiscoveryService.cs:4114
Control only reaches here when `string.IsNullOrEmpty(baseModelId)` is false, because the guard on line 456 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:494
Control only reaches here when `string.IsNullOrEmpty(callbackUrl)` is false, because the guard on line 1371 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1385
Control only reaches here when `string.IsNullOrEmpty(callbackUrl)` is false, because the guard on line 1426 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1439
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 2678 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2699
Control only reaches here when `string.IsNullOrEmpty(baseModelName)` is false, because the guard on line 2682 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2703
Control only reaches here when `string.IsNullOrEmpty(contentType)` is false, because the guard on line 4336 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4351
Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 4583 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4604
Control only reaches here when `string.IsNullOrEmpty(baseModelName)` is false, because the guard on line 4587 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4608
Control only reaches here when `string.IsNullOrEmpty(customerId)` is false, because the guard on line 5794 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5807
Control only reaches here when `string.IsNullOrEmpty(text)` is false, because the guard on line 510 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:551
Control only reaches here when `string.IsNullOrEmpty(text)` is false, because the guard on line 921 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. — src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:935
What to do
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 repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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 numbered `NNNN-title` documents in any markup this check reads, 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.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
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 & versioning9.5 / 10Exemplary✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeImage` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeImage.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeImage.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeOption` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeOption.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeOption.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypePause` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypePause.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypePause.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeSearchSkill` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeSearchSkill.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeSearchSkill.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined.cs:26
`IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeAudio` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeConnectToAgent` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeConnectToAgent.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeConnectToAgent.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeIframe` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeIframe.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeIframe.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeImage` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeImage.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeImage.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeOption` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeOption.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeOption.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypePause` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypePause.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypePause.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeSuggestion` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeSuggestion.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeSuggestion.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeText` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeText.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeText.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeUserDefined` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeUserDefined.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeUserDefined.cs:26
`IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeVideo` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:26
`IBM.Watson.Assistant.v2.Model.LogMessageSourceAction` (src/IBM.Watson.Assistant.v2/Model/LogMessageSourceAction.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/LogMessageSourceAction.cs:25
`IBM.Watson.Assistant.v2.Model.LogMessageSourceDialogNode` (src/IBM.Watson.Assistant.v2/Model/LogMessageSourceDialogNode.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/LogMessageSourceDialogNode.cs:25
`IBM.Watson.Assistant.v2.Model.LogMessageSourceHandler` (src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs:25
`IBM.Watson.Assistant.v2.Model.LogMessageSourceStep` (src/IBM.Watson.Assistant.v2/Model/LogMessageSourceStep.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/LogMessageSourceStep.cs:25
`IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventActionFinished` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionFinished.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionFinished.cs:26
`IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventActionVisited` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionVisited.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionVisited.cs:25
`IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventCallout` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventCallout.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventCallout.cs:25
`IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventHandlerVisited` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventHandlerVisited.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventHandlerVisited.cs:25
`IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventNodeVisited` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventNodeVisited.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventNodeVisited.cs:25
`IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventSearch` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventSearch.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventSearch.cs:25
`IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventStepAnswered` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventStepAnswered.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventStepAnswered.cs:25
`IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventStepVisited` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventStepVisited.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventStepVisited.cs:25
`IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeAudio` (src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:26
`IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeConnectToAgent` (src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeConnectToAgent.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeConnectToAgent.cs:26
`IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeDate` (src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeDate.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeDate.cs:25
`IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeIframe` (src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeIframe.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeIframe.cs:26
`IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeSearch` (src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeSearch.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeSearch.cs:26
`IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeSuggestion` (src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeSuggestion.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeSuggestion.cs:26
`IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeUserDefined` (src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeUserDefined.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeUserDefined.cs:26
`IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeVideo` (src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:26
What to do
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeImage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeOption` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypePause` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeSearchSkill` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeAudio` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeConnectToAgent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeIframe` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeImage` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeOption` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypePause` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeSuggestion` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeText` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeUserDefined` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeVideo` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.LogMessageSourceAction` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.LogMessageSourceDialogNode` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.LogMessageSourceHandler` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.LogMessageSourceStep` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventActionFinished` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventActionVisited` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventCallout` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventHandlerVisited` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventNodeVisited` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventSearch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventStepAnswered` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventStepVisited` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeAudio` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeConnectToAgent` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeDate` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeIframe` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeSearch` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeSuggestion` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeUserDefined` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Assistant.v2.Model.RuntimeResponseGenericRuntimeResponseTypeVideo` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v1.Model.QueryCalculationAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v1.Model.QueryHistogramAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v1.Model.QueryNestedAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v1.Model.QueryTopHitsAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryCalculationAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryGroupByAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryHistogramAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryNestedAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryPairAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryTimesliceAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryTopHitsAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryTopicAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `IBM.Watson.Discovery.v2.Model.QueryAggregationQueryTrendAggregation` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
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, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:11
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:38
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET 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 · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. — REDACTED:832
What to do
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×40) — src/IBM.Watson.Assistant.v1/AssistantService.cs:166, src/IBM.Watson.Assistant.v1/AssistantService.cs:233, src/IBM.Watson.Assistant.v1/AssistantService.cs:306, …
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 832). Every use of it in `DownloadAcousticResource` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:832
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/3 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 10 observation(s) recorded · 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.
SC1 Supply-chain hygiene — 33 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
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 — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — no coverage collector is wired up
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
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.
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no async method does work a token could cancel
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
WriteOnlyPrivateField src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:33— private string counterexample — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Assistant.v2/Examples/ServiceExample.cs:33— private string inputString — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:39— private string filepathToIngest — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:40— private string stopwordFileToIngest — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:45— private string sessionToken — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:47— private string updatedConfigurationName — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:49— private string updatedCollectionName — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Discovery.v2/Test/Integration/DiscoveryIntegrationTests.cs:40— private string testPDF — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Discovery.v2/Test/Integration/DiscoveryIntegrationTests.cs:42— private string bearerToken — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.Discovery.v2/Test/Integration/DiscoveryIntegrationTests.cs:43— private string serviceUrl — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.LanguageTranslator.v3/Examples/ServiceExample.cs:32— private string glossaryPath — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.LanguageTranslator.v3/Examples/ServiceExample.cs:33— private string documentToTranslatePath — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/IBM.Watson.LanguageTranslator.v3/Test/Integration/LanguageTranslatorServiceIntegrationTests.cs:39— private string pptToTranslatePath — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:33— private string testAudioPath — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:34— private string corpusPath — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:36— private string grammarPath — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:37— private string grammarsContentType — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:40— private string jobId — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:44— private byte[] acousticResourceData — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:1270— Control only reaches here when `string.IsNullOrEmpty(intent)` is false, because the guard on line 1245 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:1727— Control only reaches here when `string.IsNullOrEmpty(text)` is false, because the guard on line 1702 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:2167— Control only reaches here when `string.IsNullOrEmpty(text)` is false, because the guard on line 2142 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:2580— Control only reaches here when `string.IsNullOrEmpty(entity)` is false, because the guard on line 2555 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:3148— Control only reaches here when `string.IsNullOrEmpty(value)` is false, because the guard on line 3123 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:3674— Control only reaches here when `string.IsNullOrEmpty(synonym)` is false, because the guard on line 3649 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:4165— Control only reaches here when `string.IsNullOrEmpty(dialogNode)` is false, because the guard on line 4140 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:4716— Control only reaches here when `string.IsNullOrEmpty(filter)` is false, because the guard on line 4698 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v1/AssistantService.cs:4791— Control only reaches here when `string.IsNullOrEmpty(customerId)` is false, because the guard on line 4773 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v2/AssistantService.cs:853— Control only reaches here when `string.IsNullOrEmpty(customerId)` is false, because the guard on line 835 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Assistant.v2/AssistantService.cs:1609— Control only reaches here when `string.IsNullOrEmpty(environmentId)` is false, because the guard on line 1584 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:104— Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 83 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:486— Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 465 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:716— Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 695 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:872— Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 851 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1082— Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 1061 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2801— Control only reaches here when `string.IsNullOrEmpty(collectionIds)` is false, because the guard on line 2775 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3109— Control only reaches here when `string.IsNullOrEmpty(prefix)` is false, because the guard on line 3091 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3947— Control only reaches here when `string.IsNullOrEmpty(customerId)` is false, because the guard on line 3930 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4009— Control only reaches here when `string.IsNullOrEmpty(type)` is false, because the guard on line 3984 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v2/DiscoveryService.cs:154— Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 129 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v2/DiscoveryService.cs:158— Control only reaches here when `string.IsNullOrEmpty(type)` is false, because the guard on line 133 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v2/DiscoveryService.cs:533— Control only reaches here when `string.IsNullOrEmpty(name)` is false, because the guard on line 512 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1636— Control only reaches here when `string.IsNullOrEmpty(prefix)` is false, because the guard on line 1618 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2508— Control only reaches here when `string.IsNullOrEmpty(naturalLanguageQuery)` is false, because the guard on line 2483 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:166— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:233— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:306— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:450— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:524— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:685— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:739— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:855— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:991— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1068— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1176— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1289— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1365— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1472— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1535— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1626— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1742— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1820— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1919— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:1991— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:2074— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:2178— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:2248— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:2330— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/IBM.Watson.Assistant.v1/AssistantService.cs:2394— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
+ 15 more in this group — see findings.md.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×33
NuGet dependencies are not locked REDACTED:38— REDACTED declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj:32— src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Assistant.v1/Test/Unit/IBM.Watson.Assistant.v1.UnitTests.csproj:32— src/IBM.Watson.Assistant.v1/Test/Unit/IBM.Watson.Assistant.v1.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Assistant.v2/Examples/IBM.Watson.Assistant.v2.Examples.csproj:9— src/IBM.Watson.Assistant.v2/Examples/IBM.Watson.Assistant.v2.Examples.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Assistant.v2/IBM.Watson.Assistant.v2.csproj:37— src/IBM.Watson.Assistant.v2/IBM.Watson.Assistant.v2.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Assistant.v2/Test/Integration/IBM.Watson.Assistant.v2.IntegrationTests.csproj:32— src/IBM.Watson.Assistant.v2/Test/Integration/IBM.Watson.Assistant.v2.IntegrationTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Assistant.v2/Test/Unit/IBM.Watson.Assistant.v2.UnitTests.csproj:32— src/IBM.Watson.Assistant.v2/Test/Unit/IBM.Watson.Assistant.v2.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Common/IBM.Watson.Common.csproj:27— src/IBM.Watson.Common/IBM.Watson.Common.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Discovery.v1/Examples/IBM.Watson.Discovery.v1.Examples.csproj:9— src/IBM.Watson.Discovery.v1/Examples/IBM.Watson.Discovery.v1.Examples.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Discovery.v1/IBM.Watson.Discovery.v1.csproj:37— src/IBM.Watson.Discovery.v1/IBM.Watson.Discovery.v1.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Discovery.v1/Test/Integration/IBM.Watson.Discovery.v1.IntegrationTests.csproj:32— src/IBM.Watson.Discovery.v1/Test/Integration/IBM.Watson.Discovery.v1.IntegrationTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Discovery.v1/Test/Unit/IBM.Watson.Discovery.v1.UnitTests.csproj:32— src/IBM.Watson.Discovery.v1/Test/Unit/IBM.Watson.Discovery.v1.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Discovery.v2/Examples/IBM.Watson.Discovery.v2.Examples.csproj:9— src/IBM.Watson.Discovery.v2/Examples/IBM.Watson.Discovery.v2.Examples.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Discovery.v2/IBM.Watson.Discovery.v2.csproj:37— src/IBM.Watson.Discovery.v2/IBM.Watson.Discovery.v2.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Discovery.v2/Test/Integration/IBM.Watson.Discovery.v2.IntegrationTests.csproj:32— src/IBM.Watson.Discovery.v2/Test/Integration/IBM.Watson.Discovery.v2.IntegrationTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.Discovery.v2/Test/Unit/IBM.Watson.Discovery.v2.UnitTests.csproj:32— src/IBM.Watson.Discovery.v2/Test/Unit/IBM.Watson.Discovery.v2.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked REDACTED:32— REDACTED declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.LanguageTranslator.v3/Examples/IBM.Watson.LanguageTranslator.v3.Examples.csproj:9— src/IBM.Watson.LanguageTranslator.v3/Examples/IBM.Watson.LanguageTranslator.v3.Examples.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.LanguageTranslator.v3/IBM.Watson.LanguageTranslator.v3.csproj:37— src/IBM.Watson.LanguageTranslator.v3/IBM.Watson.LanguageTranslator.v3.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.LanguageTranslator.v3/Test/Integration/IBM.Watson.LanguageTranslator.v3.IntegrationTests.csproj:32— src/IBM.Watson.LanguageTranslator.v3/Test/Integration/IBM.Watson.LanguageTranslator.v3.IntegrationTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.LanguageTranslator.v3/Test/Unit/IBM.Watson.LanguageTranslator.v3.UnitTests.csproj:32— src/IBM.Watson.LanguageTranslator.v3/Test/Unit/IBM.Watson.LanguageTranslator.v3.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.NaturalLanguageUnderstanding.v1/Examples/IBM.Watson.NLU.v1.Examples.csproj:9— src/IBM.Watson.NaturalLanguageUnderstanding.v1/Examples/IBM.Watson.NLU.v1.Examples.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.NaturalLanguageUnderstanding.v1/IBM.Watson.NaturalLanguageUnderstanding.v1.csproj:37— src/IBM.Watson.NaturalLanguageUnderstanding.v1/IBM.Watson.NaturalLanguageUnderstanding.v1.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/IBM.Watson.NLU.v1.IntegrationTests.csproj:32— src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/IBM.Watson.NLU.v1.IntegrationTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Unit/IBM.Watson.NaturalLanguageUnderstanding.v1.UnitTests.csproj:32— src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Unit/IBM.Watson.NaturalLanguageUnderstanding.v1.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:525— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:525-540 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:677-692 — both copies are in the same file, so extract the block into 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/IBM.Watson.Assistant.v1/AssistantService.cs:163— src/IBM.Watson.Assistant.v1/AssistantService.cs:163-178 | src/IBM.Watson.Assistant.v2/AssistantService.cs:534-549 — `src/IBM.Watson.Assistant.v1/AssistantService.cs` and `src/IBM.Watson.Assistant.v2/AssistantService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 104 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:163` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Assistant.v2/AssistantService.cs:1241— src/IBM.Watson.Assistant.v2/AssistantService.cs:1241-1256 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1445-1460 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Assistant.v2/AssistantService.cs:1241` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `string description =` in one and `bool? includeAudit =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 2) src/IBM.Watson.Assistant.v2/AssistantService.cs:1692— src/IBM.Watson.Assistant.v2/AssistantService.cs:1692-1707 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1804-1819 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Assistant.v2/AssistantService.cs:1692` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Assistant.v2/AssistantService.cs:1992— src/IBM.Watson.Assistant.v2/AssistantService.cs:1992-2007 | src/IBM.Watson.Assistant.v2/AssistantService.cs:2059-2074 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Assistant.v2/AssistantService.cs:1992` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:413— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:413-428 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1222-1237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:413` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:951— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:951-966 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:462-477 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:951` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2074— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2074-2089 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:940-955 — 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:2074` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2290— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2290-2305 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1404-1419 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2290` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3123— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3123-3138 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1654-1669 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3123` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4959— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4959-4974 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:5022-5037 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:4959` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v1/Model/QueryHistogramAggregationResult.cs:26— src/IBM.Watson.Discovery.v1/Model/QueryHistogramAggregationResult.cs:26-41 | src/IBM.Watson.Discovery.v2/Model/QueryHistogramAggregationResult.cs:26-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/IBM.Watson.Discovery.v1/Model/QueryHistogramAggregationResult.cs:26` it does not close everything it opens, so those exact lines 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/IBM.Watson.Discovery.v2/DiscoveryService.cs:1909— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1909-1924 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1992-2007 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v2/DiscoveryService.cs:1909` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Discovery.v2/Model/CreateEnrichment.cs:111— src/IBM.Watson.Discovery.v2/Model/CreateEnrichment.cs:111-126 | src/IBM.Watson.Discovery.v2/Model/Enrichment.cs:82-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v2/Model/Enrichment.cs:80` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/CreateEnrichment.cs:110` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:505— src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:505-520 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:615-630 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:505` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:502` calls `WithBodyContent` and `src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:612` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2719— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2719-2734 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2956-2971 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2719` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3147— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3147-3162 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5031-5046 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3147` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3720— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3720-3735 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1737-1752 — 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3720` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4620— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4620-4635 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4857-4872 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4620` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1261— src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1261-1276 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1548-1563 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1261` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2181— src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2181-2196 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2243-2258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2181` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) src/IBM.Watson.Assistant.v2/AssistantService.cs:1028— src/IBM.Watson.Assistant.v2/AssistantService.cs:1028-1047 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:198-213 — 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/IBM.Watson.Assistant.v2/AssistantService.cs:1028` it does not close everything it opens, so those exact lines 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/IBM.Watson.Discovery.v1/Model/Notice.cs:72— src/IBM.Watson.Discovery.v1/Model/Notice.cs:72-89 | src/IBM.Watson.Discovery.v2/Model/Notice.cs:78-93 — before extracting anything, compare `src/IBM.Watson.Discovery.v1/Model/Notice.cs` and `src/IBM.Watson.Discovery.v2/Model/Notice.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:1286— src/IBM.Watson.Assistant.v1/AssistantService.cs:1286-1301 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1362-1377 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1469-1484 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:1286` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:1739— src/IBM.Watson.Assistant.v1/AssistantService.cs:1739-1754 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1817-1832 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1916-1931 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:1739` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:2175— src/IBM.Watson.Assistant.v1/AssistantService.cs:2175-2190 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2245-2260 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2327-2342 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:2175` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:2604— src/IBM.Watson.Assistant.v1/AssistantService.cs:2604-2619 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2680-2695 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2797-2812 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:2604` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:3172— src/IBM.Watson.Assistant.v1/AssistantService.cs:3172-3187 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3257-3272 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3390-3405 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:3172` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:3682— src/IBM.Watson.Assistant.v1/AssistantService.cs:3682-3697 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3769-3784 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3871-3886 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:3682` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:4245— src/IBM.Watson.Assistant.v1/AssistantService.cs:4245-4260 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4314-4329 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4510-4525 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:4245` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:4656— src/IBM.Watson.Assistant.v1/AssistantService.cs:4656-4671 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4734-4749 | src/IBM.Watson.Assistant.v2/AssistantService.cs:796-811 — `src/IBM.Watson.Assistant.v1/AssistantService.cs` and `src/IBM.Watson.Assistant.v2/AssistantService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 104 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:4656` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:514— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:514-529 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:634-649 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:744-759 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:514` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:892— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:892-907 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1012-1027 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1098-1113 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:892` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `string language =` in one and `string configurationId =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2503— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2503-2518 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2885-2900 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1572-1587 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2503` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3639— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3639-3654 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3815-3830 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3896-3911 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3639` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4619— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4619-4634 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4685-4700 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4779-4794 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4619` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:170— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:170-185 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:225-240 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:290-305 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:170` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `DefaultQueryParams defaultQueryParameters =` in one and `string name =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:553— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:553-568 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:617-632 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:701-716 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:553` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2886— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2886-2901 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2950-2965 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3033-3048 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2886` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `System.IO.MemoryStream file =` in one and `string description =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2883` calls `WithBodyContent` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2947` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3259— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3259-3274 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3323-3338 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3430-3445 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3259` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3256` calls `WithBodyContent` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3320` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 3) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3679— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3679-3694 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3752-3767 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3840-3855 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3679` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `double? improvementRatio =` in one and `string description =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 3) src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:282— src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:282-297 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:732-747 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:1202-1217 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:282` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v1/Model/Workspace.cs:82— src/IBM.Watson.Assistant.v1/Model/Workspace.cs:82-97 | src/IBM.Watson.Assistant.v2/Model/AssistantData.cs:36-51 | src/IBM.Watson.Discovery.v2/Model/CreateDocumentClassifier.cs:31-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Assistant.v2/Model/AssistantData.cs:31` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/CreateDocumentClassifier.cs:27` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 3) src/IBM.Watson.Assistant.v2/Model/Skill.cs:102— src/IBM.Watson.Assistant.v2/Model/Skill.cs:102-117 | src/IBM.Watson.Assistant.v2/Model/SkillImport.cs:102-117 | src/IBM.Watson.Discovery.v2/Model/CreateEnrichment.cs:109-125 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/Skill.cs` and `src/IBM.Watson.Assistant.v2/Model/SkillImport.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Assistant.v2/Model/Skill.cs:96` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/CreateEnrichment.cs:80` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Assistant.v1/Examples/IBM.Watson.Assistant.v1.Examples.csproj:5— src/IBM.Watson.Assistant.v1/Examples/IBM.Watson.Assistant.v1.Examples.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj:5— src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Assistant.v1/Test/Unit/IBM.Watson.Assistant.v1.UnitTests.csproj:5— src/IBM.Watson.Assistant.v1/Test/Unit/IBM.Watson.Assistant.v1.UnitTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Assistant.v2/Test/Integration/IBM.Watson.Assistant.v2.IntegrationTests.csproj:5— src/IBM.Watson.Assistant.v2/Test/Integration/IBM.Watson.Assistant.v2.IntegrationTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Assistant.v2/Test/Unit/IBM.Watson.Assistant.v2.UnitTests.csproj:5— src/IBM.Watson.Assistant.v2/Test/Unit/IBM.Watson.Assistant.v2.UnitTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Discovery.v1/Test/Integration/IBM.Watson.Discovery.v1.IntegrationTests.csproj:5— src/IBM.Watson.Discovery.v1/Test/Integration/IBM.Watson.Discovery.v1.IntegrationTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Discovery.v1/Test/Unit/IBM.Watson.Discovery.v1.UnitTests.csproj:5— src/IBM.Watson.Discovery.v1/Test/Unit/IBM.Watson.Discovery.v1.UnitTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Discovery.v2/Examples/IBM.Watson.Discovery.v2.Examples.csproj:5— src/IBM.Watson.Discovery.v2/Examples/IBM.Watson.Discovery.v2.Examples.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Discovery.v2/Test/Integration/IBM.Watson.Discovery.v2.IntegrationTests.csproj:5— src/IBM.Watson.Discovery.v2/Test/Integration/IBM.Watson.Discovery.v2.IntegrationTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.Discovery.v2/Test/Unit/IBM.Watson.Discovery.v2.UnitTests.csproj:5— src/IBM.Watson.Discovery.v2/Test/Unit/IBM.Watson.Discovery.v2.UnitTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 REDACTED:5— REDACTED declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.LanguageTranslator.v3/Examples/IBM.Watson.LanguageTranslator.v3.Examples.csproj:5— src/IBM.Watson.LanguageTranslator.v3/Examples/IBM.Watson.LanguageTranslator.v3.Examples.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.LanguageTranslator.v3/Test/Integration/IBM.Watson.LanguageTranslator.v3.IntegrationTests.csproj:5— src/IBM.Watson.LanguageTranslator.v3/Test/Integration/IBM.Watson.LanguageTranslator.v3.IntegrationTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.LanguageTranslator.v3/Test/Unit/IBM.Watson.LanguageTranslator.v3.UnitTests.csproj:5— src/IBM.Watson.LanguageTranslator.v3/Test/Unit/IBM.Watson.LanguageTranslator.v3.UnitTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/IBM.Watson.NLU.v1.IntegrationTests.csproj:5— src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/IBM.Watson.NLU.v1.IntegrationTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Unit/IBM.Watson.NaturalLanguageUnderstanding.v1.UnitTests.csproj:5— src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Unit/IBM.Watson.NaturalLanguageUnderstanding.v1.UnitTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.SpeechToText.v1/Test/Integration/IBM.Watson.SpeechToText.v1.IntegrationTests.csproj:5— src/IBM.Watson.SpeechToText.v1/Test/Integration/IBM.Watson.SpeechToText.v1.IntegrationTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.SpeechToText.v1/Test/Unit/IBM.Watson.SpeechToText.v1.UnitTests.csproj:5— src/IBM.Watson.SpeechToText.v1/Test/Unit/IBM.Watson.SpeechToText.v1.UnitTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.TextToSpeech.v1/Test/Integration/IBM.Watson.TextToSpeech.v1.IntegrationTests.csproj:5— src/IBM.Watson.TextToSpeech.v1/Test/Integration/IBM.Watson.TextToSpeech.v1.IntegrationTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET net7.0 src/IBM.Watson.TextToSpeech.v1/Test/Unit/IBM.Watson.TextToSpeech.v1.UnitTests.csproj:5— src/IBM.Watson.TextToSpeech.v1/Test/Unit/IBM.Watson.TextToSpeech.v1.UnitTests.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Test cannot fail: TestTokenization_Success src/IBM.Watson.Discovery.v1/Test/Integration/DiscoveryIntegrationTests.cs:1034— This test's act runs inside `catch (Exception)` at line 1118 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 5 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: TestDeleteTrainingQuery src/IBM.Watson.Discovery.v2/Test/Integration/DiscoveryIntegrationTests.cs:857— This test's act runs inside `catch (Exception)` at line 903 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: TestUpdateCategoriesModel src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/NaturalLanguageUnderstandingIntegrationTests.cs:387— This test's act runs inside `catch (Exception)` at line 453 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 12 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: TestGetCategoriesModel src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/NaturalLanguageUnderstandingIntegrationTests.cs:469— This test's act runs inside `catch (Exception)` at line 529 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 12 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: TestUpdateClassificationModel src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/NaturalLanguageUnderstandingIntegrationTests.cs:635— This test's act runs inside `catch (Exception)` at line 722 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 12 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: TestGetClassificationModel src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/NaturalLanguageUnderstandingIntegrationTests.cs:738— This test's act runs inside `catch (Exception)` at line 820 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 12 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: testAddCustomPrompts src/IBM.Watson.TextToSpeech.v1/Test/Integration/TextToSpeechServiceIntegrationTests.cs:295— This test's act runs inside `catch (Exception)` at line 326 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: testGetCustomPrompts src/IBM.Watson.TextToSpeech.v1/Test/Integration/TextToSpeechServiceIntegrationTests.cs:338— This test's act runs inside `catch (Exception)` at line 376 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: testDeleteCustomPrompts src/IBM.Watson.TextToSpeech.v1/Test/Integration/TextToSpeechServiceIntegrationTests.cs:388— This test's act runs inside `catch (Exception)` at line 426 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: testCreateSpeakerModel src/IBM.Watson.TextToSpeech.v1/Test/Integration/TextToSpeechServiceIntegrationTests.cs:438— This test's act runs inside `catch (Exception)` at line 456 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 1 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: testListSpeakerModel src/IBM.Watson.TextToSpeech.v1/Test/Integration/TextToSpeechServiceIntegrationTests.cs:468— This test's act runs inside `catch (Exception)` at line 494 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 3 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: testGetSpeakerModel src/IBM.Watson.TextToSpeech.v1/Test/Integration/TextToSpeechServiceIntegrationTests.cs:506— This test's act runs inside `catch (Exception)` at line 533 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
No assertions: ListModels_Success src/IBM.Watson.SpeechToText.v1/Test/Unit/SpeechToTextServiceGeneratedUnitTests.cs:91— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: RegisterCallback_Success src/IBM.Watson.SpeechToText.v1/Test/Unit/SpeechToTextServiceGeneratedUnitTests.cs:158— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: UnregisterCallback_Success src/IBM.Watson.SpeechToText.v1/Test/Unit/SpeechToTextServiceGeneratedUnitTests.cs:174— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: CheckJobs_Success src/IBM.Watson.SpeechToText.v1/Test/Unit/SpeechToTextServiceGeneratedUnitTests.cs:232— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ListLanguageModels_Success src/IBM.Watson.SpeechToText.v1/Test/Unit/SpeechToTextServiceGeneratedUnitTests.cs:315— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ListAcousticModels_Success src/IBM.Watson.SpeechToText.v1/Test/Unit/SpeechToTextServiceGeneratedUnitTests.cs:695— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: DeleteUserData_Success src/IBM.Watson.SpeechToText.v1/Test/Unit/SpeechToTextServiceGeneratedUnitTests.cs:866— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ListVoices_Success src/IBM.Watson.TextToSpeech.v1/Test/Unit/TextToSpeechServiceGeneratedUnitTests.cs:91— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: GetPronunciation_Success src/IBM.Watson.TextToSpeech.v1/Test/Unit/TextToSpeechServiceGeneratedUnitTests.cs:147— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ListVoiceModels_Success src/IBM.Watson.TextToSpeech.v1/Test/Unit/TextToSpeechServiceGeneratedUnitTests.cs:197— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: DeleteUserData_Success src/IBM.Watson.TextToSpeech.v1/Test/Unit/TextToSpeechServiceGeneratedUnitTests.cs:382— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D30 · Dependency Vulnerabilities· Medium CVE · ×11
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
P12 · CI test-gate honesty· Tests run only outside the merge gate · ×9
Tests run only outside the merge gate REDACTED:62— `dotnet test --no-build --verbosity normal src/IBM.Watson.LanguageTranslator.v3/Test/Integration` is the only CI command that runs 10 test(s) (e.g. LTServiceIntTestBasicAuthIamApikey.GetIdentifiableLanguages_Sucess_IamAsBasicAuth, LTServiceIntTestBasicAuthIamApikey.Identify_Sucess_IamAsBasicAuth), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate REDACTED:63— `dotnet test --no-build --verbosity normal src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration` is the only CI command that runs 20 test(s) (e.g. NaturalLanguageUnderstandingIntegrationTests.Analyze_Success, NaturalLanguageUnderstandingIntegrationTests.ListModels_Success), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate REDACTED:64— `dotnet test --no-build --verbosity normal src/IBM.Watson.SpeechToText.v1/Test/Integration` is the only CI command that runs 10 test(s) (e.g. SpeechToTextServiceIntegrationTest.TestModels_Success, SpeechToTextServiceIntegrationTest.TestCustomLanguageModels_Success), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate REDACTED:65— `dotnet test --no-build --verbosity normal src/IBM.Watson.TextToSpeech.v1/Test/Integration` is the only CI command that runs 13 test(s) (e.g. TextToSpeechServiceIntegrationTests.Voices_Success, TextToSpeechServiceIntegrationTests.Synthesize_Success), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate REDACTED:66— `dotnet test --no-build --verbosity normal src/IBM.Watson.Assistant.v1/Test/Integration` is the only CI command that runs 15 test(s) (e.g. AssistantServiceIntegrationTests.Message_Success, AssistantServiceIntegrationTests.TestCounterExamples_Success), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate REDACTED:67— `dotnet test --no-build --verbosity normal src/IBM.Watson.Assistant.v2/Test/Integration` is the only CI command that runs 11 test(s) (e.g. AssistantServiceIntegrationConfigTests.CreateDeleteSession_Success, AssistantServiceIntegrationConfigTests.Message_Success), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate REDACTED:68— `dotnet test --no-build --verbosity normal src/IBM.Watson.Discovery.v1/Test/Integration` is the only CI command that runs 15 test(s) (e.g. DiscoveryCpdIntegrationTests.TestAutocompletion, DiscoveryCpdIntegrationTests.TestSpellingSuggestions), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate REDACTED:69— `dotnet test --no-build --verbosity normal src/IBM.Watson.Discovery.v2/Test/Integration` is the only CI command that runs 16 test(s) (e.g. DiscoveryIntegrationTests.TestQueryPassagesPerDocument, DiscoveryIntegrationTests.TestQueryPassages), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate REDACTED:70— `dotnet test --no-build --verbosity normal src/IBM.Watson.IntegrationTests` is the only CI command that runs 17 test(s) (e.g. AdditionalPropertiesTest.TestRestrictedDynamicModel, AdditionalPropertiesTest.TestUnrestrictedDynamicModel), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
FileTooLong: IBM.Watson.Discovery.v1/DiscoveryService.cs src/IBM.Watson.Discovery.v1/DiscoveryService.cs— FileTooLong — 2117 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1617 over it, 4.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: IBM.Watson.Assistant.v1/AssistantService.cs src/IBM.Watson.Assistant.v1/AssistantService.cs— FileTooLong — 1917 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1417 over it, 3.83× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: IBM.Watson.Discovery.v2/DiscoveryService.cs src/IBM.Watson.Discovery.v2/DiscoveryService.cs— FileTooLong — 1678 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1178 over it, 3.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: IBM.Watson.SpeechToText.v1/SpeechToTextService.cs src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs— FileTooLong — 1462 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 962 over it, 2.92× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: IBM.Watson.Assistant.v2/AssistantService.cs src/IBM.Watson.Assistant.v2/AssistantService.cs— FileTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 262 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs— FileTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 262 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs— FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 17 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (18 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1257— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1257-1274 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2093-2110 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1257` it begins part-way through the construct above it, so those exact lines 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:1411— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1411-1428 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2250-2267 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1411` it begins part-way through the construct above it, so those exact lines 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:1822— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1822-1839 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2029-2046 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1822` it begins part-way through the construct above it, so those exact lines 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/IBM.Watson.Discovery.v2/Model/ModelEvaluationMacroAverage.cs:28— src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMacroAverage.cs:28-45 | src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMicroAverage.cs:28-45 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMacroAverage.cs` and `src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMicroAverage.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3692— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3692-3709 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1717-1734 — 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3692` it does not close everything it opens, so those exact lines 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/IBM.Watson.Discovery.v2/Model/QueryResponsePassage.cs:52— src/IBM.Watson.Discovery.v2/Model/QueryResponsePassage.cs:52-69 | src/IBM.Watson.Discovery.v2/Model/QueryResultPassage.cs:36-53 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/QueryResponsePassage.cs` and `src/IBM.Watson.Discovery.v2/Model/QueryResultPassage.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 4) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1285— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1285-1300 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1375-1390 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2121-2136 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2213-2228 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1285` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 4) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1501— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1501-1516 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1576-1591 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1701-1716 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1786-1801 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1501` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1783` calls `WithBodyContent` and `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1498` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 4) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1962— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1962-1977 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2179-2194 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1026-1041 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1277-1292 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1962` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `string metadata =` in one and `bool? xWatsonDiscoveryForce =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 4) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2680— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2680-2695 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3038-3053 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1753-1768 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1844-1859 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2680` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `List<string> similarFields =` in one and `long? offset =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 4) src/IBM.Watson.Discovery.v2/Model/TableBodyCells.cs:28— src/IBM.Watson.Discovery.v2/Model/TableBodyCells.cs:28-43 | src/IBM.Watson.Discovery.v2/Model/TableCellKey.cs:27-42 | src/IBM.Watson.Discovery.v2/Model/TableCellValues.cs:27-42 | src/IBM.Watson.Discovery.v2/Model/TableRowHeaders.cs:27-42 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/TableBodyCells.cs` and `src/IBM.Watson.Discovery.v2/Model/TableCellKey.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.Discovery.v2/Model/TableRowHeaders.cs:52` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/TableBodyCells.cs:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 4) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputOptionsElementValue.cs:28— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputOptionsElementValue.cs:28-49 | src/IBM.Watson.Assistant.v1/Model/DialogSuggestionValue.cs:31-46 | src/IBM.Watson.Assistant.v1/Model/MessageRequest.cs:27-44 | src/IBM.Watson.Assistant.v1/Model/MessageResponse.cs:27-42 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/MessageRequest.cs` and `src/IBM.Watson.Assistant.v1/Model/MessageResponse.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputOptionsElementValue.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 (5 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:627— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:627-631 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:803-807 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1005— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1005-1009 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1152-1156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2067— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2067-2071 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2283-2287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4678— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4678-4682 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4835-4839 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:5015— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:5015-5019 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:5078-5082 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs:43— src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs:43-47 | src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGeneric.cs:46-50 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs` and `src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGeneric.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1334— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1334-1355 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2172-2193 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1334` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/IBM.Watson.Assistant.v2/AssistantService.cs:510— src/IBM.Watson.Assistant.v2/AssistantService.cs:510-531 | src/IBM.Watson.Assistant.v2/AssistantService.cs:607-628 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) src/IBM.Watson.TextToSpeech.v1/Model/Prompt.cs:32— src/IBM.Watson.TextToSpeech.v1/Model/Prompt.cs:32-53 | src/IBM.Watson.TextToSpeech.v1/Model/SpeakerPrompt.cs:32-53 — before extracting anything, compare `src/IBM.Watson.TextToSpeech.v1/Model/Prompt.cs` and `src/IBM.Watson.TextToSpeech.v1/Model/SpeakerPrompt.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.TextToSpeech.v1/Model/Prompt.cs:58` calls `JsonProperty` and `src/IBM.Watson.TextToSpeech.v1/Model/SpeakerPrompt.cs:54` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 2) src/IBM.Watson.Assistant.v1/Model/DialogNodeAction.cs:60— src/IBM.Watson.Assistant.v1/Model/DialogNodeAction.cs:60-81 | src/IBM.Watson.Assistant.v2/Model/DialogNodeAction.cs:56-77 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeAction.cs` and `src/IBM.Watson.Assistant.v2/Model/DialogNodeAction.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) src/IBM.Watson.Discovery.v2/Model/ProjectDetails.cs:71— src/IBM.Watson.Discovery.v2/Model/ProjectDetails.cs:71-92 | src/IBM.Watson.Discovery.v2/Model/ProjectListDetails.cs:71-92 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/ProjectDetails.cs` and `src/IBM.Watson.Discovery.v2/Model/ProjectListDetails.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.Discovery.v2/Model/ProjectDetails.cs:96` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/ProjectListDetails.cs:93` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2763— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2763-2774 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1298-1309 — 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2763` it does not close everything it opens, so those exact lines 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/IBM.Watson.Assistant.v2/Model/ReleaseSkill.cs:51— src/IBM.Watson.Assistant.v2/Model/ReleaseSkill.cs:51-62 | src/IBM.Watson.Assistant.v2/Model/ReleaseSkillReference.cs:51-62 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/ReleaseSkill.cs` and `src/IBM.Watson.Assistant.v2/Model/ReleaseSkillReference.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) src/IBM.Watson.Discovery.v1/Model/QueryHistogramAggregationResult.cs:31— src/IBM.Watson.Discovery.v1/Model/QueryHistogramAggregationResult.cs:31-42 | src/IBM.Watson.Discovery.v1/Model/QueryTimesliceAggregationResult.cs:36-47 — before extracting anything, compare `src/IBM.Watson.Discovery.v1/Model/QueryHistogramAggregationResult.cs` and `src/IBM.Watson.Discovery.v1/Model/QueryTimesliceAggregationResult.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v1/Model/QueryTimesliceAggregationResult.cs:31` calls `JsonProperty` and `src/IBM.Watson.Discovery.v1/Model/QueryHistogramAggregationResult.cs:27` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) src/IBM.Watson.Discovery.v2/Model/QueryHistogramAggregationResult.cs:31— src/IBM.Watson.Discovery.v2/Model/QueryHistogramAggregationResult.cs:31-42 | src/IBM.Watson.Discovery.v2/Model/QueryTimesliceAggregationResult.cs:36-47 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/QueryHistogramAggregationResult.cs` and `src/IBM.Watson.Discovery.v2/Model/QueryTimesliceAggregationResult.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v2/Model/QueryTimesliceAggregationResult.cs:31` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/QueryHistogramAggregationResult.cs:27` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:618— src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:618-629 | src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:665-676 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:618` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
TooManyMethods: DiscoveryService src/IBM.Watson.Discovery.v1/DiscoveryService.cs— TooManyMethods — 2075 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DiscoveryService src/IBM.Watson.Discovery.v2/DiscoveryService.cs— TooManyMethods — 1640 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AssistantService src/IBM.Watson.Assistant.v1/AssistantService.cs— TooManyMethods — 1868 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SpeechToTextService src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs— TooManyMethods — 1083 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1248— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1248-1300 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1325-1390 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2084-2136 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2163-2228 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1464— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1464-1516 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1530-1591 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1664-1716 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1729-1801 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2575— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2575-2695 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2949-3053 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1696-1768 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1795-1859 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4129— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4129-4177 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4211-4259 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4292-4340 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4374-4422 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×4
Edited copy of a member (53 corresponding lines) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1872— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1872-1924 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1946-2007 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (53 corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:597— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:597-649 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:773-825 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (53 corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4648— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4648-4700 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4805-4857 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (53 corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4985— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4985-5037 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:5048-5100 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (17 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5794— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5794-5810 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2598-2614 — 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5794` it does not close everything it opens, so those exact lines 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/IBM.Watson.Assistant.v1/Model/BulkClassifyOutput.cs:26— src/IBM.Watson.Assistant.v1/Model/BulkClassifyOutput.cs:26-42 | src/IBM.Watson.Assistant.v2/Model/BulkClassifyOutput.cs:26-42 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/BulkClassifyOutput.cs` and `src/IBM.Watson.Assistant.v2/Model/BulkClassifyOutput.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/BulkClassifyOutput.cs:26` it does not close everything it opens, so those exact lines 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/IBM.Watson.Assistant.v1/Model/LogPagination.cs:26— src/IBM.Watson.Assistant.v1/Model/LogPagination.cs:26-42 | src/IBM.Watson.Assistant.v2/Model/LogPagination.cs:26-42 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/LogPagination.cs` and `src/IBM.Watson.Assistant.v2/Model/LogPagination.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/LogPagination.cs:26` it does not close everything it opens, so those exact lines 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/IBM.Watson.Discovery.v1/Model/QueryNoticesResult.cs:62— src/IBM.Watson.Discovery.v1/Model/QueryNoticesResult.cs:62-78 | src/IBM.Watson.Discovery.v1/Model/QueryResult.cs:32-48 — before extracting anything, compare `src/IBM.Watson.Discovery.v1/Model/QueryNoticesResult.cs` and `src/IBM.Watson.Discovery.v1/Model/QueryResult.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) src/IBM.Watson.Assistant.v1/AssistantService.cs:4704— src/IBM.Watson.Assistant.v1/AssistantService.cs:4704-4718 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4066-4080 — 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/IBM.Watson.Assistant.v1/AssistantService.cs:4704` it does not close everything it opens, so those exact lines 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/IBM.Watson.Assistant.v1/Model/DialogNodeVisitedDetails.cs:27— src/IBM.Watson.Assistant.v1/Model/DialogNodeVisitedDetails.cs:27-41 | src/IBM.Watson.Assistant.v2/Model/DialogNodeVisited.cs:28-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) src/IBM.Watson.Discovery.v1/Model/NluEnrichmentEntities.cs:27— src/IBM.Watson.Discovery.v1/Model/NluEnrichmentEntities.cs:27-41 | src/IBM.Watson.Discovery.v1/Model/NluEnrichmentKeywords.cs:27-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) src/IBM.Watson.Discovery.v1/Model/QueryNoticesResponse.cs:38— src/IBM.Watson.Discovery.v1/Model/QueryNoticesResponse.cs:38-52 | src/IBM.Watson.Discovery.v1/Model/QueryResponse.cs:38-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
ClassTooLong: AssistantService src/IBM.Watson.Assistant.v2/AssistantService.cs— ClassTooLong — 738 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 338 over it, 1.85× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TextToSpeechService src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs— ClassTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 158 over it, 1.40× the bar. 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: NaturalLanguageUnderstandingService src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs— ClassTooLong — 488 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 88 over it, 1.22× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (38 lines × 2) src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEvent.cs:84— src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEvent.cs:84-121 | src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionVisited.cs:50-87 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEvent.cs` and `src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionVisited.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEvent.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (38 lines × 2) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeOption.cs:51— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeOption.cs:51-88 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeOption.cs:51-89 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeOption.cs` and `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeOption.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeOption.cs:51` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (38 lines × 2) src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryTopicAggregation.cs:36— src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryTopicAggregation.cs:36-73 | src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryTrendAggregation.cs:35-72 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryTopicAggregation.cs` and `src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryTrendAggregation.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryTopicAggregation.cs:36` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21–22 lines × 2) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGeneric.cs:233— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGeneric.cs:233-254 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs:177-197 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs:176` calls `JsonProperty` and `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGeneric.cs:233` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21–22 lines × 2) src/IBM.Watson.Discovery.v1/Model/QueryResponse.cs:26— src/IBM.Watson.Discovery.v1/Model/QueryResponse.cs:26-46 | src/IBM.Watson.Discovery.v2/Model/QueryResponse.cs:26-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/Model/QueryResponse.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–22 lines × 2) src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs:28— src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs:28-49 | src/IBM.Watson.Discovery.v2/Model/TableHeaders.cs:27-47 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs` and `src/IBM.Watson.Discovery.v2/Model/TableHeaders.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs:54` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/TableHeaders.cs:48` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:864— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:864-883 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1074-1093 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2260— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2260-2279 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1369-1388 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2260` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs:33— src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs:33-61 | src/IBM.Watson.Assistant.v2/Model/LogMessageSourceStep.cs:33-52 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs` and `src/IBM.Watson.Assistant.v2/Model/LogMessageSourceStep.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs:33` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) src/IBM.Watson.Assistant.v1/AssistantService.cs:3438— src/IBM.Watson.Assistant.v1/AssistantService.cs:3438-3451 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3928-3941 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Assistant.v1/AssistantService.cs:3438` it begins part-way through the construct above it, so those exact lines 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:2050— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2050-2063 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:916-929 — 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:2050` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2688— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2688-2701 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1234-1247 — 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2688` it does not close everything it opens, so those exact lines 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:1760— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1760-1768 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:462-470 — 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:1760` it does not close everything it opens, so those exact lines 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:402— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:402-410 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:397-405 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) src/IBM.Watson.Assistant.v1/AssistantService.cs:35— src/IBM.Watson.Assistant.v1/AssistantService.cs:35-43 | src/IBM.Watson.Assistant.v2/AssistantService.cs:36-44 — `src/IBM.Watson.Assistant.v1/AssistantService.cs` and `src/IBM.Watson.Assistant.v2/AssistantService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 104 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:223— src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:223-236 | src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:769-783 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) REDACTED:547— REDACTED:547-560 | src/IBM.Watson.TextToSpeech.v1/Examples/ServiceExample.cs:309-322 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) REDACTED:531— REDACTED:531-544 | src/IBM.Watson.TextToSpeech.v1/Examples/ServiceExample.cs:293-306 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Prerelease dependency: MSTest.TestAdapter — MSTest.TestAdapter resolves to 1.1.8-rc, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: MSTest.TestFramework — MSTest.TestFramework resolves to 1.0.8-rc, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) src/IBM.Watson.Assistant.v1/AssistantService.cs:1768— src/IBM.Watson.Assistant.v1/AssistantService.cs:1768-1832 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2204-2260 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3712-3784 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4273-4329 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1019-1075 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1404-1460 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1855-1903 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) src/IBM.Watson.Assistant.v2/AssistantService.cs:75— src/IBM.Watson.Assistant.v2/AssistantService.cs:75-128 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1203-1256 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2979-3048 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3782-3855 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2677-2734 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4582-4635 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1227-1276 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) src/IBM.Watson.Assistant.v1/AssistantService.cs:373— src/IBM.Watson.Assistant.v1/AssistantService.cs:373-462 | src/IBM.Watson.Assistant.v1/AssistantService.cs:480-536 | src/IBM.Watson.Assistant.v1/AssistantService.cs:596-697 | src/IBM.Watson.Assistant.v1/AssistantService.cs:782-867 | src/IBM.Watson.Assistant.v1/AssistantService.cs:906-1003 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1024-1080 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/IBM.Watson.Assistant.v2/AssistantService.cs:1019— src/IBM.Watson.Assistant.v2/AssistantService.cs:1019-1075 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1107-1180 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1563-1632 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:78-135 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:193-237 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:252-313 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1906— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1906-1977 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2115-2194 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:965-1041 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1208-1292 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3967-4038 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3216— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3216-3285 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3359-3419 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2470-2539 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2551-2603 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2619-2696 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copies of one member (3 members, 70+ corresponding lines) · ×2
Edited copies of one member (3 members, 70+ corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1040— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1040-1113 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3749-3830 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4725-4794 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 70 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 70+ corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:1232— src/IBM.Watson.Assistant.v1/AssistantService.cs:1232-1301 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1407-1484 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:647-716 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 70 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (54 corresponding lines) · ×2
Edited copy of a member (54 corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:192— src/IBM.Watson.Assistant.v1/AssistantService.cs:192-245 | src/IBM.Watson.Assistant.v2/AssistantService.cs:661-718 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (54 corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4921— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4921-4974 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:252-305 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 61+ corresponding lines) · ×2
Edited copies of one member (4 members, 61+ corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:2635— src/IBM.Watson.Assistant.v1/AssistantService.cs:2635-2695 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2891-2951 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3204-3272 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3497-3577 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 61 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 61+ corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2029— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2029-2089 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2245-2305 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1097-1157 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1354-1419 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 61 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 53+ corresponding lines) · ×2
Edited copies of one member (3 members, 53+ corresponding lines) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3286— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3286-3338 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3520-3572 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3707-3767 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 53 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 53+ corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:975— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:975-1027 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1122-1174 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:580-632 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 53 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×2
Edited copy of a member (45 corresponding lines) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3114— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3114-3162 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5002-5046 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (45 corresponding lines) src/IBM.Watson.Assistant.v2/AssistantService.cs:1655— src/IBM.Watson.Assistant.v2/AssistantService.cs:1655-1707 | src/IBM.Watson.Assistant.v2/AssistantService.cs:2030-2074 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (87 lines × 2) src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:799— src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:799-885 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:1092-1178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (87 lines × 2) src/IBM.Watson.Assistant.v2/Model/Skill.cs:96— src/IBM.Watson.Assistant.v2/Model/Skill.cs:96-182 | src/IBM.Watson.Assistant.v2/Model/SkillImport.cs:96-182 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/Skill.cs` and `src/IBM.Watson.Assistant.v2/Model/SkillImport.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (57 lines × 4) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:967— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:967-1023 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2068-2124 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5487-5543 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5565-5621 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (57 lines × 4) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:35— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:35-92 | src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo.cs:35-91 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:35-92 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:35-91 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs` and `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (46 lines × 2) src/IBM.Watson.Assistant.v1/Model/RuntimeEntityInterpretation.cs:30— src/IBM.Watson.Assistant.v1/Model/RuntimeEntityInterpretation.cs:30-75 | src/IBM.Watson.Assistant.v2/Model/RuntimeEntityInterpretation.cs:30-75 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/RuntimeEntityInterpretation.cs` and `src/IBM.Watson.Assistant.v2/Model/RuntimeEntityInterpretation.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/RuntimeEntityInterpretation.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (46 lines × 2) src/IBM.Watson.Discovery.v1/Model/Field.cs:30— src/IBM.Watson.Discovery.v1/Model/Field.cs:30-75 | src/IBM.Watson.Discovery.v2/Model/Field.cs:30-75 — before extracting anything, compare `src/IBM.Watson.Discovery.v1/Model/Field.cs` and `src/IBM.Watson.Discovery.v2/Model/Field.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/Model/Field.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (45 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3865— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3865-3909 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1652-1696 — 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3865` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `words` to `List<CustomWord>` in one and `List<Word>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (45 lines × 2) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent.cs:35— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent.cs:35-79 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeConnectToAgent.cs:35-100 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent.cs` and `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeConnectToAgent.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3237— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3237-3247 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3408-3418 — both copies are in the same file, so extract the block into 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/IBM.Watson.Discovery.v2/DiscoveryService.cs:3020— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3020-3030 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3827-3837 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (28 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1359— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1359-1386 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2197-2224 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1359` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (28 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3627— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3627-3654 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3803-3830 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:3627` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (25 lines × 3) src/IBM.Watson.Discovery.v1/Model/QueryTermAggregationResult.cs:28— src/IBM.Watson.Discovery.v1/Model/QueryTermAggregationResult.cs:28-52 | src/IBM.Watson.Discovery.v2/Model/QueryGroupByAggregationResult.cs:28-52 | src/IBM.Watson.Discovery.v2/Model/QueryTermAggregationResult.cs:28-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (25 lines × 3) src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryHistogramAggregation.cs:35— src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryHistogramAggregation.cs:35-59 | src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryTermAggregation.cs:34-63 | src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryTimesliceAggregation.cs:34-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v2/Model/QueryAggregationQueryHistogramAggregation.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 2) src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs:40— src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs:40-64 | src/IBM.Watson.Discovery.v2/Model/TableRowHeaders.cs:38-62 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs` and `src/IBM.Watson.Discovery.v2/Model/TableRowHeaders.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs:38` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/TableRowHeaders.cs:37` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (25 lines × 2) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer.cs:37— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer.cs:37-61 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeChannelTransfer.cs:37-62 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer.cs` and `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeChannelTransfer.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer.cs:37` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 2) src/IBM.Watson.Discovery.v1/Model/QueryTimesliceAggregationResult.cs:26— src/IBM.Watson.Discovery.v1/Model/QueryTimesliceAggregationResult.cs:26-46 | src/IBM.Watson.Discovery.v2/Model/QueryTimesliceAggregationResult.cs:26-46 — before extracting anything, compare `src/IBM.Watson.Discovery.v1/Model/QueryTimesliceAggregationResult.cs` and `src/IBM.Watson.Discovery.v2/Model/QueryTimesliceAggregationResult.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/Model/QueryTimesliceAggregationResult.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined.cs:35— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined.cs:35-55 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeUserDefined.cs:35-55 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined.cs` and `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeUserDefined.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 6) src/IBM.Watson.Assistant.v1/AssistantService.cs:447— src/IBM.Watson.Assistant.v1/AssistantService.cs:447-462 | src/IBM.Watson.Assistant.v1/AssistantService.cs:521-536 | src/IBM.Watson.Assistant.v1/AssistantService.cs:682-697 | src/IBM.Watson.Assistant.v1/AssistantService.cs:852-867 | src/IBM.Watson.Assistant.v1/AssistantService.cs:988-1003 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1065-1080 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:447` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `bool? includeAudit =` in one and `string sort =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 6) src/IBM.Watson.Assistant.v2/AssistantService.cs:1060— src/IBM.Watson.Assistant.v2/AssistantService.cs:1060-1075 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1165-1180 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1617-1632 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:120-135 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:222-237 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:298-313 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v2/AssistantService.cs:1060` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `bool? includeAudit =` in one and `List<EnvironmentSkill> skillReferences =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 5) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3270— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3270-3285 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3404-3419 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2524-2539 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2588-2603 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2681-2696 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3270` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `List<TrainingExample> examples =` in one and `string filter =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 5) src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionFinished.cs:86— src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionFinished.cs:86-110 | src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionVisited.cs:97-122 | src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventHandlerVisited.cs:33-48 | src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventStepAnswered.cs:53-78 | src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventStepVisited.cs:53-77 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionFinished.cs` and `src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventHandlerVisited.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionFinished.cs:86` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 3) src/IBM.Watson.Discovery.v1/Model/QueryPassages.cs:42— src/IBM.Watson.Discovery.v1/Model/QueryPassages.cs:42-56 | src/IBM.Watson.Discovery.v2/Model/QueryResponsePassage.cs:49-63 | src/IBM.Watson.Discovery.v2/Model/QueryResultPassage.cs:33-47 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/QueryResponsePassage.cs` and `src/IBM.Watson.Discovery.v2/Model/QueryResultPassage.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.Discovery.v2/Model/QueryResultPassage.cs:52` calls `JsonProperty` and `src/IBM.Watson.Discovery.v1/Model/QueryPassages.cs:57` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 3) src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMacroAverage.cs:31— src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMacroAverage.cs:31-45 | src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMicroAverage.cs:31-45 | src/IBM.Watson.Discovery.v2/Model/PerClassModelEvaluation.cs:35-49 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMacroAverage.cs` and `src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMicroAverage.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v2/Model/PerClassModelEvaluation.cs:30` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/ModelEvaluationMacroAverage.cs:27` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4944— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4944-4956 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:275-287 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:1060— src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:1060-1072 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:559-571 — 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/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:1060` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3456— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3456-3465 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3700-3709 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:3456` it begins part-way through the construct above it, so those exact lines 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:3615— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3615-3624 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3795-3804 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:3615` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:2164— src/IBM.Watson.Assistant.v1/AssistantService.cs:2164-2172 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2316-2324 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:548-556 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:159— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:159-167 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:562-570 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:940-948 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) src/IBM.Watson.Assistant.v2/AssistantService.cs:101— src/IBM.Watson.Assistant.v2/AssistantService.cs:101-110 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3021-3030 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3828-3837 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:1276— src/IBM.Watson.Assistant.v1/AssistantService.cs:1276-1285 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1459-1468 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3260-3269 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:1276` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `bool? includeAudit =` in one and `List<TrainingExample> examples =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:936— src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:936-948 | src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:978-990 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) REDACTED:814— REDACTED:814-826 | src/IBM.Watson.TextToSpeech.v1/Examples/ServiceExample.cs:327-339 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
AX2 · Stateful singletons· Process-global static state · ×1
Process-global static state: Common REDACTED:25— `Common` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (os, osVersion, frameworkDescription; e.g. `os` at line 54). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
SpeechToTextService.CreateJob (cyclomatic 36) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1884— SpeechToTextService.CreateJob has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SpeechToTextService.Recognize (cyclomatic 30) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:807— SpeechToTextService.Recognize has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.Query (cyclomatic 29) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2375— DiscoveryService.Query has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.QueryNotices (cyclomatic 29) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2574— DiscoveryService.QueryNotices has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.FederatedQuery (cyclomatic 29) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2761— DiscoveryService.FederatedQuery has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.CreateDialogNode (cyclomatic 28) src/IBM.Watson.Assistant.v1/AssistantService.cs:4126— AssistantService.CreateDialogNode has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateDialogNode (cyclomatic 28) src/IBM.Watson.Assistant.v1/AssistantService.cs:4387— AssistantService.UpdateDialogNode has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.FederatedQueryNotices (cyclomatic 26) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2948— DiscoveryService.FederatedQueryNotices has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateWorkspace (cyclomatic 24) src/IBM.Watson.Assistant.v1/AssistantService.cs:595— AssistantService.UpdateWorkspace has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateWorkspaceAsync (cyclomatic 23) src/IBM.Watson.Assistant.v1/AssistantService.cs:905— AssistantService.UpdateWorkspaceAsync has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.Query (cyclomatic 23) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1477— DiscoveryService.Query has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.CreateWorkspace (cyclomatic 22) src/IBM.Watson.Assistant.v1/AssistantService.cs:372— AssistantService.CreateWorkspace has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.CreateWorkspaceAsync (cyclomatic 21) src/IBM.Watson.Assistant.v1/AssistantService.cs:781— AssistantService.CreateWorkspaceAsync has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateValue (cyclomatic 17) src/IBM.Watson.Assistant.v1/AssistantService.cs:3311— AssistantService.UpdateValue has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.CreateDocumentClassifierModel (cyclomatic 17) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3604— DiscoveryService.CreateDocumentClassifierModel has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NaturalLanguageUnderstandingService.UpdateClassificationsModel (cyclomatic 17) src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:1022— NaturalLanguageUnderstandingService.UpdateClassificationsModel has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.Message (cyclomatic 16) src/IBM.Watson.Assistant.v1/AssistantService.cs:96— AssistantService.Message has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.CreateValue (cyclomatic 16) src/IBM.Watson.Assistant.v1/AssistantService.cs:3101— AssistantService.CreateValue has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.UpdateConfiguration (cyclomatic 16) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:673— DiscoveryService.UpdateConfiguration has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NaturalLanguageUnderstandingService.Analyze (cyclomatic 16) src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:111— NaturalLanguageUnderstandingService.Analyze has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (NaturalLanguageUnderstandingService.CreateClassificationsModel) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
NaturalLanguageUnderstandingService.UpdateCategoriesModel (cyclomatic 16) src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:559— NaturalLanguageUnderstandingService.UpdateCategoriesModel has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NaturalLanguageUnderstandingService.CreateClassificationsModel (cyclomatic 16) src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:768— NaturalLanguageUnderstandingService.CreateClassificationsModel has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (NaturalLanguageUnderstandingService.Analyze) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DeadPreprocessorBranch src/IBM.Watson.Assistant.v1/Test/Integration/AssistantServiceIntegrationTests.cs:69— #if DELETE_DOTNET_WORKSPACES — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
TodoComment src/IBM.Watson.LanguageTranslator.v3/Test/Unit/LanguageTranslatorServiceGeneratedUnitTests.cs:171— // TODO: FIX UNIT TEST — 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.
SpeechToTextService.CreateJob (cognitive 35) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1884— SpeechToTextService.CreateJob has cognitive complexity 35 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.Query (cognitive 31) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2375— DiscoveryService.Query has cognitive complexity 31 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.QueryNotices (cognitive 30) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2574— DiscoveryService.QueryNotices has cognitive complexity 30 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.FederatedQuery (cognitive 30) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2761— DiscoveryService.FederatedQuery has cognitive complexity 30 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateDialogNode (cognitive 29) src/IBM.Watson.Assistant.v1/AssistantService.cs:4387— AssistantService.UpdateDialogNode has cognitive complexity 29 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SpeechToTextService.Recognize (cognitive 29) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:807— SpeechToTextService.Recognize has cognitive complexity 29 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.CreateDialogNode (cognitive 28) src/IBM.Watson.Assistant.v1/AssistantService.cs:4126— AssistantService.CreateDialogNode has cognitive complexity 28 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.FederatedQueryNotices (cognitive 26) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2948— DiscoveryService.FederatedQueryNotices has cognitive complexity 26 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateWorkspace (cognitive 24) src/IBM.Watson.Assistant.v1/AssistantService.cs:595— AssistantService.UpdateWorkspace has cognitive complexity 24 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateWorkspaceAsync (cognitive 23) src/IBM.Watson.Assistant.v1/AssistantService.cs:905— AssistantService.UpdateWorkspaceAsync has cognitive complexity 23 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.Query (cognitive 23) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1477— DiscoveryService.Query has cognitive complexity 23 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.CreateWorkspace (cognitive 21) src/IBM.Watson.Assistant.v1/AssistantService.cs:372— AssistantService.CreateWorkspace has cognitive complexity 21 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.CreateWorkspaceAsync (cognitive 20) src/IBM.Watson.Assistant.v1/AssistantService.cs:781— AssistantService.CreateWorkspaceAsync has cognitive complexity 20 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateValue (cognitive 19) src/IBM.Watson.Assistant.v1/AssistantService.cs:3311— AssistantService.UpdateValue has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.CreateDocumentClassifierModel (cognitive 18) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3604— DiscoveryService.CreateDocumentClassifierModel has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.CreateValue (cognitive 17) src/IBM.Watson.Assistant.v1/AssistantService.cs:3101— AssistantService.CreateValue has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DiscoveryService.UpdateConfiguration (cognitive 17) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:673— DiscoveryService.UpdateConfiguration has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NaturalLanguageUnderstandingService.UpdateClassificationsModel (cognitive 17) src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:1022— NaturalLanguageUnderstandingService.UpdateClassificationsModel has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.Message (cognitive 16) src/IBM.Watson.Assistant.v1/AssistantService.cs:96— AssistantService.Message has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssistantService.UpdateEntity (cognitive 16) src/IBM.Watson.Assistant.v1/AssistantService.cs:2726— AssistantService.UpdateEntity has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NaturalLanguageUnderstandingService.UpdateCategoriesModel (cognitive 16) src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:559— NaturalLanguageUnderstandingService.UpdateCategoriesModel has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D4 · Code Duplication· Members sharing a duplicated core (57 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (57 members, 50+ identical tokens) src/IBM.Watson.Assistant.v1/AssistantService.cs:707— src/IBM.Watson.Assistant.v1/AssistantService.cs:707-751 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1495-1547 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1943-2003 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2354-2406 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2823-2875 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3417-3477 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3899-3967 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4536-4588 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4768-4812 | src/IBM.Watson.Assistant.v2/AssistantService.cs:249-293 | src/IBM.Watson.Assistant.v2/AssistantService.cs:392-444 | src/IBM.Watson.Assistant.v2/AssistantService.cs:830-874 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1483-1535 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1402-1453 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1602-1653 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1813-1864 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3296-3347 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3431-3490 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3667-3734 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3925-3968 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:319-362 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:729-780 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2020-2071 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2241-2292 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2411-2454 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2708-2759 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3062-3113 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3457-3508 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3868-3927 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:4092-4135 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:965-1008 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1425-1460 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2586-2621 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2991-3027 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3214-3250 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3287-3323 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3458-3522 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3610-3654 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3864-3913 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3993-4054 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4140-4184 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4315-4382 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4498-4542 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4892-4928 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5069-5105 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5153-5197 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5392-5460 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5728-5772 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5793-5828 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1457-1510 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1578-1613 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1651-1700 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1795-1855 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1932-1975 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2279-2322 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2542-2577 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2597-2632 — These 57 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 57 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 57 times.
D4 · Code Duplication· Edited copy of a member (134 corresponding lines) · ×1
Edited copy of a member (134 corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:4127— src/IBM.Watson.Assistant.v1/AssistantService.cs:4127-4260 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4388-4525 — These two members are one piece of code written twice and then edited apart: 134 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 110+ corresponding lines) · ×1
Edited copies of one member (3 members, 110+ corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2376— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2376-2518 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2762-2900 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1478-1587 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 110 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 78+ corresponding lines) · ×1
Edited copies of one member (6 members, 78+ corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:2542— src/IBM.Watson.Assistant.v1/AssistantService.cs:2542-2619 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2727-2812 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1742-1819 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:452-529 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:674-759 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3605-3694 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 78 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 78+ corresponding lines) · ×1
Edited copies of one member (3 members, 78+ corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:3102— src/IBM.Watson.Assistant.v1/AssistantService.cs:3102-3187 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3312-3405 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3620-3697 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 78 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (70 corresponding lines) · ×1
Edited copy of a member (70 corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:838— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:838-907 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:499-568 — These two members are one piece of code written twice and then edited apart: 70 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 68+ corresponding lines) · ×1
Edited copies of one member (4 members, 68+ corresponding lines) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2834— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2834-2901 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3194-3274 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3361-3445 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2125-2196 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 68 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 62+ corresponding lines) · ×1
Edited copies of one member (4 members, 62+ corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:1681— src/IBM.Watson.Assistant.v1/AssistantService.cs:1681-1754 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1854-1931 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2129-2190 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2277-2342 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 62 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3502— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3502-3562 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3843-3911 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 54+ corresponding lines) · ×1
Edited copies of one member (4 members, 54+ corresponding lines) src/IBM.Watson.Assistant.v2/AssistantService.cs:317— src/IBM.Watson.Assistant.v2/AssistantService.cs:317-370 | src/IBM.Watson.Assistant.v2/AssistantService.cs:480-549 | src/IBM.Watson.Assistant.v2/AssistantService.cs:585-646 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1938-2007 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 54 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 57+ corresponding lines) · ×1
Edited copies of one member (7 members, 57+ corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:262— src/IBM.Watson.Assistant.v1/AssistantService.cs:262-318 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1566-1638 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2022-2086 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3985-4049 | src/IBM.Watson.Assistant.v2/AssistantService.cs:148-204 | src/IBM.Watson.Assistant.v2/AssistantService.cs:904-968 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1288-1352 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 57 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (58 corresponding lines) · ×1
Edited copy of a member (58 corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3979— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3979-4036 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:124-185 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 57+ corresponding lines) · ×1
Edited copies of one member (4 members, 57+ corresponding lines) src/IBM.Watson.Assistant.v1/AssistantService.cs:4611— src/IBM.Watson.Assistant.v1/AssistantService.cs:4611-4671 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4693-4749 | src/IBM.Watson.Assistant.v2/AssistantService.cs:751-811 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4059-4115 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 57 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 49+ corresponding lines) · ×1
Edited copies of one member (3 members, 49+ corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:376— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:376-428 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:375-423 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1605-1669 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 49 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 41+ corresponding lines) · ×1
Edited copies of one member (3 members, 41+ corresponding lines) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:145— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:145-185 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:540-588 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:918-966 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3691— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3691-3735 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1716-1752 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 37+ corresponding lines) · ×1
Edited copies of one member (3 members, 37+ corresponding lines) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4836— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4836-4872 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5218-5254 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5658-5702 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 37+ corresponding lines) · ×1
Edited copies of one member (5 members, 37+ corresponding lines) src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1527— src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1527-1563 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1872-1916 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1993-2029 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2214-2258 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2484-2520 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 37+ corresponding lines) · ×1
Edited copies of one member (6 members, 37+ corresponding lines) src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:73— src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:73-109 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:205-241 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:530-574 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:586-630 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:638-674 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:911-955 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 37+ corresponding lines) · ×1
Edited copies of one member (8 members, 37+ corresponding lines) src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:207— src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:207-243 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:253-297 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:449-485 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:495-539 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:703-747 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:909-945 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:955-999 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:1173-1217 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 33+ corresponding lines) · ×1
Edited copies of one member (3 members, 33+ corresponding lines) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2760— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2760-2792 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4661-4693 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1295-1327 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:76— src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:76-104 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2336-2364 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (220 lines × 3) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:224— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:224-443 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1105-1324 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2206-2425 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (190 lines × 3) src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:181— src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:181-370 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:655-844 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:986-1175 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.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 (144 lines × 2) src/IBM.Watson.Assistant.v1/Model/RuntimeEntityInterpretation.cs:83— src/IBM.Watson.Assistant.v1/Model/RuntimeEntityInterpretation.cs:83-226 | src/IBM.Watson.Assistant.v2/Model/RuntimeEntityInterpretation.cs:83-226 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/RuntimeEntityInterpretation.cs` and `src/IBM.Watson.Assistant.v2/Model/RuntimeEntityInterpretation.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (106 lines × 2) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2808— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2808-2913 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4709-4814 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2808` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (70 lines × 2) src/IBM.Watson.TextToSpeech.v1/Model/Translation.cs:34— src/IBM.Watson.TextToSpeech.v1/Model/Translation.cs:34-103 | src/IBM.Watson.TextToSpeech.v1/Model/Word.cs:34-103 — before extracting anything, compare `src/IBM.Watson.TextToSpeech.v1/Model/Translation.cs` and `src/IBM.Watson.TextToSpeech.v1/Model/Word.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.TextToSpeech.v1/Model/Translation.cs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (67 lines × 2) src/IBM.Watson.NaturalLanguageUnderstanding.v1/Model/CategoriesModel.cs:65— src/IBM.Watson.NaturalLanguageUnderstanding.v1/Model/CategoriesModel.cs:65-131 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/Model/ClassificationsModel.cs:65-131 — before extracting anything, compare `src/IBM.Watson.NaturalLanguageUnderstanding.v1/Model/CategoriesModel.cs` and `src/IBM.Watson.NaturalLanguageUnderstanding.v1/Model/ClassificationsModel.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (64–66 lines × 3) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGeneric.cs:155— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGeneric.cs:155-220 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs:102-165 | src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGeneric.cs:108-171 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs` and `src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGeneric.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGeneric.cs:149` calls `JsonProperty` and `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs:97` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (52–53 lines × 2) src/IBM.Watson.Assistant.v1/Model/RuntimeEntity.cs:26— src/IBM.Watson.Assistant.v1/Model/RuntimeEntity.cs:26-77 | src/IBM.Watson.Assistant.v2/Model/RuntimeEntity.cs:26-78 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/RuntimeEntity.cs` and `src/IBM.Watson.Assistant.v2/Model/RuntimeEntity.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/RuntimeEntity.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.Assistant.v2/Model/RuntimeEntity.cs:85` calls `JsonProperty` and `src/IBM.Watson.Assistant.v1/Model/RuntimeEntity.cs:78` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (47 lines × 3) src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:160— src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:160-206 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1041-1087 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2142-2188 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (45–47 lines × 2) src/IBM.Watson.Assistant.v1/Model/MessageRequest.cs:31— src/IBM.Watson.Assistant.v1/Model/MessageRequest.cs:31-77 | src/IBM.Watson.Assistant.v1/Model/MessageResponse.cs:31-75 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/MessageRequest.cs` and `src/IBM.Watson.Assistant.v1/Model/MessageResponse.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (42 lines × 2) src/IBM.Watson.Assistant.v2/Model/MessageInput.cs:58— src/IBM.Watson.Assistant.v2/Model/MessageInput.cs:58-99 | src/IBM.Watson.Assistant.v2/Model/MessageInputStateless.cs:58-99 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/MessageInput.cs` and `src/IBM.Watson.Assistant.v2/Model/MessageInputStateless.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (33–42 lines × 2) src/IBM.Watson.SpeechToText.v1/Model/AcousticModel.cs:80— src/IBM.Watson.SpeechToText.v1/Model/AcousticModel.cs:80-112 | src/IBM.Watson.SpeechToText.v1/Model/LanguageModel.cs:80-121 — before extracting anything, compare `src/IBM.Watson.SpeechToText.v1/Model/AcousticModel.cs` and `src/IBM.Watson.SpeechToText.v1/Model/LanguageModel.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (39 lines × 2) src/IBM.Watson.SpeechToText.v1/Model/AcousticModel.cs:107— src/IBM.Watson.SpeechToText.v1/Model/AcousticModel.cs:107-145 | src/IBM.Watson.SpeechToText.v1/Model/LanguageModel.cs:123-161 — before extracting anything, compare `src/IBM.Watson.SpeechToText.v1/Model/AcousticModel.cs` and `src/IBM.Watson.SpeechToText.v1/Model/LanguageModel.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.SpeechToText.v1/Model/LanguageModel.cs:169` calls `JsonProperty` and `src/IBM.Watson.SpeechToText.v1/Model/AcousticModel.cs:148` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (35 lines × 4) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4143— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4143-4177 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4225-4259 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4306-4340 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4388-4422 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4143` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (33 lines × 2) src/IBM.Watson.Assistant.v1/Model/Pagination.cs:26— src/IBM.Watson.Assistant.v1/Model/Pagination.cs:26-58 | src/IBM.Watson.Assistant.v2/Model/Pagination.cs:26-58 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/Pagination.cs` and `src/IBM.Watson.Assistant.v2/Model/Pagination.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/Pagination.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (32 lines × 2) src/IBM.Watson.Assistant.v1/AssistantService.cs:214— src/IBM.Watson.Assistant.v1/AssistantService.cs:214-245 | src/IBM.Watson.Assistant.v2/AssistantService.cs:687-718 — `src/IBM.Watson.Assistant.v1/AssistantService.cs` and `src/IBM.Watson.Assistant.v2/AssistantService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 104 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:214` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (31 lines × 2) src/IBM.Watson.Assistant.v1/Model/CreateValue.cs:58— src/IBM.Watson.Assistant.v1/Model/CreateValue.cs:58-88 | src/IBM.Watson.Assistant.v1/Model/Value.cs:58-88 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/CreateValue.cs` and `src/IBM.Watson.Assistant.v1/Model/Value.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 2) src/IBM.Watson.Assistant.v1/Model/CreateEntity.cs:37— src/IBM.Watson.Assistant.v1/Model/CreateEntity.cs:37-65 | src/IBM.Watson.Assistant.v1/Model/Entity.cs:37-65 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/CreateEntity.cs` and `src/IBM.Watson.Assistant.v1/Model/Entity.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (29–30 lines × 2) src/IBM.Watson.Discovery.v1/Model/Notice.cs:48— src/IBM.Watson.Discovery.v1/Model/Notice.cs:48-76 | src/IBM.Watson.Discovery.v2/Model/Notice.cs:48-77 — before extracting anything, compare `src/IBM.Watson.Discovery.v1/Model/Notice.cs` and `src/IBM.Watson.Discovery.v2/Model/Notice.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (25–28 lines × 2) src/IBM.Watson.Discovery.v2/Model/CollectionDetails.cs:37— src/IBM.Watson.Discovery.v2/Model/CollectionDetails.cs:37-64 | src/IBM.Watson.Discovery.v2/Model/DocumentClassifier.cs:37-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (22 lines × 5) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1929— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1929-1950 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2146-2167 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:988-1009 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1239-1260 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3990-4011 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1929` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `string metadata =` in one and `bool? xWatsonDiscoveryForce =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (24 lines × 2) src/IBM.Watson.Discovery.v2/DiscoveryService.cs:545— src/IBM.Watson.Discovery.v2/DiscoveryService.cs:545-568 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:693-716 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v2/DiscoveryService.cs:545` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (24–25 lines × 2) src/IBM.Watson.Assistant.v2/Model/MessageInputOptions.cs:26— src/IBM.Watson.Assistant.v2/Model/MessageInputOptions.cs:26-50 | src/IBM.Watson.Assistant.v2/Model/MessageInputOptionsStateless.cs:26-49 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/MessageInputOptions.cs` and `src/IBM.Watson.Assistant.v2/Model/MessageInputOptionsStateless.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v2/Model/MessageInputOptions.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 5) src/IBM.Watson.Discovery.v1/Model/Collection.cs:58— src/IBM.Watson.Discovery.v1/Model/Collection.cs:58-77 | src/IBM.Watson.Discovery.v1/Model/Environment.cs:118-137 | src/IBM.Watson.Discovery.v2/Model/CollectionDetails.cs:33-53 | src/IBM.Watson.Discovery.v2/Model/DocumentClassifier.cs:33-53 | src/IBM.Watson.Discovery.v2/Model/DocumentClassifierModel.cs:58-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.Discovery.v1/Model/Collection.cs:82` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/CollectionDetails.cs:54` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 4) src/IBM.Watson.Discovery.v2/Model/TableBodyCells.cs:44— src/IBM.Watson.Discovery.v2/Model/TableBodyCells.cs:44-63 | src/IBM.Watson.Discovery.v2/Model/TableColumnHeaders.cs:51-70 | src/IBM.Watson.Discovery.v2/Model/TableHeaders.cs:44-63 | src/IBM.Watson.Discovery.v2/Model/TableRowHeaders.cs:49-68 — before extracting anything, compare `src/IBM.Watson.Discovery.v2/Model/TableBodyCells.cs` and `src/IBM.Watson.Discovery.v2/Model/TableRowHeaders.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.Discovery.v2/Model/TableHeaders.cs:37` calls `JsonProperty` and `src/IBM.Watson.Discovery.v2/Model/TableBodyCells.cs:38` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4598— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4598-4616 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:4758-4776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/IBM.Watson.Discovery.v1/DiscoveryService.cs:4598` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20–21 lines × 2) src/IBM.Watson.SpeechToText.v1/Model/AudioListing.cs:66— src/IBM.Watson.SpeechToText.v1/Model/AudioListing.cs:66-85 | src/IBM.Watson.SpeechToText.v1/Model/AudioResource.cs:63-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (18 lines × 5) src/IBM.Watson.Assistant.v1/Model/CreateIntent.cs:36— src/IBM.Watson.Assistant.v1/Model/CreateIntent.cs:36-53 | src/IBM.Watson.Assistant.v1/Model/Intent.cs:36-53 | src/IBM.Watson.Discovery.v1/Model/Collection.cs:64-81 | src/IBM.Watson.Discovery.v1/Model/Environment.cs:124-141 | src/IBM.Watson.Discovery.v2/Model/DocumentClassifierModel.cs:64-81 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/CreateIntent.cs` and `src/IBM.Watson.Assistant.v1/Model/Intent.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/IBM.Watson.Discovery.v1/Model/Environment.cs:149` calls `JsonProperty` and `src/IBM.Watson.Discovery.v1/Model/Collection.cs:83` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 57) src/IBM.Watson.Assistant.v1/AssistantService.cs:736— src/IBM.Watson.Assistant.v1/AssistantService.cs:736-751 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1532-1547 | src/IBM.Watson.Assistant.v1/AssistantService.cs:1988-2003 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2391-2406 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2860-2875 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3462-3477 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3952-3967 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4573-4588 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4797-4812 | src/IBM.Watson.Assistant.v2/AssistantService.cs:278-293 | src/IBM.Watson.Assistant.v2/AssistantService.cs:429-444 | src/IBM.Watson.Assistant.v2/AssistantService.cs:859-874 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1520-1535 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1438-1453 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1638-1653 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1849-1864 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3332-3347 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3475-3490 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3719-3734 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:3953-3968 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:347-362 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:765-780 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2056-2071 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2277-2292 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2439-2454 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2744-2759 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3098-3113 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3493-3508 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3912-3927 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:4120-4135 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:993-1008 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1445-1460 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2606-2621 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3012-3027 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3235-3250 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3308-3323 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3507-3522 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3639-3654 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3898-3913 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4039-4054 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4169-4184 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4367-4382 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4527-4542 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4913-4928 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5090-5105 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5182-5197 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5445-5460 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5757-5772 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:5813-5828 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1495-1510 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1598-1613 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1685-1700 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1840-1855 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1960-1975 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2307-2322 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2562-2577 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:2617-2632 — `src/IBM.Watson.Assistant.v1/AssistantService.cs` and `src/IBM.Watson.Assistant.v2/AssistantService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 104 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/AssistantService.cs:736` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `bool? allowOverwrite =` in one and `string displayAs =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:3504` calls `WithBodyContent` and `src/IBM.Watson.Assistant.v1/AssistantService.cs:733` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 3) src/IBM.Watson.Assistant.v1/Model/CreateIntent.cs:41— src/IBM.Watson.Assistant.v1/Model/CreateIntent.cs:41-54 | src/IBM.Watson.Assistant.v1/Model/Intent.cs:41-54 | src/IBM.Watson.Discovery.v2/Model/TrainingQuery.cs:44-57 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/CreateIntent.cs` and `src/IBM.Watson.Assistant.v1/Model/Intent.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 7) src/IBM.Watson.Assistant.v1/AssistantService.cs:1806— src/IBM.Watson.Assistant.v1/AssistantService.cs:1806-1814 | src/IBM.Watson.Assistant.v1/AssistantService.cs:2234-2242 | src/IBM.Watson.Assistant.v1/AssistantService.cs:3758-3766 | src/IBM.Watson.Assistant.v1/AssistantService.cs:4303-4311 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1049-1057 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1434-1442 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1877-1885 — `src/IBM.Watson.Assistant.v1/AssistantService.cs` and `src/IBM.Watson.Assistant.v2/AssistantService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 104 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 6) src/IBM.Watson.Assistant.v2/AssistantService.cs:105— src/IBM.Watson.Assistant.v2/AssistantService.cs:105-110 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3025-3030 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:3832-3837 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:2711-2716 | src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:4612-4617 | src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1253-1258 — there are 6 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 3) src/IBM.Watson.Assistant.v1/AssistantService.cs:155— src/IBM.Watson.Assistant.v1/AssistantService.cs:155-160 | src/IBM.Watson.Assistant.v2/AssistantService.cs:526-531 | src/IBM.Watson.Assistant.v2/AssistantService.cs:623-628 — `src/IBM.Watson.Assistant.v1/AssistantService.cs` and `src/IBM.Watson.Assistant.v2/AssistantService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 104 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 3) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:402— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:402-409 | src/IBM.Watson.Discovery.v1/DiscoveryService.cs:2975-2982 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:397-404 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:402` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `List<string> similarFields =` in one and `List<string> collectionIds =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) src/IBM.Watson.Assistant.v2/AssistantService.cs:105— src/IBM.Watson.Assistant.v2/AssistantService.cs:105-110 | src/IBM.Watson.Assistant.v2/AssistantService.cs:1233-1238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 4) src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1764— src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1764-1770 | src/IBM.Watson.Discovery.v2/DiscoveryService.cs:2864-2870 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:466-472 | src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:475-481 — `src/IBM.Watson.Discovery.v1/DiscoveryService.cs` and `src/IBM.Watson.Discovery.v2/DiscoveryService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 327 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1764` it does not close everything it opens, so those 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `System.IO.MemoryStream file =` in one and `string name =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (48 lines × 2) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe.cs:35— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe.cs:35-82 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeIframe.cs:35-82 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe.cs` and `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeIframe.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (47 lines × 6) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:35— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:35-92 | src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeImage.cs:35-81 | src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo.cs:35-91 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:35-92 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeImage.cs:35-82 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:35-91 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs` and `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeImage.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (30 lines × 2) src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypePause.cs:35— src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypePause.cs:35-64 | src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypePause.cs:35-64 — before extracting anything, compare `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypePause.cs` and `src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypePause.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypePause.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) src/IBM.Watson.Assistant.v2/Model/LogMessageSourceAction.cs:33— src/IBM.Watson.Assistant.v2/Model/LogMessageSourceAction.cs:33-43 | src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs:33-61 | src/IBM.Watson.Assistant.v2/Model/LogMessageSourceStep.cs:33-52 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/LogMessageSourceAction.cs` and `src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v2/Model/LogMessageSourceAction.cs:33` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (57 lines × 2) src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:35— src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:35-92 | src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:35-91 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs` and `src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (48 lines × 3) src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:35— src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:35-92 | src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeImage.cs:35-82 | src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:35-91 — before extracting anything, compare `src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs` and `src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeImage.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Edited copies of one member (6 members, 24+ corresponding lines) · ×1
Edited copies of one member (6 members, 24+ corresponding lines) src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:573— src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:573-596 | src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:617-644 | src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:664-690 | src/IBM.Watson.LanguageTranslator.v3/Examples/ServiceExample.cs:118-141 | src/IBM.Watson.LanguageTranslator.v3/Examples/ServiceExample.cs:186-210 | REDACTED:394-417 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:443— src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:443-472 | src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:507-538 | src/IBM.Watson.Discovery.v1/Examples/ServiceExample.cs:804-830 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 19+ corresponding lines) · ×1
Edited copies of one member (5 members, 19+ corresponding lines) src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:106— src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:106-124 | src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:223-249 | src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:268-291 | src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:504-534 | src/IBM.Watson.Assistant.v1/Examples/ServiceExample.cs:660-681 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) REDACTED:202— REDACTED:202-220 | REDACTED:508-528 | REDACTED:580-596 | REDACTED:761-777 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) src/IBM.Watson.Assistant.v2/Examples/ServiceExample.cs:49— src/IBM.Watson.Assistant.v2/Examples/ServiceExample.cs:49-63 | src/IBM.Watson.Assistant.v2/Examples/ServiceExample.cs:84-101 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) src/IBM.Watson.LanguageTranslator.v3/Examples/ServiceExample.cs:106— src/IBM.Watson.LanguageTranslator.v3/Examples/ServiceExample.cs:106-115 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/Examples/ServiceExample.cs:80-91 | REDACTED:115-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (18 lines × 4) src/IBM.Watson.NaturalLanguageUnderstanding.v1/Examples/ServiceExample.cs:112— src/IBM.Watson.NaturalLanguageUnderstanding.v1/Examples/ServiceExample.cs:112-132 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/Examples/ServiceExample.cs:135-155 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/Examples/ServiceExample.cs:205-227 | src/IBM.Watson.NaturalLanguageUnderstanding.v1/Examples/ServiceExample.cs:230-247 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Outbound HTTP without resilience REDACTED:832— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×1
Disposable created and abandoned in the method that made it REDACTED:832— `client` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 832). Every use of it in `DownloadAcousticResource` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Orphaned file src/IBM.Watson.Discovery.v2/DiscoveryService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.TextToSpeech.v1/TextToSpeechService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v2/AssistantService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.NaturalLanguageUnderstanding.v1/NaturalLanguageUnderstandingService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGeneric.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v1/Model/DialogNode.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Discovery.v1/Model/CredentialDetails.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v1/Model/RuntimeEntityInterpretation.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v2/Model/RuntimeEntityInterpretation.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v2/Model/RuntimeResponseGeneric.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v1/IAssistantService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Discovery.v1/IDiscoveryService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGeneric.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.SpeechToText.v1/Model/LanguageModel.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Discovery.v1/Model/LogQueryResponseResult.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v2/Model/MessageContextGlobalSystem.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEvent.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Discovery.v2/IDiscoveryService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Assistant.v1/Model/Workspace.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.SpeechToText.v1/Model/AcousticModel.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.SpeechToText.v1/ISpeechToTextService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Discovery.v1/Model/Environment.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.Discovery.v1/Model/NormalizationOperation.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/IBM.Watson.SpeechToText.v1/Model/RecognitionJob.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 155 more in this group — see findings.md.
P10 · Library API & versioning· Public type used only inside its own library · ×40
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeAudio.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeChannelTransfer.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeConnectToAgent.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeIframe.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeImage.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeImage` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeImage.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeOption.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeOption` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeOption.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypePause.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypePause` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypePause.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeSearchSkill.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeSearchSkill` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeSearchSkill.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeUserDefined.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo.cs:26— `IBM.Watson.Assistant.v1.Model.DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo` (src/IBM.Watson.Assistant.v1/Model/DialogNodeOutputGenericDialogNodeOutputResponseTypeVideo.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeAudio` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeAudio.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeConnectToAgent.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeConnectToAgent` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeConnectToAgent.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeIframe.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeIframe` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeIframe.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeImage.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeImage` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeImage.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeOption.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeOption` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeOption.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypePause.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypePause` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypePause.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeSuggestion.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeSuggestion` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeSuggestion.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeText.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeText` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeText.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeUserDefined.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeUserDefined` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeUserDefined.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:26— `IBM.Watson.Assistant.v1.Model.RuntimeResponseGenericRuntimeResponseTypeVideo` (src/IBM.Watson.Assistant.v1/Model/RuntimeResponseGenericRuntimeResponseTypeVideo.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v1.Examples`, `IBM.Watson.Assistant.v1.IntegrationTests`, `IBM.Watson.Assistant.v1.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v2/Model/LogMessageSourceAction.cs:25— `IBM.Watson.Assistant.v2.Model.LogMessageSourceAction` (src/IBM.Watson.Assistant.v2/Model/LogMessageSourceAction.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v2/Model/LogMessageSourceDialogNode.cs:25— `IBM.Watson.Assistant.v2.Model.LogMessageSourceDialogNode` (src/IBM.Watson.Assistant.v2/Model/LogMessageSourceDialogNode.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs:25— `IBM.Watson.Assistant.v2.Model.LogMessageSourceHandler` (src/IBM.Watson.Assistant.v2/Model/LogMessageSourceHandler.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v2/Model/LogMessageSourceStep.cs:25— `IBM.Watson.Assistant.v2.Model.LogMessageSourceStep` (src/IBM.Watson.Assistant.v2/Model/LogMessageSourceStep.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionFinished.cs:26— `IBM.Watson.Assistant.v2.Model.MessageOutputDebugTurnEventTurnEventActionFinished` (src/IBM.Watson.Assistant.v2/Model/MessageOutputDebugTurnEventTurnEventActionFinished.cs:26) is public, and the library's own code uses it, but no other project in this repository uses it (read: `IBM.Watson.Assistant.v2.Examples`, `IBM.Watson.Assistant.v2.IntegrationTests`, `IBM.Watson.Assistant.v2.UnitTests`, `IBM.Watson.IntegrationTests`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
redundant comment src/IBM.Watson.Assistant.v1/Test/Unit/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Assistant.v1/Test/Unit/Properties/AssemblyInfo.cs:13— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Assistant.v1/Test/Unit/Properties/AssemblyInfo.cs:18— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v1/Test/Integration/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v1/Test/Integration/Properties/AssemblyInfo.cs:13— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v1/Test/Integration/Properties/AssemblyInfo.cs:18— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v1/Test/Unit/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v1/Test/Unit/Properties/AssemblyInfo.cs:13— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v1/Test/Unit/Properties/AssemblyInfo.cs:18— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v2/Test/Integration/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v2/Test/Integration/Properties/AssemblyInfo.cs:13— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.Discovery.v2/Test/Integration/Properties/AssemblyInfo.cs:18— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.LanguageTranslator.v3/Test/Integration/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.LanguageTranslator.v3/Test/Integration/Properties/AssemblyInfo.cs:13— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.LanguageTranslator.v3/Test/Integration/Properties/AssemblyInfo.cs:18— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.LanguageTranslator.v3/Test/Unit/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.LanguageTranslator.v3/Test/Unit/Properties/AssemblyInfo.cs:13— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.LanguageTranslator.v3/Test/Unit/Properties/AssemblyInfo.cs:18— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/Properties/AssemblyInfo.cs:13— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.NaturalLanguageUnderstanding.v1/Test/Integration/Properties/AssemblyInfo.cs:18— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.SpeechToText.v1/Test/Integration/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.SpeechToText.v1/Test/Integration/Properties/AssemblyInfo.cs:13— "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.SpeechToText.v1/Test/Integration/Properties/AssemblyInfo.cs:18— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/IBM.Watson.TextToSpeech.v1/Test/Integration/Properties/AssemblyInfo.cs:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Fat interface: IAssistantService (49 members) src/IBM.Watson.Assistant.v1/IAssistantService.cs:24— `IAssistantService` declares 49 members: `Message`, `BulkClassify`, `ListWorkspaces`, `CreateWorkspace`, `GetWorkspace`, `UpdateWorkspace`, `DeleteWorkspace`, `CreateWorkspaceAsync`, `UpdateWorkspaceAsync`, `ExportWorkspaceAsync`, `ListIntents`, `CreateIntent`, `GetIntent`, `UpdateIntent`, `DeleteIntent`, `ListExamples`, `CreateExample`, `GetExample`, `UpdateExample`, `DeleteExample`, `ListCounterexamples`, `CreateCounterexample`, `GetCounterexample`, `UpdateCounterexample`, `DeleteCounterexample`, `ListEntities`, `CreateEntity`, `GetEntity`, `UpdateEntity`, `DeleteEntity`, `ListMentions`, `ListValues`, `CreateValue`, `GetValue`, `UpdateValue`, `DeleteValue`, `ListSynonyms`, `CreateSynonym`, `GetSynonym`, `UpdateSynonym`, and 9 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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.
Fat interface: IAssistantService (23 members) src/IBM.Watson.Assistant.v2/IAssistantService.cs:25— `IAssistantService` declares 23 members: `CreateAssistant`, `ListAssistants`, `DeleteAssistant`, `CreateSession`, `DeleteSession`, `Message`, `MessageStateless`, `BulkClassify`, `ListLogs`, `DeleteUserData`, `ListEnvironments`, `GetEnvironment`, `UpdateEnvironment`, `CreateRelease`, `ListReleases`, `GetRelease`, `DeleteRelease`, `DeployRelease`, `GetSkill`, `UpdateSkill`, `ExportSkills`, `ImportSkills`, `ImportSkillsStatus`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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.
Fat interface: IDiscoveryService (62 members) src/IBM.Watson.Discovery.v1/IDiscoveryService.cs:26— `IDiscoveryService` declares 62 members: `CreateEnvironment`, `ListEnvironments`, `GetEnvironment`, `UpdateEnvironment`, `DeleteEnvironment`, `ListFields`, `CreateConfiguration`, `ListConfigurations`, `GetConfiguration`, `UpdateConfiguration`, `DeleteConfiguration`, `CreateCollection`, `ListCollections`, `GetCollection`, `UpdateCollection`, `DeleteCollection`, `ListCollectionFields`, `ListExpansions`, `CreateExpansions`, `DeleteExpansions`, `GetTokenizationDictionaryStatus`, `CreateTokenizationDictionary`, `DeleteTokenizationDictionary`, `GetStopwordListStatus`, `CreateStopwordList`, `DeleteStopwordList`, `AddDocument`, `GetDocumentStatus`, `UpdateDocument`, `DeleteDocument`, `Query`, `QueryNotices`, `FederatedQuery`, `FederatedQueryNotices`, `GetAutocompletion`, `ListTrainingData`, `AddTrainingData`, `DeleteAllTrainingData`, `GetTrainingData`, `DeleteTrainingData`, and 22 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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.
Fat interface: IDiscoveryService (50 members) src/IBM.Watson.Discovery.v2/IDiscoveryService.cs:24— `IDiscoveryService` declares 50 members: `ListProjects`, `CreateProject`, `GetProject`, `UpdateProject`, `DeleteProject`, `ListFields`, `ListCollections`, `CreateCollection`, `GetCollection`, `UpdateCollection`, `DeleteCollection`, `ListDocuments`, `AddDocument`, `GetDocument`, `UpdateDocument`, `DeleteDocument`, `Query`, `GetAutocompletion`, `QueryCollectionNotices`, `QueryNotices`, `GetStopwordList`, `CreateStopwordList`, `DeleteStopwordList`, `ListExpansions`, `CreateExpansions`, `DeleteExpansions`, `GetComponentSettings`, `ListTrainingQueries`, `DeleteTrainingQueries`, `CreateTrainingQuery`, `GetTrainingQuery`, `UpdateTrainingQuery`, `DeleteTrainingQuery`, `ListEnrichments`, `CreateEnrichment`, `GetEnrichment`, `UpdateEnrichment`, `DeleteEnrichment`, `ListDocumentClassifiers`, `CreateDocumentClassifier`, and 10 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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.
Fat interface: ISpeechToTextService (41 members) src/IBM.Watson.SpeechToText.v1/ISpeechToTextService.cs:24— `ISpeechToTextService` declares 41 members: `ListModels`, `GetModel`, `Recognize`, `RegisterCallback`, `UnregisterCallback`, `CreateJob`, `CheckJobs`, `CheckJob`, `DeleteJob`, `CreateLanguageModel`, `ListLanguageModels`, `GetLanguageModel`, `DeleteLanguageModel`, `TrainLanguageModel`, `ResetLanguageModel`, `UpgradeLanguageModel`, `ListCorpora`, `AddCorpus`, `GetCorpus`, `DeleteCorpus`, `ListWords`, `AddWords`, `AddWord`, `GetWord`, `DeleteWord`, `ListGrammars`, `AddGrammar`, `GetGrammar`, `DeleteGrammar`, `CreateAcousticModel`, `ListAcousticModels`, `GetAcousticModel`, `DeleteAcousticModel`, `TrainAcousticModel`, `ResetAcousticModel`, `UpgradeAcousticModel`, `ListAudio`, `AddAudio`, `GetAudio`, `DeleteAudio`, and 1 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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.
Fat interface: ITextToSpeechService (23 members) src/IBM.Watson.TextToSpeech.v1/ITextToSpeechService.cs:24— `ITextToSpeechService` declares 23 members: `ListVoices`, `GetVoice`, `Synthesize`, `GetPronunciation`, `CreateCustomModel`, `ListCustomModels`, `UpdateCustomModel`, `GetCustomModel`, `DeleteCustomModel`, `AddWords`, `ListWords`, `AddWord`, `GetWord`, `DeleteWord`, `ListCustomPrompts`, `AddCustomPrompt`, `GetCustomPrompt`, `DeleteCustomPrompt`, `ListSpeakerModels`, `CreateSpeakerModel`, `GetSpeakerModel`, `DeleteSpeakerModel`, `DeleteUserData`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. 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.
Outdated: coveralls.net src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj:40— coveralls.net 0.7.0 → 4.0.1 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
Outdated: Microsoft.Extensions.Configuration src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj:37— Microsoft.Extensions.Configuration 1.0.2 → 11.0.0 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
Outdated: Microsoft.Extensions.Configuration.Json src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj:38— Microsoft.Extensions.Configuration.Json 1.0.2 → 11.0.0 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
Outdated: Microsoft.NET.Test.Sdk src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj:32— Microsoft.NET.Test.Sdk 15.5.0 → 18.12.0 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
Outdated: MSTest.TestAdapter src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj:33— MSTest.TestAdapter 1.1.8-rc → 4.5.3 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
Outdated: MSTest.TestFramework src/IBM.Watson.Assistant.v1/Test/Integration/IBM.Watson.Assistant.v1.IntegrationTests.csproj:34— MSTest.TestFramework 1.0.8-rc → 4.5.3 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×4
Projects may be oversized for their cohesion REDACTED:1— `IBM.Watson.Assistant.v1` overshoots its size bounds (10592 LoC, 141 public types across 2 namespaces). 4 of 34 project(s) overshoot their size bounds, lowering Project Cohesion to 8.0/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
Projects may be oversized for their cohesion src/IBM.Watson.Discovery.v1/IBM.Watson.Discovery.v1.csproj:1— `IBM.Watson.Discovery.v1` overshoots its size bounds (10444 LoC, 150 public types across 2 namespaces). 4 of 34 project(s) overshoot their size bounds, lowering Project Cohesion to 8.0/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
Projects may be oversized for their cohesion src/IBM.Watson.Discovery.v2/IBM.Watson.Discovery.v2.csproj:1— `IBM.Watson.Discovery.v2` overshoots its size bounds (9409 LoC, 124 public types across 2 namespaces). 4 of 34 project(s) overshoot their size bounds, lowering Project Cohesion to 8.0/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
Projects may be oversized for their cohesion src/IBM.Watson.Assistant.v2/IBM.Watson.Assistant.v2.csproj:1— `IBM.Watson.Assistant.v2` overshoots its size bounds (8845 LoC, 155 public types across 2 namespaces). 4 of 34 project(s) overshoot their size bounds, lowering Project Cohesion to 8.0/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file src/IBM.Watson.SpeechToText.v1/SpeechToTextService.cs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/IBM.Watson.Assistant.v1/AssistantService.cs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Duplicated predicate src/IBM.Watson.Discovery.v1/DiscoveryService.cs:407— `collectionIds != null && collectionIds.Count > 0` appears character-identically in 2 files — src/IBM.Watson.Discovery.v1/DiscoveryService.cs, src/IBM.Watson.Discovery.v2/DiscoveryService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/IBM.Watson.Discovery.v1/DiscoveryService.cs:498— `enrichments != null && enrichments.Count > 0` appears character-identically in 2 files — src/IBM.Watson.Discovery.v1/DiscoveryService.cs, src/IBM.Watson.Discovery.v2/DiscoveryService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/IBM.Watson.Discovery.v1/DiscoveryService.cs:1367— `expansions != null && expansions.Count > 0` appears character-identically in 2 files — src/IBM.Watson.Discovery.v1/DiscoveryService.cs, src/IBM.Watson.Discovery.v2/DiscoveryService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Documentation: no map of the repository's parts README.md:1— The repository has 9 units (`IBM.Watson.Assistant.v1`, `IBM.Watson.Assistant.v2`, `IBM.Watson.Common`, `IBM.Watson.Discovery.v1`, `IBM.Watson.Discovery.v2`, ...); `README.md` and the documents it links name none of them. Add a short list of the parts and what each does.
D27 · Navigability· High interface indirection · ×1
High interface indirection — 39 % of calls go through an interface — tracing a call means resolving the implementation each hop. Prefer concrete types where there's a single implementation.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Dormant codebase — 183 of 196 significant files have no living knowledge — the codebase as a whole is dormant, not 183 separate risks. Counted over 196 of the 558 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, 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.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 5 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
No SAST REDACTED:11— No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation REDACTED:38— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Nullable reference types not enabled everywhere — 0/3 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
doc comments repeat the names src/IBM.Watson.Assistant.v1/AssistantService.cs:3051— 0 of 302 documented parameters and 55 of 733 summaries in `IBM.Watson.Assistant.v1` only repeat the member or parameter name (e.g. "Enum values for ListValues." for `ListValuesEnums`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/IBM.Watson.Assistant.v2/Model/AgentAvailabilityMessage.cs:22— 0 of 78 documented parameters and 81 of 770 summaries in `IBM.Watson.Assistant.v2` only repeat the member or parameter name (e.g. "AgentAvailabilityMessage." for `AgentAvailabilityMessage`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/IBM.Watson.Discovery.v1/DiscoveryService.cs:190— 88 of 256 documented parameters and 11 of 716 summaries in `IBM.Watson.Discovery.v1` only repeat the member or parameter name (e.g. "The ID of the environment." for `environmentId`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/IBM.Watson.Discovery.v2/DiscoveryService.cs:108— 30 of 173 documented parameters and 12 of 650 summaries in `IBM.Watson.Discovery.v2` only repeat the member or parameter name (e.g. "Create a project. Create a new project for this instance." for `CreateProject`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/IBM.Watson.LanguageTranslator.v3/LanguageTranslatorService.cs:794— 1 of 25 documented parameters and 10 of 139 summaries in `IBM.Watson.LanguageTranslator.v3` only repeat the member or parameter name (e.g. "The content type of file." for `FileContentTypeValue`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/IBM.Watson.NaturalLanguageUnderstanding.v1/Model/CategoriesModel.cs:24— 6 of 51 documented parameters and 32 of 315 summaries in `IBM.Watson.NaturalLanguageUnderstanding.v1` only repeat the member or parameter name (e.g. "Categories model." for `CategoriesModel`). Delete the restating tags, or add what the name does not say.
Outdated: Newtonsoft.Json — REDACTED → 13.0.4 available (referenced by IBM.Watson.Common).
Outdated: JsonSubTypes — JsonSubTypes 1.6.0 → 2.2.0 available (referenced by IBM.Watson.Assistant.v1).
Outdated: NSubstitute — NSubstitute 4.2.1 → 6.2.0 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
Outdated: OpenCover — OpenCover 4.7.922 → 4.7.1221 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
Outdated: ReportGenerator — ReportGenerator 4.1.5 → 5.6.0 available (referenced by IBM.Watson.SpeechToText.v1.IntegrationTests).
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e771-4dda-7f41-a6c8-bad3e4a44e74 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 85 · Warnings: 566 · Recommendations: 730 · Info: 28 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 02:58 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.