Public report of shimat/opencvsharp, published 16 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 report Measured 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, 16 November 2026, 23:10 UTC · Survey ID cd_3076966b28f444cf8733eb10dee52207

shimat/opencvsharp

Measured 16 November 2026, 23:09 UTC, at code version 0e2572d

First survey, so nothing to compare with yet Code coverage: not measuredBoundary Type-Coupling: not measured

Code coverage is not measured: The repo's test suite did not build.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 50.7out of 100 Weak
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 large codebase: 151,117 lines of product code in 62 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Code Health, 45.2

Findings by how serious they are

259 critical 680 serious 226 minor

4 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 23:09 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 ▸

56of 56 dimensions measured by tools.
1152of 1165 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
56dimensions across 6 lenses, read from 151,117 lines of product code in 62 projects.
Chapters

Executive summary

shimat/opencvsharp falls short of our standard for production because its Explicit debt dimensions are rated Critical, and it has warnings switched off for a whole file. It scores 50.7 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.

Code Health, at 45.2, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 4.7 points. Removing the unread values would lift Code Health itself, worth about 3.2 points.

132 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Ten pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and nine secrets can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the five passwords or keys in the code's history and the three passwords or keys in the code need replacing, with the old ones switched off. The 47 warnings switched off for a whole file need narrowing to the lines that need them.

The product code is 151,117 lines, about €130,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 for The 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.
Code Health 45.2 · counts for 46%Production Readiness 47.2 · counts for 25%Security and Compliance 47.7 · counts for 14%Maturity 60.6 · counts for 8%Architecture 96.0 · counts for 4%Performance 100.0 · counts for 2%

The weakest lenses score close to each other, so improving any of them moves the score.

Code composition: what the lines of code are Most of the hand-written code is supporting code, such as wiring, settings and declarations, and business logic is 9% of it. That is normal for a service that mainly connects other systems or stores and fetches records, and worth a look if this product is meant to hold complex business rules.
Business logic 7%Supporting code 65%Tests 28%Code analyzers 0%
Rebuild cost: about €130,000 · Estimate
Cost to rebuild€44,000 to €220,000, for 731 to 2,291 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problemStandard, 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 51. 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.
SizeLarge: 151,117 lines of product code
Comment linesThe estimate prices 113,349 lines. Comment lines count towards the size of 151,117 lines but aren't priced as work.
What it is notNot 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 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3).
Raises the score by about 4.7 points · Low effort · Secret Scanning
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with OpenCvSharp.WpfExtensions.csproj.
Raises the score by about 1.9 points · Low effort · ADR Quality
3
Resolve the 12 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Stitcher.cs (7), FlannBasedMatcher.cs (2), MatTest.cs.
Raises the score by about 3.2 points · Medium effort · Explicit Debt

Diagnosis: what the measurements show together

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 €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Code Health, at 45.2 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 4.7 points for low effort, because it clears the 3 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch OpenCvSharp OpenCvSharp OpenCvSharp.AvaloniaExtensions AvaloniaExtensions OpenCvSharp.AvaloniaExtensions->OpenCvSharp OpenCvSharp.GdipExtensions GdipExtensions OpenCvSharp.GdipExtensions->OpenCvSharp OpenCvSharp.WpfExtensions WpfExtensions OpenCvSharp.WpfExtensions->OpenCvSharp OpenCvSharp5.Windows Windows OpenCvSharp5.Windows.Slim Slim OpenCvSharp5.official.runtime.linux-arm64 linux-arm64 OpenCvSharp5.official.runtime.linux-arm64.headless headless OpenCvSharp5.official.runtime.linux-arm64.slim slim OpenCvSharp5.official.runtime.linux-x64 linux-x64 OpenCvSharp5.official.runtime.linux-x64.headless headless OpenCvSharp5.official.runtime.linux-x64.slim slim OpenCvSharp5.runtime.android android OpenCvSharp5.runtime.linux-arm linux-arm OpenCvSharp5.runtime.linux-arm64 linux-arm64 OpenCvSharp5.runtime.osx.arm64 arm64 OpenCvSharp5.runtime.osx.x64 x64 OpenCvSharp5.runtime.wasm wasm OpenCvSharp5.runtime.win win OpenCvSharp5.runtime.win-arm64 win-arm64 __more__ +2 more projects

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.

40 modules, with 71 dependencies between them. One loop runs through 20 of the modules, marked above the diagonal.

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.
uses →1 Analyzers2 DnnObjdetect3 Aruco4 Detail5 Flann6 ImgHash7 Internal.Util8 LineDescriptor9 ML10 Text11 Tracking12 Tracking.Legacy13 XFeatures2D14 XImgProc.Segmentation15 XPhoto16 Internal17 Internal.Vectors18 Dnn19 Face20 OptFlow21 XImgProc22 OpenCvSharp23 AvaloniaExtensions24 Bioinspired25 DnnSuperres26 Dpm27 Extensions28 GdipExtensions29 Hfs30 Plot31 PpfMatch3D32 Quality33 Rapid34 Reg35 Rgbd36 Saliency37 Segmentation38 StructuredLight39 VideoStab40 WpfExtensions
1 Analyzers
2 DnnObjdetect
3 Aruco28
4 Detail39
5 Flann4
6 ImgHash11
7 Internal.Util1
8 LineDescriptor10
9 ML27
10 Text17
11 Tracking5
12 Tracking.Legacy13
13 XFeatures2D58
14 XImgProc.Segmentation9
15 XPhoto10
16 Internal231122197
17 Internal.Vectors12221
18 Dnn130
19 Face144
20 OptFlow215
21 XImgProc162
22 OpenCvSharp13122112316622101324
23 AvaloniaExtensions1
24 Bioinspired8
25 DnnSuperres24
26 Dpm3
27 Extensions2
28 GdipExtensions1
29 Hfs3
30 Plot4
31 PpfMatch3D3
32 Quality120
33 Rapid3
34 Reg1
35 Rgbd745
36 Saliency20
37 Segmentation4
38 StructuredLight12
39 VideoStab1
40 WpfExtensions3
Uses a module listed above itPart of a loopThe module itself
1 Analyzers2 DnnObjdetect3 Aruco4 Detail5 Flann6 ImgHash7 Internal.Util8 LineDescriptor9 ML10 Text11 Tracking12 Tracking.Legacy13 XFeatures2D14 XImgProc.Segmentation15 XPhoto16 Internal17 Internal.Vectors18 Dnn19 Face20 OptFlow21 XImgProc22 OpenCvSharp23 AvaloniaExtensions24 Bioinspired25 DnnSuperres26 Dpm27 Extensions28 GdipExtensions29 Hfs30 Plot31 PpfMatch3D32 Quality33 Rapid34 Reg35 Rgbd36 Saliency37 Segmentation38 StructuredLight39 VideoStab40 WpfExtensionsAnalyzers1DnnObjdetect2Aruco3Detail4Flann5ImgHash6Internal.Util7LineDescriptor8ML9Text10Tracking11Tracking.Legacy12XFeatures2D13XImgProc.Segmentation14XPhoto15Internal16Internal.Vectors17Dnn18Face19OptFlow20XImgProc21OpenCvSharp22AvaloniaExtensions23Bioinspired24DnnSuperres25Dpm26Extensions27GdipExtensions28Hfs29Plot30PpfMatch3D31Quality32Rapid33Reg34Rgbd35Saliency36Segmentation37StructuredLight38VideoStab39WpfExtensions40283941111027175135891023112219712221130144215162131221123166221013241824321343120317452041213

At a glance — Code Health · 45.2 · Weak · gated by D17 ·

At a glance — Architecture · 96.0 · Exemplary ·

At a glance — Maturity · 60.6 · Adequate · gated by M2 ·

At a glance — Readiness · 47.2 · Weak · gated by D13, P2 ·

At a glance — Security · 47.7 · Weak · gated by D29, D36 ·

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection154High / Critical
A02:2025 — Security Misconfiguration15Medium
A07:2025 — Authentication Failures9High / Critical
A03:2025 — Software Supply Chain Failures5Medium

Roadmap

Top priorities: Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3); Resolve the 12 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Stitcher.cs (7), FlannBasedMatcher.cs (2), MatTest.cs; Resolve the 29 NoWarnInCsproj finding(s) in Explicit Debt — start with OpenCvSharp.Tests.csproj (6), OpenCvSharp.Tests.Avalonia.csproj (5), OpenCvSharp.AvaloniaExtensions.csproj (4).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3).+4.7 ptsLowSecret Scanning
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with OpenCvSharp.WpfExtensions.csproj.+1.9 ptsLowADR Quality
Resolve the 12 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Stitcher.cs (7), FlannBasedMatcher.cs (2), MatTest.cs.+3.2 ptsMediumExplicit Debt
Resolve the 29 NoWarnInCsproj finding(s) in Explicit Debt — start with OpenCvSharp.Tests.csproj (6), OpenCvSharp.Tests.Avalonia.csproj (5), OpenCvSharp.AvaloniaExtensions.csproj (4).+3.2 ptsMediumExplicit Debt
Resolve the 34 FileScopedPragmaDisable finding(s) in Explicit Debt — start with FlannDistance.cs (2), CvObject.cs, NativeMethods_barcode.cs.+3.2 ptsMediumExplicit Debt
Give consumers a diagnostics seam rather than taking a logging dependency: emit through an `EventSource`/`ActivitySource` (or `DiagnosticSource`) the host can subscribe to, accept an optional logger/handler on your options object, or document the hook you already expose.+2.4 ptsMediumObservability
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.+2.4 ptsMediumArchitecture documentation
Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED (5).+0.9 ptsLowSecrets (history)

File quality

Per-file score 0–10 — a quality signature. Of 325 files carrying findings, judged against the Production bar: 1% slop · 51% mixed · 48% near-clean.

FileScoreBandWorst signal
src/OpenCvSharp/Modules/core/Mat/Mat.cs1.1SlopExplicit Debt: FileScopedPragmaDisable repeated across 18 files
test/OpenCvSharp.Tests/imgcodecs/ImgCodecsTest.cs1.9SlopExplicit Debt: FileScopedPragmaDisable
src/OpenCvSharp/Modules/stitching/Stitcher.cs1.9SlopExplicit Debt: WriteOnlyPrivateField
test/OpenCvSharp.Tests/core/MatTest.cs2.3SlopExplicit Debt: WriteOnlyPrivateField
test/OpenCvSharp.Tests/TestBase.cs4.2MixedExplicit Debt: FileScopedPragmaDisable
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
test/OpenCvSharp.Tests/barcode/BarcodeDetectorTest.cs4.7MixedExplicit Debt: FileScopedPragmaDisable repeated across 10 files

How the grades work

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 — 259

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 — 680

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 — 226

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 4

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 56 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 — 56 dimensions across the health lenses
D1D2D3D4D5D6D10D11D13D14D15D17D18D19D20D21D24D26D27D28D29D30D31D34D35D36D43D44AX10AX3AX4AX5AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P6PF3X12X16X18X20X27X29X3X30X5

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
  1. 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, 1152 of 1165 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1e69f-c756-7cdc-84ac-b3a1e2833e44.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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.

  • D4 Code Duplication — 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 43 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cpp (40,285 lines, 27% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: error: The imported file "$(VCTargetsPath)/Microsoft.Cpp.Default.props" does not exist and appears to be part of a Visual Studio component. This file may require MSBuild.exe in order to be imported successfully, and so may fail to build in the dotnet CLI. /tmp/codehealth-iso-2cf7ac5ec8e7477bbd3a62….
  • 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 (101 contributor(s) across 4362 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 100 hold 0.1% 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 'src/OpenCvSharp.AvaloniaExtensions/OpenCvSharp.AvaloniaExtensions.csproj' with message: The URL of repository remote 'origin' is invalid: ''.
  • 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 1,049 deducted marker(s) and the 6.4/KLoC density on this row were taken over this repository's .NET projects ALONE: .cpp (40,285 lines, 27% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D18 Solution Shape — 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 repository declares git submodule(s) (opencv, opencv_contrib) that are not checked out in the tree the analyzer was given, and every compiler error is an unresolved reference (CS0234: The type or namespace name 'Media' does not exist in the namespace 'System.Windows' (are you missing an assembly reference?); CS0234: The type or namespace name 'Threading' does not exist in the namespace 'System.Windows' (are you missing an assembly reference?); CS0246: The type or namespace name 'BitmapSource' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'BitmapPalette' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'WriteableBitmap' could not be found (are you missing a using directive or an assembly reference?)). Those types exist for anyone who cloned with `--recurse-submodules`, so this is an analyzer-input gap, NOT a code defect: Solution Shape is scored on structure and is NOT capped.
  • 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 — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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 (110,832 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"]`.
  • D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 2063 sampled here came from .cs files. This repository's .cpp source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (nuget packages.config) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — 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. `src/OpenCvSharp/Modules/line_descriptors/LSDParam.cs`, `src/OpenCvSharp/Modules/video/DenseOpticalFlow.cs`, `src/OpenCvSharp/Modules/video/SparseOpticalFlow.cs`, `src/OpenCvSharp/Modules/videoio/StreamReaderStreamAdapter.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX6 Interface segregation — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • AXB2 Runtime readiness — 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. A file the REDACTED copies (`cmake/opencv_build_options_slim.cmake`) is not in the build context; the repository declares git submodules, and a submodule our checkout did not fetch would explain it. (rule: missing-build-input). The renderer reported: docker build failed (exit 1) — ------ REDACTED:71 -------------------- 69 | FROM opencv-builder AS opencvsharp-builder 70 | 71 | >>> COPY src/ /opencvsharp/src/ 72 | 73 | RUN --mount=type=cache,target=/root/.ccache \ -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref b581b959-5935-43bc-add4-31adcbf6cd54::65wyswjiz03ixzcv2iogdv9qv: "/src": not found; likely cause (not identified): a file the REDACTED copies (`cmake/opencv_build_options_slim.cmake`) is not in the build context; the repository declares git submodules, and a submodule our checkout did not fetch would explain it; runtime evidence skipped.
  • 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). docker build failed (exit 1) — ------ REDACTED:71 -------------------- 69 | FROM opencv-builder AS opencvsharp-builder 70 | 71 | >>> COPY src/ /opencvsharp/src/ 72 | 73 | RUN --mount=type=cache,target=/root/.ccache \ -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref b581b959-5935-43bc-add4-31adcbf6cd54::65wyswjiz03ixzcv2iogdv9qv: "/src": not found; likely cause (not identified): a file the REDACTED copies (`cmake/opencv_build_options_slim.cmake`) is not in the build context; the repository declares git submodules, and a submodule our checkout did not fetch would explain it; runtime evidence skipped.
  • 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • 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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
  • M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • 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.
  • X12 Unreachable branch — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X16 Unfloored truncation loop — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X18 Disposal-pattern 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X20 Mistyped argument guard — 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. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
  • X27 Collection changed while being enumerated — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X29 Per-element action decided by a fixed element — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X3 Exception handling — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X30 Support guard that admits what it rejects — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

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.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • 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.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • 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.

Dimensions

D1 · Cyclomatic Complexity7.8 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.8 / 10 · rule-coverage 100% · ceiling Prevented

13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was InputArray.EstimateType at 45. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being MatType.ToString at 17 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/OpenCvSharp/Modules/core/Struct/MatType.cs (MatType.ToString at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

InputArray.EstimateType (cyclomatic 45)src/OpenCvSharp/Modules/core/InputArray.cs:326
BitmapConverter.ToMat (cyclomatic 40)src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:45
CvExtensions.HoughLinesProbabilisticEx (cyclomatic 36)src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:24
StdVector.New1 (cyclomatic 23)src/OpenCvSharp/Internal/Vectors/StdVector.cs:117
StdVector.GetSize (cyclomatic 23)src/OpenCvSharp/Internal/Vectors/StdVector.cs:183

+ 8 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with InputArray.EstimateType (cyclomatic 45), BitmapConverter.ToMat (cyclomatic 40), CvExtensions.HoughLinesProbabilisticEx (cyclomatic 36). — 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 13 together lifts Cyclomatic Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity7.0 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Prevented

14 method(s) exceeded the cognitive complexity threshold of 15; the worst was CvExtensions.HoughLinesProbabilisticEx at 88.

CvExtensions.HoughLinesProbabilisticEx (cognitive 88)src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:24
BitmapConverter.ToMat (cognitive 57)src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:45
BitmapSourceConverter.ToMat (cognitive 47)src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:121
InputArray.EstimateType (cognitive 36)src/OpenCvSharp/Modules/core/InputArray.cs:326
BitmapConverter.ToBitmap (cognitive 34)src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:321

+ 9 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with CvExtensions.HoughLinesProbabilisticEx (cognitive 88). — Refactoring it lifts Cognitive Complexity from 7.0 to about 7.4/10.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes9.0 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Prevented

28 god class(es) detected.

TooManyMethods: Cv2 · ×15src/OpenCvSharp/Cv2/Cv2_core.cs
FileTooLong: objdetect/HOGDescriptor.cs · ×9src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs
ClassTooLong: NativeMethods · ×2src/OpenCvSharp/Internal/PInvoke/NativeMethods/core/NativeMethods_core_Mat.cs
MethodTooLong: BitmapConverter.ToMat · ×2src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:45

What to do

  1. Resolve the 15 TooManyMethods finding(s) in God Classes — start with Cv2_core.cs, Mat.cs, MatExpr.cs. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 9 FileTooLong finding(s) in God Classes — start with HOGDescriptor.cs, Cv2_geometry.cs, Mat.cs. — One of this dimension's main actionable groups (9 warning-level).
  3. Resolve the 2 ClassTooLong finding(s) in God Classes — start with NativeMethods_core_Mat.cs, HOGDescriptor.cs. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication6.6 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.6 / 10 · rule-coverage 100% · ceiling Verified

43 duplicated block group(s) detected. 8.4 % of the production lines (9,322 of 110,832) are in a reported copy. A further 335 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .cpp (27% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Edited copy of a member (7 corresponding lines) · ×30src/OpenCvSharp/Cv2/Cv2_core.cs:517
Edited copy of a member (8 corresponding lines) · ×23src/OpenCvSharp/Modules/bioinspired/Retina.cs:16
Edited copy of a member (9 corresponding lines) · ×19src/OpenCvSharp/Cv2/Cv2_geometry.cs:2423
Edited copy of a member (6 corresponding lines) · ×17src/OpenCvSharp/Cv2/Cv2_video.cs:65
Edited copy of a member (12 corresponding lines) · ×13src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:39

+ 99 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 30 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with Cv2_core.cs (7), Cv2_imgproc.cs (7), LDA.cs (2). — One of this dimension's main actionable groups (30 warning-level).
  2. Resolve the 23 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with Mat.cs (4), Cv2_imgproc.cs (2), Retina.cs. — One of this dimension's main actionable groups (23 warning-level).
  3. Resolve the 19 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with Cv2_core.cs (5), Cv2_imgproc.cs (4), Cv2_geometry.cs (3). — One of this dimension's main actionable groups (19 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling9.9 / 10Stronggated by 1 serious finding✓ 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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

62 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

Off the main sequence: OpenCvSharpsrc/OpenCvSharp/OpenCvSharp.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with OpenCvSharp.csproj. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 32 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D10 · Test Quality9.4 / 10Stronggated by 73 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.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Prevented

75 skipped (71 with a documented reason), 69 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1748 tests.

No assertions: GetPredefinedDictionary · ×69test/OpenCvSharp.Tests/aruco/ArucoTest.cs:74
Skipped test: Issue349 · ×4test/OpenCvSharp.Tests/core/MatTest.cs:1256
Skipped (documented): BlobFromImageWithParamsMatchesBlobFromImage · ×71test/OpenCvSharp.Tests/dnn/BlobAndNmsTest.cs:14

What to do

  1. Resolve the 69 No assertions finding(s) in Test Quality — start with UtilityTest.cs (9), XimgProcTest.cs (7), BarcodeDetectorTest.cs (5). — One of this dimension's main actionable groups (69 warning-level).
  2. Resolve the 4 Skipped test finding(s) in Test Quality — start with ImgCodecsTest.cs (2), MatTest.cs, TrackbarTest.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.

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 flaky across 1 measured tier(s). unit: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

3 secret(s) detected.

REDACTED

What to do

  1. Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 262 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 28 direct `PackageReference`(s), and 218 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

1049 deducted debt markers + unmeasured dead symbols across 110832 LoC in the .NET projects (6.4/KLoC) → score 0.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .cpp (27% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

FileScopedPragmaDisable · ×34src/OpenCvSharp/Fundamentals/CvObject.cs:1
NoWarnInCsproj — 11 warning codes suppressed in one element · ×29src/OpenCvSharp/OpenCvSharp.csproj:83
WriteOnlyPrivateField · ×12src/OpenCvSharp/Modules/features/FlannBasedMatcher.cs:13
AnalyzerSeverityNone · ×5.editorconfig:63
EmptyCatchBlock · ×3src/OpenCvSharp/Cv2/Cv2_highgui.cs:87

+ 18 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 34 FileScopedPragmaDisable finding(s) in Explicit Debt — start with FlannDistance.cs (2), CvObject.cs, NativeMethods_barcode.cs. — One of this dimension's main actionable groups (34 issue-level).
  2. Resolve the 29 NoWarnInCsproj finding(s) in Explicit Debt — start with OpenCvSharp.Tests.csproj (6), OpenCvSharp.Tests.Avalonia.csproj (5), OpenCvSharp.AvaloniaExtensions.csproj (4). — One of this dimension's main actionable groups (29 issue-level).
  3. Resolve the 12 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Stitcher.cs (7), FlannBasedMatcher.cs (2), MatTest.cs. — One of this dimension's main actionable groups (12 issue-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

9 projects, 1205 source files, 139199 hand-written lines of code (110832 production / 28367 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), 11 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 39 document(s) read across 7 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundsrc/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj:36

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with OpenCvSharp.WpfExtensions.csproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency6.2 / 10Adequate✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 6.2 / 10 · rule-coverage 100% · ceiling Verified

2 naming inconsistencies among 53 declarations measured against a convention their peers follow.

`CreateDefaultLINE` spells `LINE` where 53 names in the project spell it `Line`src/OpenCvSharp/Modules/rgbd/LinemodDetector.cs:43
`WeChatQRCode` spells `QR` where 19 names in the project spell it `Qr`src/OpenCvSharp/Modules/wechat_qrcode/WeChatQRCode.cs:12

What to do

  1. Resolve the 1 `CreateDefaultLINE` spells `LINE` where 53 names in the project spell it… finding(s) in Naming Consistency — start with LinemodDetector.cs. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `WeChatQRCode` spells `QR` where 19 names in the project spell it `Qr` finding(s) in Naming Consistency — start with WeChatQRCode.cs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 93% · ceiling Documented

85 of 742 judged comments only repeat the code they sit on (11.5 %). 79 comment(s) in another language or script were not judged.

redundant comment · ×74src/OpenCvSharp.GdipExtensions/Properties/AssemblyInfo.cs:4
doc comments repeat the names · ×3src/OpenCvSharp/Cv2/Cv2_core.cs:44

What to do

  1. Resolve the 74 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (9), NativeMethods_img_hash.cs (4), NativeMethods_shape_HistogramCostExtractor.cs (4). — One of this dimension's main actionable groups (74 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Documented

1 of 27 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionsrc/OpenCvSharp/OpenCvSharp.csproj:1

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 4.2 / 10 · rule-coverage 100% · ceiling Documented

93 % of calls cross a namespace and 0 % go through an interface, but 59 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected. Measured over the .cs source only — this repository's .cpp was not sampled for call sites, so this score covers part of the tree, not all of it.

Scattered collaborators

What to do

  1. Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)5.0 / 10Adequate✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret 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.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 5 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

  1. Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
  2. 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.

D29 · Static Analysis (SAST)0.1 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 0.1 / 10 · rule-coverage 100% · ceiling Documented

154 finding(s): 0 critical, 154 high, 0 medium, 0 low. 124 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. semgrep hit a parse error in 11 file(s) — `src/OpenCvSharp/Modules/line_descriptors/LSDParam.cs` (lines 22–29, line 29), `src/OpenCvSharp/Modules/video/DenseOpticalFlow.cs` (line 22, line 23, lines 23–24, …), `src/OpenCvSharp/Modules/video/SparseOpticalFlow.cs` (line 22, line 23, lines 23–24, …), `src/OpenCvSharp/Modules/videoio/StreamReaderStreamAdapter.cs` (line 6), `src/OpenCvSharpExtern/core.h` (line 1341), … (+6 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 4 of those file(s) — `src/OpenCvSharp/Modules/line_descriptors/LSDParam.cs`, `src/OpenCvSharp/Modules/video/DenseOpticalFlow.cs`, `src/OpenCvSharp/Modules/video/SparseOpticalFlow.cs`, `src/OpenCvSharp/Modules/videoio/StreamReaderStreamAdapter.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 10 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

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED, REDACTED. — One of this dimension's main actionable groups (10 issue-level).
  2. Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
  3. Resolve the 8 REDACTED finding(s) charged to Static Analysis (SAST) — the other 124 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (132 issue-level, 8 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (nuget packages.config). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget packages.config), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D31 · IaC & Container Security8.8 / 10Strong✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.8 / 10 · rule-coverage 100% · ceiling Documented

15 finding(s): 0 critical, 0 high, 11 medium, 4 low.

REDACTED
REDACTED

What to do

  1. Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 517 of the 894 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 31 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

  • The namespaces OpenCvSharp ↔ OpenCvSharp.Aruco ↔ OpenCvSharp.Detail ↔ OpenCvSharp.Dnn ↔ OpenCvSharp.Face ↔ OpenCvSharp.Flann ↔ OpenCvSharp.ImgHash ↔ OpenCvSharp.Internal ↔ OpenCvSharp.Internal.Util ↔ OpenCvSharp.Internal.Vectors ↔ OpenCvSharp.LineDescriptor ↔ OpenCvSharp.ML ↔ OpenCvSharp.OptFlow ↔ OpenCvSharp.Text ↔ OpenCvSharp.Tracking ↔ OpenCvSharp.Tracking.Legacy ↔ OpenCvSharp.XFeatures2D ↔ OpenCvSharp.XImgProc ↔ OpenCvSharp.XImgProc.Segmentation ↔ OpenCvSharp.XPhoto depend on each other. The lightest dependency in the cycle is OpenCvSharp → OpenCvSharp.Face (OpenCvSharp.Face → OpenCvSharp.Face.FacemarkKazemi, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/OpenCvSharp/Modules/face/Cv2.Face.cs:11

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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.

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.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/OpenCvSharp/Modules/core/FileNodeIterator.cs:78

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs7.4 / 10Strong✓ Tool-verified

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.

  • The catch-all arm (reached by `Indexed`, `Gdi`, `Alpha`, `PAlpha` and 13 more) throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:33
  • The branch `if (dst.IsSubmatrix())` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:102
  • The branch `if (submat)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. (×2) — src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:372, src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:151
  • The `default:` section (reached by `Indexed`, `Gdi`, `Alpha`, `PAlpha` and 15 more) throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:411
  • The branch `if (src.IsSubmatrix())` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:236
  • `Reset` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/OpenCvSharp/Modules/core/FileNodeIterator.cs:78
  • Code inside a `#if false` block is permanently excluded from the build — disabled code that should be removed or restored. — src/OpenCvSharp/Modules/features/DenseFeatureDetector.cs:1
  • The branch `if (function != FuzzyFunction.Linear)` throws `ArgumentOutOfRangeException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/OpenCvSharp/Modules/fuzzy/Cv2.Fuzzy.cs:108
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×17) — src/OpenCvSharp.Analyzers/RowColNotDisposedAnalyzer.cs:74, src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:333, src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:376, …
  • 13 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:187
  • 6 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp/Cv2/Cv2_core.cs:2691
  • 5 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp/Cv2/Cv2_core.cs:2701
  • 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp/Internal/PInvoke/NativeMethods/core/NativeMethods_core.cs:67
  • 9 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:14
  • 10 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:24
  • 7 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). (×3) — src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:60, src/OpenCvSharp/Modules/img_hash/AverageHash.cs:36, src/OpenCvSharp/Modules/img_hash/BlockMeanHash.cs:63
  • 8 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:68
  • 43 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp/Modules/core/Struct/MatType.cs:246
  • 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/OpenCvSharp/Modules/core/Struct/RotatedRect.cs:92
  • A test is skipped ("heavy") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — test/OpenCvSharp.Tests/core/MatTest.cs:1256
  • A test is skipped ("GUI Test") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — test/OpenCvSharp.Tests/highgui/TrackbarTest.cs:10

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

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.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P10 · Library API & versioning9.2 / 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.

  • 14 public types in `OpenCvSharp.Internal` are marked as implementation by their own namespace, folder or name: `ExceptionHandler` (src/OpenCvSharp/Internal/PInvoke/ExceptionHandler.cs:11, `Internal`), `ExceptionStatus` (src/OpenCvSharp/Internal/PInvoke/ExceptionStatus.cs:6, `Internal`), `CvGPCTrainingParams` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_optflow_gpc.cs:17, `Internal`), `CvGPCMatchingParams` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_optflow_gpc.cs:31, `Internal`), `NativeMethods` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/bioinspired/NativeMethods_bioinspired.cs:10, `Internal`), `FacemarkLBFParamsData` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/face/FacemarkParamsData.cs:12, `Internal`), `FacemarkAAMParamsData` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/face/FacemarkParamsData.cs:33, `Internal`), `CvColoredKinFuParams` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/rgbd/NativeMethods_rgbd_colored_kinfu.cs:18, `Internal`), and 6 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/OpenCvSharp/Internal/PInvoke/ExceptionHandler.cs:11
  • 4 public types in `OpenCvSharp.Internal.Util` are marked as implementation by their own namespace, folder or name: `ArrayAddress2` (src/OpenCvSharp/Internal/Util/ArrayAddress2.cs:10, `Internal`), `MatTypeMap` (src/OpenCvSharp/Internal/Util/MatTypeMap.cs:10, `Internal`), `ReadOnlyArray2D` (src/OpenCvSharp/Internal/Util/ReadOnlyArray2D.cs:7, `Internal`), `SaturateCast` (src/OpenCvSharp/Internal/Util/SaturateCast.cs:4, `Internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/OpenCvSharp/Internal/Util/ArrayAddress2.cs:10
  • 15 public types in `OpenCvSharp.Internal.Vectors` are marked as implementation by their own namespace, folder or name: `IStdVector` (src/OpenCvSharp/Internal/Vectors/IStdVector.cs:6, `Internal`), `StdVector` (src/OpenCvSharp/Internal/Vectors/StdVector.cs:18, `Internal`), `VectorOfDTreesNode` (src/OpenCvSharp/Internal/Vectors/VectorOfDTreesNode.cs:7, `Internal`), `VectorOfImageFeatures` (src/OpenCvSharp/Internal/Vectors/VectorOfImageFeatures.cs:7, `Internal`), `VectorOfKeyLine` (src/OpenCvSharp/Internal/Vectors/VectorOfKeyLine.cs:7, `Internal`), `VectorOfMat` (src/OpenCvSharp/Internal/Vectors/VectorOfMat.cs:5, `Internal`), `VectorOfString` (src/OpenCvSharp/Internal/Vectors/VectorOfString.cs:7, `Internal`), `VectorOfVectorByte` (src/OpenCvSharp/Internal/Vectors/VectorOfVectorByte.cs:7, `Internal`), and 7 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/OpenCvSharp/Internal/Vectors/IStdVector.cs:6
  • 1 public type in `OpenCvSharp.DnnSuperres` is marked as implementation by its own namespace, folder or name: `DnnSuperResImpl` (src/OpenCvSharp/Modules/dnn_superres/DnnSuperResImpl.cs:21, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/OpenCvSharp/Modules/dnn_superres/DnnSuperResImpl.cs:21
  • 42 public types in `OpenCvSharp.Detail` are marked as implementation by their own namespace, folder or name: `AffineBasedEstimator` (src/OpenCvSharp/Modules/stitching/AffineBasedEstimator.cs:9, `Detail`), `AffineBestOf2NearestMatcher` (src/OpenCvSharp/Modules/stitching/AffineBestOf2NearestMatcher.cs:13, `Detail`), `BestOf2NearestMatcher` (src/OpenCvSharp/Modules/stitching/BestOf2NearestMatcher.cs:9, `Detail`), `BestOf2NearestRangeMatcher` (src/OpenCvSharp/Modules/stitching/BestOf2NearestRangeMatcher.cs:13, `Detail`), `BlenderType` (src/OpenCvSharp/Modules/stitching/Blender.cs:8, `Detail`), `Blender` (src/OpenCvSharp/Modules/stitching/Blender.cs:20, `Detail`), `BlocksChannelsCompensator` (src/OpenCvSharp/Modules/stitching/BlocksChannelsCompensator.cs:9, `Detail`), `BlocksCompensator` (src/OpenCvSharp/Modules/stitching/BlocksCompensator.cs:10, `Detail`), and 34 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/OpenCvSharp/Modules/stitching/AffineBasedEstimator.cs:9
  • `OpenCvSharp.BroxOpticalFlow` (src/OpenCvSharp/Modules/superres/BroxOpticalFlow.cs:10) is public, and the library's own code uses it, but no other project in this repository uses it (read: `OpenCvSharp.AvaloniaExtensions`, `OpenCvSharp.GdipExtensions`, `OpenCvSharp.Tests`, `OpenCvSharp.Tests.Avalonia`, `OpenCvSharp.Tests.NativeAot`, `OpenCvSharp.Tests.Windows`, `OpenCvSharp.WpfExtensions`) 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/OpenCvSharp/Modules/superres/BroxOpticalFlow.cs:10
  • `OpenCvSharp.DualTVL1OpticalFlow` (src/OpenCvSharp/Modules/superres/DualTVL1OpticalFlow.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `OpenCvSharp.AvaloniaExtensions`, `OpenCvSharp.GdipExtensions`, `OpenCvSharp.Tests`, `OpenCvSharp.Tests.Avalonia`, `OpenCvSharp.Tests.NativeAot`, `OpenCvSharp.Tests.Windows`, `OpenCvSharp.WpfExtensions`) 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/OpenCvSharp/Modules/superres/DualTVL1OpticalFlow.cs:9
  • `OpenCvSharp.PyrLKOpticalFlow` (src/OpenCvSharp/Modules/superres/PyrLKOpticalFlow.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `OpenCvSharp.AvaloniaExtensions`, `OpenCvSharp.GdipExtensions`, `OpenCvSharp.Tests`, `OpenCvSharp.Tests.Avalonia`, `OpenCvSharp.Tests.NativeAot`, `OpenCvSharp.Tests.Windows`, `OpenCvSharp.WpfExtensions`) 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/OpenCvSharp/Modules/superres/PyrLKOpticalFlow.cs:9
  • `OpenCvSharp.SuperResFarnebackOpticalFlow` (src/OpenCvSharp/Modules/superres/SuperResFarnebackOpticalFlow.cs:11) is public, and the library's own code uses it, but no other project in this repository uses it (read: `OpenCvSharp.AvaloniaExtensions`, `OpenCvSharp.GdipExtensions`, `OpenCvSharp.Tests`, `OpenCvSharp.Tests.Avalonia`, `OpenCvSharp.Tests.NativeAot`, `OpenCvSharp.Tests.Windows`, `OpenCvSharp.WpfExtensions`) 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/OpenCvSharp/Modules/superres/SuperResFarnebackOpticalFlow.cs:11

What to do

  • Hide `OpenCvSharp.Internal` (`ExceptionHandler`, `ExceptionStatus`, `CvGPCTrainingParams`, `CvGPCMatchingParams`, `NativeMethods`, `FacemarkLBFParamsData`, `FacemarkAAMParamsData`, `CvColoredKinFuParams`, and 6 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `OpenCvSharp.Internal.Util` (`ArrayAddress2`, `MatTypeMap`, `ReadOnlyArray2D`, `SaturateCast`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `OpenCvSharp.Internal.Vectors` (`IStdVector`, `StdVector`, `VectorOfDTreesNode`, `VectorOfImageFeatures`, `VectorOfKeyLine`, `VectorOfMat`, `VectorOfString`, `VectorOfVectorByte`, and 7 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `OpenCvSharp.DnnSuperres` (`DnnSuperResImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `OpenCvSharp.Detail` (`AffineBasedEstimator`, `AffineBestOf2NearestMatcher`, `BestOf2NearestMatcher`, `BestOf2NearestRangeMatcher`, `BlenderType`, `Blender`, `BlocksChannelsCompensator`, `BlocksCompensator`, and 34 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Make `OpenCvSharp.BroxOpticalFlow` 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 `OpenCvSharp.DualTVL1OpticalFlow` 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 `OpenCvSharp.PyrLKOpticalFlow` 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 `OpenCvSharp.SuperResFarnebackOpticalFlow` 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.
P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging or diagnostics emission found. This codebase ships libraries rather than a process it operates, so structured logging itself is the HOST application's to configure — but a library that emits nothing at all gives its consumers no way to see what it did.

What to do

  • Give consumers a diagnostics seam rather than taking a logging dependency: emit through an `EventSource`/`ActivitySource` (or `DiagnosticSource`) the host can subscribe to, accept an optional logger/handler on your options object, or document the hook you already expose.
  • Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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.

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness7.9 / 10Strong✓ Tool-verified

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.

  • `CharucoParameters` declares a finalizer (line 36), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/OpenCvSharp/Modules/aruco/CharucoParameters.cs:36
  • `ImageFeatures` declares a finalizer (line 36), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/OpenCvSharp/Modules/stitching/ImageFeatures.cs:36

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.
X20 · Mistyped argument guard1.8 / 10Critical✓ Tool-verified

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.

  • The guard on line 355 rejects `windowName` and line 356 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(windowName)` is true of a value that is NOT null: it is satisfied by an EMPTY `windowName`, and on that path `windowName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_highgui.cs:356
  • The guard on line 414 rejects `windowName` and line 415 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(windowName)` is true of a value that is NOT null: it is satisfied by an EMPTY `windowName`, and on that path `windowName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_highgui.cs:415
  • The guard on line 459 rejects `windowName` and line 460 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(windowName)` is true of a value that is NOT null: it is satisfied by an EMPTY `windowName`, and on that path `windowName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_highgui.cs:460
  • The guard on line 17 rejects `fileName` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:18
  • The guard on line 35 rejects `filename` and line 36 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:36
  • The guard on line 54 rejects `filename` and line 55 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. (×2) — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:55, src/OpenCvSharp/Modules/imgcodecs/ImageCollection.cs:55
  • The guard on line 82 rejects `filename` and line 83 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:83
  • The guard on line 108 rejects `filename` and line 109 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:109
  • The guard on line 141 rejects `fileName` and line 142 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:142
  • The guard on line 186 rejects `filename` and line 187 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:187
  • The guard on line 233 rejects `fileName` and line 234 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:234
  • The guard on line 263 rejects `ext` and line 264 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ext)` is true of a value that is NOT null: it is satisfied by an EMPTY `ext`, and on that path `ext` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:264
  • The guard on line 285 rejects `fileName` and line 286 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:286
  • The guard on line 306 rejects `fileName` and line 307 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:307
  • The guard on line 450 rejects `ext` and line 451 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ext)` is true of a value that is NOT null: it is satisfied by an EMPTY `ext`, and on that path `ext` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:451
  • The guard on line 474 rejects `ext` and line 475 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ext)` is true of a value that is NOT null: it is satisfied by an EMPTY `ext`, and on that path `ext` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:475
  • The guard on line 507 rejects `ext` and line 508 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ext)` is true of a value that is NOT null: it is satisfied by an EMPTY `ext`, and on that path `ext` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:508
  • The guard on line 3082 rejects `text` and line 3083 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(text)` is true of a value that is NOT null: it is satisfied by an EMPTY `text`, and on that path `text` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3083
  • The guard on line 3104 rejects `text` and line 3105 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(text)` is true of a value that is NOT null: it is satisfied by an EMPTY `text`, and on that path `text` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3105
  • The guard on line 104 rejects `fileName` and line 105 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/core/Mat/Mat.cs:105
  • The guard on line 70 rejects `descriptorMatcherType` and line 71 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(descriptorMatcherType)` is true of a value that is NOT null: it is satisfied by an EMPTY `descriptorMatcherType`, and on that path `descriptorMatcherType` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:71
  • The guard on line 252 rejects `fileName` and line 253 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/features/Feature2D.cs:253
  • The guard on line 266 rejects `fileName` and line 267 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/features/Feature2D.cs:267
  • The guard on line 77 rejects `filename` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/flann/Index.cs:78
  • The guard on line 271 rejects `filename` and line 272 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/flann/Index.cs:272
  • The guard on line 27 rejects `fileName` and line 28 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/flann/IndexParams/SavedIndexParams.cs:28
  • The guard on line 302 rejects `name` and line 303 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/highgui/Window.cs:303
  • The guard on line 32 rejects `filename` and line 33 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/imgcodecs/ImageCollection.cs:33
  • The guard on line 31 rejects `fileName` and line 32 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:32
  • The guard on line 77 rejects `fileName` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:78
  • The guard on line 34 rejects `modelFilePath` and line 35 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(modelFilePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `modelFilePath`, and on that path `modelFilePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/quality/QualityBRISQUE.cs:35
  • The guard on line 36 rejects `rangeFilePath` and line 37 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(rangeFilePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `rangeFilePath`, and on that path `rangeFilePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/quality/QualityBRISQUE.cs:37
  • The guard on line 75 rejects `modelFilePath` and line 76 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(modelFilePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `modelFilePath`, and on that path `modelFilePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/quality/QualityBRISQUE.cs:76
  • The guard on line 77 rejects `rangeFilePath` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(rangeFilePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `rangeFilePath`, and on that path `rangeFilePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/quality/QualityBRISQUE.cs:78
  • The guard on line 44 rejects `fileName` and line 45 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/superres/FrameSource.cs:45
  • The guard on line 61 rejects `fileName` and line 62 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/superres/FrameSource.cs:62
  • The guard on line 223 rejects `fileName` and line 224 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/videoio/VideoCapture.cs:224
  • The guard on line 256 rejects `fileName` and line 257 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/videoio/VideoCapture.cs:257
  • The guard on line 285 rejects `fileName` and line 285 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/OpenCvSharp/Modules/videoio/VideoCapture.cs:285

What to do

  • Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
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.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.0 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — src/OpenCvSharp/Cv2/Cv2_highgui.cs:87, src/OpenCvSharp/Cv2/Cv2_highgui.cs:110, src/OpenCvSharp/Modules/tracking/TrackerKCF.cs:117

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types6.4 / 10Adequate✓ Tool-verified

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.

  • 5/9 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 `!`.

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.

LensScoreRatingImpact
Code Health45.2Weak — gated by D17Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96.0ExemplarySolid.
Maturity60.6Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness47.2Weak — gated by D13, P2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security47.7Weak — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
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.

  • SC1 Supply-chain hygiene — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 5 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 — 58 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
  • AX2 Stateful singletons — no singleton implementations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:71 -------------------- 69 | FROM opencv-builder AS opencvsharp-builder 70 | 71 | >>> COPY src/ /opencvsharp/src/ 72 | 73 | RUN --mount=type=cache,target=/root/.ccache \ -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref b581b959-5935-43bc-add4-31adcbf6cd54::65wyswjiz03ixzcv2iogdv9qv: "": not found; likely cause (not identified): a file the REDACTED copies (`cmake/opencv_build_options_slim.cmake`) is not in the build context; the repository declares git submodules, and a submodule our checkout did not fetch would explain it; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — 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.
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • 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) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (5 value object(s))
  • 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
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
  • 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.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • 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
  • 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.
  • 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.

Critical — 259 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 107 more in this group — see findings.md.
D17 · Explicit Debt · FileScopedPragmaDisable · ×34
  • FileScopedPragmaDisable src/OpenCvSharp/Fundamentals/CvObject.cs:1 — #pragma warning disable CA2216 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_barcode.cs:5 — #pragma warning disable CA1707 // Underscore — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_stdvector.cs:8 — #pragma warning disable CA1707 // Underscore — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_wechat_qrcode.cs:5 — #pragma warning disable CA1707 // Underscore — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_xphoto.cs:6 — #pragma warning disable CA1707 // Underscore — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/videoio/Enum/VideoCaptureAPIs.cs:3 — #pragma warning disable CA1707 // Underscore — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Internal/PInvoke/NativeMethods/face/NativeMethods_face_Additional.cs:6 — #pragma warning disable CA2101 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/core/Enum/BorderTypes.cs:3 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/core/Enum/DecompTypes.cs:1 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/flann/FlannDistance.cs:2 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/imgcodecs/Enum/ImwriteFlags.cs:2 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/imgproc/Enum/ColorConversionCodes.cs:4 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/imgproc/Enum/HistCompMethods.cs:3 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/imgproc/Enum/LineTypes.cs:4 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/imgproc/Enum/PixelConnectivity.cs:2 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/ml/EM.cs:338 — #pragma warning disable CA1027 // Mark enums with FlagsAttribute — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/flann/FlannDistance.cs:3 — #pragma warning disable CA1069 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/geometry/UsacParams.cs:8 — #pragma warning disable CA1805 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:1 — #pragma warning disable CA5394 // Do not use insecure randomness — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable test/OpenCvSharp.Tests/calib3d/GeometryFunctionsTest.cs:4 — #pragma warning disable CA5394 // Do not use insecure randomness — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable test/OpenCvSharp.Tests/calib3d/SACSegmentationTest.cs:5 — #pragma warning disable CA5394 // Do not use insecure randomness — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable test/OpenCvSharp.Tests/core/CoreTest.cs:4 — #pragma warning disable CA5394 // Do not use insecure randomness — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable test/OpenCvSharp.Tests/core/VecTest.cs:4 — #pragma warning disable CA5394 // Do not use insecure randomness — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable test/OpenCvSharp.Tests/line_descriptor/LSDDetectorTest.cs:1 — #pragma warning disable CA5394 // Do not use insecure randomness — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable test/OpenCvSharp.Tests/ml/EMTest.cs:4 — #pragma warning disable CA5394 // Do not use insecure randomness — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • + 9 more in this group — see findings.md.
D17 · Explicit Debt · NoWarnInCsproj · ×29
  • NoWarnInCsproj — 11 warning codes suppressed in one element src/OpenCvSharp/OpenCvSharp.csproj:83 — A single <NoWarn> suppresses 11 warning codes (1701;1702;CA1303;CA1707;CA1814;CA1401;CA1720;CA2213;CA1510;CA1512;CA1513) in one stroke — one team-wide decision, not 11 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj src/OpenCvSharp.Analyzers/OpenCvSharp.Analyzers.csproj:21 — CS1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
  • NoWarnInCsproj src/OpenCvSharp.AvaloniaExtensions/OpenCvSharp.AvaloniaExtensions.csproj:60 — CA1303 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.GdipExtensions/OpenCvSharp.GdipExtensions.csproj:64 — CA1303 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj:56 — CA1303 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests/OpenCvSharp.Tests.csproj:68 — CA1303 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests.Avalonia/OpenCvSharp.Tests.Avalonia.csproj:35 — CA1303 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests.Wasm/OpenCvSharp.Tests.Wasm.csproj:8 — CA1303 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests.Windows/OpenCvSharp.Tests.Windows.csproj:43 — CA1303 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.AvaloniaExtensions/OpenCvSharp.AvaloniaExtensions.csproj:60 — CA1510 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.GdipExtensions/OpenCvSharp.GdipExtensions.csproj:64 — CA1510 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj:56 — CA1510 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests/OpenCvSharp.Tests.csproj:72 — CA1510 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests.Avalonia/OpenCvSharp.Tests.Avalonia.csproj:35 — CA1510 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.AvaloniaExtensions/OpenCvSharp.AvaloniaExtensions.csproj:60 — CA1512 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.GdipExtensions/OpenCvSharp.GdipExtensions.csproj:64 — CA1512 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj:56 — CA1512 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests/OpenCvSharp.Tests.csproj:72 — CA1512 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests.Avalonia/OpenCvSharp.Tests.Avalonia.csproj:35 — CA1512 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.AvaloniaExtensions/OpenCvSharp.AvaloniaExtensions.csproj:60 — CA1513 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.GdipExtensions/OpenCvSharp.GdipExtensions.csproj:64 — CA1513 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj:56 — CA1513 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests/OpenCvSharp.Tests.csproj:72 — CA1513 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests.Avalonia/OpenCvSharp.Tests.Avalonia.csproj:35 — CA1513 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/OpenCvSharp.Tests/OpenCvSharp.Tests.csproj:68 — CA1814 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • + 4 more in this group — see findings.md.
D17 · Explicit Debt · WriteOnlyPrivateField · ×12
  • WriteOnlyPrivateField src/OpenCvSharp/Modules/features/FlannBasedMatcher.cs:13 — private IndexParams? indexParams — 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/OpenCvSharp/Modules/features/FlannBasedMatcher.cs:14 — private SearchParams? searchParams — 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/OpenCvSharp/Modules/stitching/Stitcher.cs:480 — private Feature2D? featuresFinderRef — 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/OpenCvSharp/Modules/stitching/Stitcher.cs:481 — private FeaturesMatcher? featuresMatcherRef — 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/OpenCvSharp/Modules/stitching/Stitcher.cs:482 — private BundleAdjusterBase? bundleAdjusterRef — 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/OpenCvSharp/Modules/stitching/Stitcher.cs:483 — private WarperCreator? warperRef — 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/OpenCvSharp/Modules/stitching/Stitcher.cs:484 — private ExposureCompensator? exposureCompensatorRef — 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/OpenCvSharp/Modules/stitching/Stitcher.cs:485 — private SeamFinder? seamFinderRef — 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/OpenCvSharp/Modules/stitching/Stitcher.cs:486 — private Blender? blenderRef — 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 test/OpenCvSharp.Tests/core/MatTest.cs:11 — private ITestOutputHelper testOutputHelper — 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 test/OpenCvSharp.Tests/dnn/NetTest.cs:8 — private ITestOutputHelper testOutputHelper — 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 test/OpenCvSharp.Tests/ml/ANN_MLPTest.cs:10 — private ITestOutputHelper testOutputHelper — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · AnalyzerSeverityNone · ×5
  • AnalyzerSeverityNone .editorconfig:63 — CA1711 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:70 — CA1014 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:73 — IDE0079 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone test/.editorconfig:4 — CA1861 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone test/.editorconfig:7 — CA5394 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
D28 · Secrets (history) · High secret · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · Secret Scanning · Leaked secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×3
  • EmptyCatchBlock src/OpenCvSharp/Cv2/Cv2_highgui.cs:87 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/OpenCvSharp/Cv2/Cv2_highgui.cs:110 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/OpenCvSharp/Modules/tracking/TrackerKCF.cs:117 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 14 files · ×2
  • FileScopedPragmaDisable repeated across 14 files src/OpenCvSharp/Internal/PInvoke/NativeMethods/bioinspired/NativeMethods_bioinspired.cs:5 — The identical FileScopedPragmaDisable (`#pragma warning disable CA1401`) appears in 14 files (14 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 14 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
  • FileScopedPragmaDisable repeated across 14 files src/OpenCvSharp/Internal/PInvoke/NativeMethods/bioinspired/NativeMethods_bioinspired.cs:6 — The identical FileScopedPragmaDisable (`#pragma warning disable IDE1006`) appears in 14 files (14 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 14 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/OpenCvSharp/Modules/face/Cv2.Face.cs:11 — The namespaces OpenCvSharp ↔ OpenCvSharp.Aruco ↔ OpenCvSharp.Detail ↔ OpenCvSharp.Dnn ↔ OpenCvSharp.Face ↔ OpenCvSharp.Flann ↔ OpenCvSharp.ImgHash ↔ OpenCvSharp.Internal ↔ OpenCvSharp.Internal.Util ↔ OpenCvSharp.Internal.Vectors ↔ OpenCvSharp.LineDescriptor ↔ OpenCvSharp.ML ↔ OpenCvSharp.OptFlow ↔ OpenCvSharp.Text ↔ OpenCvSharp.Tracking ↔ OpenCvSharp.Tracking.Legacy ↔ OpenCvSharp.XFeatures2D ↔ OpenCvSharp.XImgProc ↔ OpenCvSharp.XImgProc.Segmentation ↔ OpenCvSharp.XPhoto depend on each other. The lightest dependency in the cycle is OpenCvSharp → OpenCvSharp.Face (OpenCvSharp.Face → OpenCvSharp.Face.FacemarkKazemi, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 185 files · ×1
  • FileScopedPragmaDisable repeated across 185 files src/OpenCvSharp/Internal/PInvoke/ExceptionStatus.cs:8 — The identical FileScopedPragmaDisable (`#pragma warning disable 1591`) appears in 185 files (186 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 186 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 146 files · ×1
  • FileScopedPragmaDisable repeated across 146 files src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_aruco.cs:6 — The identical FileScopedPragmaDisable (`#pragma warning disable CA1401 // P/Invokes should not be visible`) appears in 146 files (146 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 146 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 125 files · ×1
  • FileScopedPragmaDisable repeated across 125 files src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_aruco.cs:7 — The identical FileScopedPragmaDisable (`#pragma warning disable IDE1006 // Naming style`) appears in 125 files (125 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 125 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 49 files · ×1
  • FileScopedPragmaDisable repeated across 49 files src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_barcode.cs:6 — The identical FileScopedPragmaDisable (`#pragma warning disable CA2101 // Specify marshaling for P/Invoke string arguments`) appears in 49 files (49 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 49 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 28 files · ×1
  • FileScopedPragmaDisable repeated across 28 files src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_xfeatures2d_BOW.cs:6 — The identical FileScopedPragmaDisable (`#pragma warning disable CA1720 // Identifiers should not contain type names`) appears in 28 files (28 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 28 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 12 files · ×1
  • FileScopedPragmaDisable repeated across 12 files src/OpenCvSharp/Modules/aruco/DetectorParameters.cs:7 — The identical FileScopedPragmaDisable (`#pragma warning disable CA1815`) appears in 12 files (12 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 12 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 11 files · ×1
  • FileScopedPragmaDisable repeated across 11 files src/OpenCvSharp/Modules/calib/Enum/FishEyeCalibrationFlags.cs:6 — The identical FileScopedPragmaDisable (`#pragma warning disable CS1591`) appears in 11 files (11 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 11 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 30 files · ×1
  • FileScopedPragmaDisable repeated across 30 files src/OpenCvSharp/Modules/core/Enum/CovarFlags.cs:1 — The identical FileScopedPragmaDisable (`#pragma warning disable CA1008 // Enums should have zero value`) appears in 30 files (30 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 30 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 18 files · ×1
  • FileScopedPragmaDisable repeated across 18 files src/OpenCvSharp/Modules/core/Mat/Mat.cs:2659 — The identical FileScopedPragmaDisable (`#pragma warning disable CA1034`) appears in 18 files (20 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 20 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 43 files · ×1
  • FileScopedPragmaDisable repeated across 43 files src/OpenCvSharp/Modules/core/Struct/DMatch.cs:3 — The identical FileScopedPragmaDisable (`#pragma warning disable CA1051`) appears in 43 files (43 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 43 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · FileScopedPragmaDisable repeated across 10 files · ×1
  • FileScopedPragmaDisable repeated across 10 files test/OpenCvSharp.Tests/barcode/BarcodeDetectorTest.cs:3 — The identical FileScopedPragmaDisable (`#pragma warning disable CA1707 // Identifiers should not contain underscores`) appears in 10 files (10 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 10 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 680 finding(s)
D10 · Test Quality · No assertions · ×69
  • No assertions: GetPredefinedDictionary test/OpenCvSharp.Tests/aruco/ArucoTest.cs:74 — 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: DrawDetectedCornersCharuco test/OpenCvSharp.Tests/aruco/ArucoTest.cs:860 — 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: DrawDetectedDiamonds test/OpenCvSharp.Tests/aruco/ArucoTest.cs:879 — 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: Constructor_Default test/OpenCvSharp.Tests/barcode/BarcodeDetectorTest.cs:16 — 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: Constructor_EmptyPaths test/OpenCvSharp.Tests/barcode/BarcodeDetectorTest.cs:25 — 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: SetDownsamplingThreshold_ValidValue test/OpenCvSharp.Tests/barcode/BarcodeDetectorTest.cs:47 — 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: SetGradientThreshold_ValidValue test/OpenCvSharp.Tests/barcode/BarcodeDetectorTest.cs:54 — 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: SetDetectorScales_ValidSizes test/OpenCvSharp.Tests/barcode/BarcodeDetectorTest.cs:61 — 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: ProjectPoints test/OpenCvSharp.Tests/calib3d/Calib3dTest.cs:408 — 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: FishEyeProjectPoints test/OpenCvSharp.Tests/calib3d/Calib3dTest.cs:454 — 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: SolvePnPTestByArray test/OpenCvSharp.Tests/calib3d/Calib3dTest.cs:497 — 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: SolvePnPTestByMat test/OpenCvSharp.Tests/calib3d/Calib3dTest.cs:600 — 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: Rectify3Collinear test/OpenCvSharp.Tests/calib3d/StereoRectificationTest.cs:83 — 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: PrintBuildInformation test/OpenCvSharp.Tests/core/BuildConfigurationTest.cs:25 — 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: CreateAndDispose test/OpenCvSharp.Tests/core/LDATest.cs:8 — 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: MatOfTDispose test/OpenCvSharp.Tests/core/MatTest.cs:41 — 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: Reserve test/OpenCvSharp.Tests/core/MatTest.cs:454 — 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: NewAndDispose test/OpenCvSharp.Tests/core/UMatTest.cs:9 — 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: GetThreadNum test/OpenCvSharp.Tests/core/UtilityTest.cs:31 — 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: GetVersionMajor test/OpenCvSharp.Tests/core/UtilityTest.cs:50 — 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: GetVersionMinor test/OpenCvSharp.Tests/core/UtilityTest.cs:54 — 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: GetVersionRevision test/OpenCvSharp.Tests/core/UtilityTest.cs:58 — 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: GetTickCount test/OpenCvSharp.Tests/core/UtilityTest.cs:62 — 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: GetTickFrequency test/OpenCvSharp.Tests/core/UtilityTest.cs:66 — 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: GetCpuTickCount test/OpenCvSharp.Tests/core/UtilityTest.cs:70 — 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.
  • + 44 more in this group — see findings.md.
D17 · Explicit Debt · BarePragmaDisable · ×49
  • BarePragmaDisable src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:16 — #pragma warning disable CA1810 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Internal/Util/ReadOnlyArray2D.cs:32 — #pragma warning disable CA1721 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/Mat.cs:338 — #pragma warning disable CA1508 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/Mat.cs:375 — #pragma warning disable CA1508 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/Mat.cs:420 — #pragma warning disable CA1508 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/Mat.cs:439 — #pragma warning disable CA1508 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:238 — #pragma warning disable CA1508 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/Mat.cs:3352 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:529 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:542 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:574 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:610 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/UMat.cs:1345 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable test/OpenCvSharp.Tests/core/MatTest.cs:44 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable test/OpenCvSharp.Tests/photo/CalibrateExposuresTest.cs:9 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable test/OpenCvSharp.Tests/photo/MergeExposuresTest.cs:7 — #pragma warning disable CA2000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:180 — #pragma warning disable CA1000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:200 — #pragma warning disable CA1000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:231 — #pragma warning disable CA1000 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Struct/Size.cs:34 — #pragma warning disable CA2225 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Struct/Size2d.cs:24 — #pragma warning disable CA2225 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/core/Struct/Size2f.cs:35 — #pragma warning disable CA2225 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/features/SimpleBlobDetector.cs:244 — #pragma warning disable CA1051 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/ml/DTrees.cs:313 — #pragma warning disable CA1051 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/OpenCvSharp/Modules/tracking/Legacy/TrackerBoosting.cs:45 — #pragma warning disable CA1051 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • + 24 more in this group — see findings.md.
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×40
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_highgui.cs:356 — The guard on line 355 rejects `windowName` and line 356 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(windowName)` is true of a value that is NOT null: it is satisfied by an EMPTY `windowName`, and on that path `windowName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_highgui.cs:415 — The guard on line 414 rejects `windowName` and line 415 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(windowName)` is true of a value that is NOT null: it is satisfied by an EMPTY `windowName`, and on that path `windowName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_highgui.cs:460 — The guard on line 459 rejects `windowName` and line 460 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(windowName)` is true of a value that is NOT null: it is satisfied by an EMPTY `windowName`, and on that path `windowName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:18 — The guard on line 17 rejects `fileName` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:36 — The guard on line 35 rejects `filename` and line 36 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:55 — The guard on line 54 rejects `filename` and line 55 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:83 — The guard on line 82 rejects `filename` and line 83 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:109 — The guard on line 108 rejects `filename` and line 109 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:142 — The guard on line 141 rejects `fileName` and line 142 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:187 — The guard on line 186 rejects `filename` and line 187 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:234 — The guard on line 233 rejects `fileName` and line 234 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:264 — The guard on line 263 rejects `ext` and line 264 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ext)` is true of a value that is NOT null: it is satisfied by an EMPTY `ext`, and on that path `ext` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:286 — The guard on line 285 rejects `fileName` and line 286 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:307 — The guard on line 306 rejects `fileName` and line 307 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:451 — The guard on line 450 rejects `ext` and line 451 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ext)` is true of a value that is NOT null: it is satisfied by an EMPTY `ext`, and on that path `ext` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:475 — The guard on line 474 rejects `ext` and line 475 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ext)` is true of a value that is NOT null: it is satisfied by an EMPTY `ext`, and on that path `ext` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:508 — The guard on line 507 rejects `ext` and line 508 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ext)` is true of a value that is NOT null: it is satisfied by an EMPTY `ext`, and on that path `ext` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3083 — The guard on line 3082 rejects `text` and line 3083 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(text)` is true of a value that is NOT null: it is satisfied by an EMPTY `text`, and on that path `text` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3105 — The guard on line 3104 rejects `text` and line 3105 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(text)` is true of a value that is NOT null: it is satisfied by an EMPTY `text`, and on that path `text` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Modules/core/Mat/Mat.cs:105 — The guard on line 104 rejects `fileName` and line 105 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:71 — The guard on line 70 rejects `descriptorMatcherType` and line 71 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(descriptorMatcherType)` is true of a value that is NOT null: it is satisfied by an EMPTY `descriptorMatcherType`, and on that path `descriptorMatcherType` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Modules/features/Feature2D.cs:253 — The guard on line 252 rejects `fileName` and line 253 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Modules/features/Feature2D.cs:267 — The guard on line 266 rejects `fileName` and line 267 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Modules/flann/Index.cs:78 — The guard on line 77 rejects `filename` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/OpenCvSharp/Modules/flann/Index.cs:272 — The guard on line 271 rejects `filename` and line 272 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • + 15 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×30
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:517 — src/OpenCvSharp/Cv2/Cv2_core.cs:517-525 | src/OpenCvSharp/Cv2/Cv2_ptcloud_processing.cs:32-38 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/xfeatures2d/VGG.cs:32 — src/OpenCvSharp/Modules/xfeatures2d/VGG.cs:32-39 | src/OpenCvSharp/Modules/bgsegm/BackgroundSubtractorCNT.cs:22-28 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1282 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1282-1290 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:704-710 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1305 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1305-1311 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:1019-1025 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:48 — src/OpenCvSharp/Cv2/Cv2_core.cs:48-56 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:145-151 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:668 — src/OpenCvSharp/Cv2/Cv2_core.cs:668-674 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1709-1715 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:507 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:507-513 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:810-817 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/core/LDA.cs:35 — src/OpenCvSharp/Modules/core/LDA.cs:35-41 | src/OpenCvSharp/Modules/core/PCA.cs:32-38 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/plot/Plot2d.cs:36 — src/OpenCvSharp/Modules/plot/Plot2d.cs:36-44 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2343-2349 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:437 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:437-445 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:234-240 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/features/ORB.cs:60 — src/OpenCvSharp/Modules/features/ORB.cs:60-69 | src/OpenCvSharp/Modules/xfeatures2d/BRISK.cs:26-32 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:2175 — src/OpenCvSharp/Cv2/Cv2_core.cs:2175-2181 | src/OpenCvSharp/Modules/core/PCA.cs:159-166 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:227 — src/OpenCvSharp/Cv2/Cv2_core.cs:227-235 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1033-1039 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:2822 — src/OpenCvSharp/Cv2/Cv2_core.cs:2822-2828 | src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:131-137 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1076 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1076-1082 | src/OpenCvSharp/Modules/xphoto/Cv2.XPhoto.cs:183-189 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/core/InputArray.cs:294 — src/OpenCvSharp/Modules/core/InputArray.cs:294-303 | src/OpenCvSharp/Modules/imgproc/Moments.cs:81-87 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:190 — src/OpenCvSharp/Cv2/Cv2_core.cs:190-196 | src/OpenCvSharp/Modules/ptcloud/Viz3d.cs:120-126 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:356 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:356-363 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:860-866 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/core/LDA.cs:168 — src/OpenCvSharp/Modules/core/LDA.cs:168-177 | src/OpenCvSharp/Modules/core/PCA.cs:185-191 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:137 — src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:137-143 | src/OpenCvSharp/Modules/dnn/Net.cs:66-73 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/imgproc/Subdiv2D.cs:189 — src/OpenCvSharp/Modules/imgproc/Subdiv2D.cs:189-195 | src/OpenCvSharp/Modules/ximgproc/EdgeDrawing.cs:211-218 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/dnn/Net.cs:534 — src/OpenCvSharp/Modules/dnn/Net.cs:534-543 | src/OpenCvSharp/Modules/img_hash/BlockMeanHash.cs:50-56 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:81 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:81-87 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:82-88 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:94 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:94-100 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:95-101 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:735 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:735-741 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:833-839 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×23
  • Edited copy of a member (8 corresponding lines) src/OpenCvSharp/Modules/bioinspired/Retina.cs:16 — src/OpenCvSharp/Modules/bioinspired/Retina.cs:16-23 | src/OpenCvSharp/Modules/bioinspired/TransientAreasSegmentation.cs:16-24 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1921 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1921-1928 | src/OpenCvSharp/Modules/fuzzy/Cv2.Fuzzy.cs:46-56 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/ml/TrainData.cs:81 — src/OpenCvSharp/Modules/ml/TrainData.cs:81-91 | src/OpenCvSharp/Modules/ximgproc/Segmentation/SelectiveSearchSegmentationStrategyMultiple.cs:100-107 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/xfeatures2d/DAISY.cs:35 — src/OpenCvSharp/Modules/xfeatures2d/DAISY.cs:35-43 | src/OpenCvSharp/Modules/xfeatures2d/SURF.cs:32-39 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/fuzzy/Cv2.Fuzzy.cs:23 — src/OpenCvSharp/Modules/fuzzy/Cv2.Fuzzy.cs:23-30 | src/OpenCvSharp/Cv2/Cv2_core.cs:1966-1973 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:50 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:50-57 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:1287-1294 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/photo/ColorCorrectionModel.cs:336 — src/OpenCvSharp/Modules/photo/ColorCorrectionModel.cs:336-344 | src/OpenCvSharp/Modules/ximgproc/FastLineDetector.cs:91-98 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/optflow/Cv2.OptFlow.cs:74 — src/OpenCvSharp/Modules/optflow/Cv2.OptFlow.cs:74-83 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:585-592 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1770 — src/OpenCvSharp/Cv2/Cv2_core.cs:1770-1778 | src/OpenCvSharp/Modules/stitching/Stitcher.cs:365-372 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2380 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2380-2387 | src/OpenCvSharp/Modules/ptcloud/Octree.cs:45-52 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Cv2/Cv2_photo.cs:273 — src/OpenCvSharp/Cv2/Cv2_photo.cs:273-280 | src/OpenCvSharp/Modules/optflow/Cv2.OptFlow.cs:125-134 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:2862 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:2862-2871 | src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:365-372 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/hfs/HfsSegment.cs:197 — src/OpenCvSharp/Modules/hfs/HfsSegment.cs:197-205 | src/OpenCvSharp/Modules/photo/AlignMTB.cs:58-65 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:2851 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:2851-2860 | src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:356-363 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/dnn/Model.cs:138 — src/OpenCvSharp/Modules/dnn/Model.cs:138-145 | src/OpenCvSharp/Modules/dnn/TextRecognitionModel.cs:94-101 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/geometry/SACSegmentation.cs:85 — src/OpenCvSharp/Modules/geometry/SACSegmentation.cs:85-92 | src/OpenCvSharp/Modules/ptcloud/Odometry.cs:137-144 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/stitching/Cv2.Detail.Utilities.cs:95 — src/OpenCvSharp/Modules/stitching/Cv2.Detail.Utilities.cs:95-103 | src/OpenCvSharp/Modules/face/FaceRecognizer/FaceRecognizer.cs:192-199 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/imgcodecs/Animation.cs:105 — src/OpenCvSharp/Modules/imgcodecs/Animation.cs:105-112 | src/OpenCvSharp/Modules/xstereo/QuasiDenseStereo.cs:90-97 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/core/FileStorage.cs:383 — src/OpenCvSharp/Modules/core/FileStorage.cs:383-390 | src/OpenCvSharp/Modules/rgbd/LinemodDetector.cs:215-222 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/imgproc/Model/Line2D.cs:54 — src/OpenCvSharp/Modules/imgproc/Model/Line2D.cs:54-61 | src/OpenCvSharp/Modules/imgproc/Model/Line3D.cs:62-73 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:1297 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:1297-1304 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:726-733 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:373 — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:373-381 | src/OpenCvSharp/Modules/dnn/Net.cs:137-144 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:1329 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:1329-1336 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:758-765 — These two members are one piece of code written twice and then edited apart: 8 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.
D17 · Explicit Debt · TodoComment · ×19
  • TodoComment src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:194 — // TODO src.Palette.Flags & 2 == 2
  • TodoComment src/OpenCvSharp/Internal/Vectors/VectorOfMat.cs:45 — // todo: rsb - should probably generate Mat[] and then get CvPtrs — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenCvSharp/Modules/highgui/Enum/ButtonType.cs:2 — // TODO support createButton — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenCvSharp/Modules/imgcodecs/ImageEncodingParam.cs:6 — // TODO record — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenCvSharp/Modules/quality/QualityMSE.cs:32 — // TODO support InputArrayOfArrays — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/OpenCvSharp/Modules/stitching/Stitcher.cs:202 — // TODO this should be method? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/calib3d/Calib3dTest.cs:169 — // TODO fail on appveyor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/calib3d/Calib3dTest.cs:882 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/imgcodecs/ImgCodecsTest.cs:356 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/imgcodecs/ImgCodecsTest.cs:375 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/imgproc/ImgProcTest.cs:62 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/ml/ANN_MLPTest.cs:53 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/ximgproc/SuperpixelTest.cs:96 — // TODO
  • TodoComment test/OpenCvSharp.Tests/ximgproc/XimgProcTest.cs:76 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/imgcodecs/ImgCodecsTest.cs:64 — // TODO: Fails on AppVeyor (probably this test succeeds only on Japanese Windows)
  • TodoComment test/OpenCvSharp.Tests/imgcodecs/ImgCodecsTest.cs:204 — // TODO: Fails on AppVeyor (probably this test succeeds only on Japanese Windows) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/imgcodecs/ImgCodecsTest.cs:360 — // TODO: Fails on AppVeyor (probably this test succeeds only on Japanese Windows) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/stitching/Cv2DetailTest.cs:13 — //[Fact] // TODO mac test fails — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment test/OpenCvSharp.Tests/xphoto/TonemapDurandTest.cs:31 — // TODO OpenCV bug https://github.com/opencv/opencv_contrib/pull/2398
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×19
  • Edited copy of a member (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2423 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2423-2431 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2446-2454 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2043 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2043-2051 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:1429-1438 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2389 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2389-2397 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2448-2456 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Modules/face/FaceRecognizer/PredictCollector.cs:91 — src/OpenCvSharp/Modules/face/FaceRecognizer/PredictCollector.cs:91-99 | src/OpenCvSharp/Modules/face/FaceRecognizer/PredictCollector.cs:103-111 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:437 — src/OpenCvSharp/Cv2/Cv2_core.cs:437-445 | src/OpenCvSharp/Cv2/Cv2_core.cs:2408-2417 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1476 — src/OpenCvSharp/Cv2/Cv2_core.cs:1476-1484 | src/OpenCvSharp/Cv2/Cv2_photo.cs:201-209 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:172 — src/OpenCvSharp/Cv2/Cv2_core.cs:172-180 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1115-1123 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1746 — src/OpenCvSharp/Cv2/Cv2_core.cs:1746-1754 | src/OpenCvSharp/Cv2/Cv2_core.cs:1875-1883 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:221 — src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:221-230 | src/OpenCvSharp/Modules/ptcloud/Octree.cs:168-176 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1624 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1624-1632 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2829-2837 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.cs:109 — src/OpenCvSharp/Cv2/Cv2_calib.cs:109-117 | src/OpenCvSharp/Cv2/Cv2_core.cs:1790-1798 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Modules/core/Mat/UMat.cs:1342 — src/OpenCvSharp/Modules/core/Mat/UMat.cs:1342-1350 | src/OpenCvSharp/Modules/core/Mat/Mat.cs:3349-3357 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Modules/text/ERFilter.cs:58 — src/OpenCvSharp/Modules/text/ERFilter.cs:58-67 | src/OpenCvSharp/Modules/features/GFTTDetector.cs:25-33 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2073 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2073-2081 | src/OpenCvSharp/Cv2/Cv2_objdetect.cs:160-168 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:898 — src/OpenCvSharp/Cv2/Cv2_core.cs:898-907 | src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:342-350 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1677 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1677-1685 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2114-2123 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2236 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2236-2244 | src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:214-222 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Modules/dnn/Layer.cs:38 — src/OpenCvSharp/Modules/dnn/Layer.cs:38-46 | src/OpenCvSharp/Modules/imgcodecs/Animation.cs:114-122 — These two members are one piece of code written twice and then edited apart: 9 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 (9 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:1345 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:1345-1353 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:774-782 — These two members are one piece of code written twice and then edited apart: 9 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.
D17 · Explicit Debt · CommentedOutCode · ×17
  • CommentedOutCode src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:187 — 13 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Cv2/Cv2_core.cs:2691 — 6 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Cv2/Cv2_core.cs:2701 — 5 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Internal/PInvoke/NativeMethods/core/NativeMethods_core.cs:67 — 4 consecutive commented-code lines
  • CommentedOutCode test/OpenCvSharp.Tests/core/MatTest.cs:1239 — 4 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:14 — 9 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:24 — 10 consecutive commented-code lines
  • CommentedOutCode test/OpenCvSharp.Tests/calib3d/Calib3dTest.cs:884 — 10 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:60 — 7 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Modules/img_hash/AverageHash.cs:36 — 7 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Modules/img_hash/BlockMeanHash.cs:63 — 7 consecutive commented-code lines
  • CommentedOutCode test/OpenCvSharp.Tests/features/FlannBasedMatcherTest.cs:32 — 7 consecutive commented-code lines
  • CommentedOutCode test/OpenCvSharp.Tests/features/FlannBasedMatcherTest.cs:66 — 7 consecutive commented-code lines
  • CommentedOutCode test/OpenCvSharp.Tests/features/FlannBasedMatcherTest.cs:100 — 7 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:68 — 8 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Modules/core/Struct/MatType.cs:246 — 43 consecutive commented-code lines
  • CommentedOutCode src/OpenCvSharp/Modules/core/Struct/RotatedRect.cs:92 — 3 consecutive commented-code lines
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×17
  • Edited copy of a member (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_video.cs:65 — src/OpenCvSharp/Cv2/Cv2_video.cs:65-70 | src/OpenCvSharp/Cv2/Cv2_video.cs:96-103 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:176 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:176-181 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:184-189 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Modules/features/FastFeatureDetector.cs:24 — src/OpenCvSharp/Modules/features/FastFeatureDetector.cs:24-30 | src/OpenCvSharp/Modules/xfeatures2d/BriefDescriptorExtractor.cs:32-37 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:16 — src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:16-21 | src/OpenCvSharp/Modules/surface_matching/ICP.cs:14-22 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Modules/aruco/CharucoBoard.cs:135 — src/OpenCvSharp/Modules/aruco/CharucoBoard.cs:135-142 | src/OpenCvSharp/Modules/rgbd/DynaFu.cs:139-144 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Modules/dnn/KeypointsModel.cs:55 — src/OpenCvSharp/Modules/dnn/KeypointsModel.cs:55-63 | src/OpenCvSharp/Modules/xfeatures2d/PCTSignatures.cs:342-347 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3081 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3081-3090 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:436-441 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Modules/bioinspired/Retina.cs:36 — src/OpenCvSharp/Modules/bioinspired/Retina.cs:36-41 | src/OpenCvSharp/Modules/bioinspired/TransientAreasSegmentation.cs:39-45 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:2650 — src/OpenCvSharp/Cv2/Cv2_core.cs:2650-2655 | src/OpenCvSharp/Modules/videoio/Cv2.VideoIORegistry.cs:40-45 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_photo.cs:333 — src/OpenCvSharp/Cv2/Cv2_photo.cs:333-339 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:339-344 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Modules/barcode/BarcodeDetector.cs:88 — src/OpenCvSharp/Modules/barcode/BarcodeDetector.cs:88-93 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1673-1679 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_photo.cs:354 — src/OpenCvSharp/Cv2/Cv2_photo.cs:354-360 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:485-490 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:1140 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:1140-1145 | src/OpenCvSharp/Modules/dnn/Net.cs:568-573 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2512 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2512-2517 | src/OpenCvSharp/Cv2/Cv2_highgui.cs:436-442 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2607 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2607-2612 | src/OpenCvSharp/Cv2/Cv2_video.cs:18-23 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_ptcloud_processing.cs:68 — src/OpenCvSharp/Cv2/Cv2_ptcloud_processing.cs:68-73 | src/OpenCvSharp/Modules/shape/ShapeTransformer.cs:67-77 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1669 — src/OpenCvSharp/Cv2/Cv2_core.cs:1669-1674 | src/OpenCvSharp/Cv2/Cv2_objdetect.cs:242-247 — These two members are one piece of code written twice and then edited apart: 6 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.
D3 · God Classes · TooManyMethods · ×15
  • TooManyMethods: Cv2 src/OpenCvSharp/Cv2/Cv2_core.cs — TooManyMethods — 5838 significant lines (blank, comment-only and punctuation-only lines excluded), 648 methods, declared across 18 files: Cv2/Cv2_core.cs (160), Cv2/Cv2_geometry.cs (141), Cv2/Cv2_imgproc.cs (140), Cv2/Cv2_highgui.cs (35), +14 more file(s). The bar is 30 methods; this is 618 over it, 21.60× 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.
  • TooManyMethods: Mat src/OpenCvSharp/Modules/core/Mat/Mat.cs — TooManyMethods — 1328 significant lines (blank, comment-only and punctuation-only lines excluded), 269 methods, declared across 3 files: Mat/Mat.cs (266), Mat/MatPixelBlit.cs (2), Mat/MatPinning.cs (1). The bar is 30 methods; this is 239 over it, 8.97× 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: MatExpr src/OpenCvSharp/Modules/core/MatExpr.cs — TooManyMethods — 284 significant lines (blank, comment-only and punctuation-only lines excluded), 136 methods. The bar is 30 methods; this is 106 over it, 4.53× 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: FileStorage src/OpenCvSharp/Modules/core/FileStorage.cs — TooManyMethods — 506 significant lines (blank, comment-only and punctuation-only lines excluded), 82 methods. The bar is 30 methods; this is 52 over it, 2.73× 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.
  • TooManyMethods: UMat src/OpenCvSharp/Modules/core/Mat/UMat.cs — TooManyMethods — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 77 methods. The bar is 30 methods; this is 47 over it, 2.57× 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.
  • TooManyMethods: FileNode src/OpenCvSharp/Modules/core/FileNode.cs — TooManyMethods — 486 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. The bar is 30 methods; this is 44 over it, 2.47× 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.
  • TooManyMethods: InputArray src/OpenCvSharp/Modules/core/InputArray.cs — TooManyMethods — 154 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: Net src/OpenCvSharp/Modules/dnn/Net.cs — TooManyMethods — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 30 methods; this is 32 over it, 2.07× 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.
  • TooManyMethods: NativeMatExpr src/OpenCvSharp/Modules/core/NativeMatExpr.cs — TooManyMethods — 334 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods, declared across 2 files: core/NativeMatExpr.cs (59), core/NativeMatExpr_CvMethods.cs (1). The bar is 30 methods; this is 30 over it, 2.00× 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.
  • TooManyMethods: XImgProc src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs — TooManyMethods — 316 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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.
  • TooManyMethods: SaturateCast src/OpenCvSharp/Internal/Util/SaturateCast.cs — TooManyMethods — 51 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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.
  • TooManyMethods: Scalar src/OpenCvSharp/Modules/core/Struct/Scalar.cs — TooManyMethods — 235 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: VideoCapture src/OpenCvSharp/Modules/videoio/VideoCapture.cs — TooManyMethods — 550 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: Mat src/OpenCvSharp/Modules/core/Mat/MatOfT.cs — TooManyMethods — 162 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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.
  • TooManyMethods: SparseMat src/OpenCvSharp/Modules/core/SparseMat.cs — TooManyMethods — 179 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×15
  • NuGet dependencies are not locked packaging/nuget/OpenCvSharp5.Windows.Slim.csproj:24 — packaging/nuget/OpenCvSharp5.Windows.Slim.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 packaging/nuget/OpenCvSharp5.Windows.csproj:26 — packaging/nuget/OpenCvSharp5.Windows.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 packaging/nuget/OpenCvSharp5.runtime.linux-arm.csproj:31 — packaging/nuget/OpenCvSharp5.runtime.linux-arm.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/OpenCvSharp.Analyzers/OpenCvSharp.Analyzers.csproj:26 — src/OpenCvSharp.Analyzers/OpenCvSharp.Analyzers.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/OpenCvSharp.AvaloniaExtensions/OpenCvSharp.AvaloniaExtensions.csproj:47 — src/OpenCvSharp.AvaloniaExtensions/OpenCvSharp.AvaloniaExtensions.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/OpenCvSharp.GdipExtensions/OpenCvSharp.GdipExtensions.csproj:49 — src/OpenCvSharp.GdipExtensions/OpenCvSharp.GdipExtensions.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/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj:39 — src/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.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/OpenCvSharp/OpenCvSharp.csproj:60 — src/OpenCvSharp/OpenCvSharp.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 test/OpenCvSharp.Analyzers.Tests/OpenCvSharp.Analyzers.Tests.csproj:12 — test/OpenCvSharp.Analyzers.Tests/OpenCvSharp.Analyzers.Tests.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 test/OpenCvSharp.AndroidSmoke/OpenCvSharp.AndroidSmoke.csproj:14 — test/OpenCvSharp.AndroidSmoke/OpenCvSharp.AndroidSmoke.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 test/OpenCvSharp.PackageSmokeTest/OpenCvSharp.PackageSmokeTest.csproj:27 — test/OpenCvSharp.PackageSmokeTest/OpenCvSharp.PackageSmokeTest.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 test/OpenCvSharp.Tests.Avalonia/OpenCvSharp.Tests.Avalonia.csproj:21 — test/OpenCvSharp.Tests.Avalonia/OpenCvSharp.Tests.Avalonia.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 test/OpenCvSharp.Tests.Wasm/OpenCvSharp.Tests.Wasm.csproj:29 — test/OpenCvSharp.Tests.Wasm/OpenCvSharp.Tests.Wasm.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 test/OpenCvSharp.Tests.Windows/OpenCvSharp.Tests.Windows.csproj:23 — test/OpenCvSharp.Tests.Windows/OpenCvSharp.Tests.Windows.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 test/OpenCvSharp.Tests/OpenCvSharp.Tests.csproj:40 — test/OpenCvSharp.Tests/OpenCvSharp.Tests.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.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×13
  • Edited copy of a member (12 corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:39 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:39-55 | src/OpenCvSharp/Modules/ccalib/Cv2.Omnidir.cs:100-111 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Cv2/Cv2_video.cs:288 — src/OpenCvSharp/Cv2/Cv2_video.cs:288-299 | src/OpenCvSharp/Cv2/Cv2_video.cs:332-346 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptorMatcher.cs:46 — src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptorMatcher.cs:46-57 | src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptorMatcher.cs:87-99 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Modules/aruco/CharucoBoard.cs:21 — src/OpenCvSharp/Modules/aruco/CharucoBoard.cs:21-32 | src/OpenCvSharp/Modules/aruco/GridBoard.cs:22-33 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:39 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:39-50 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:59-70 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:284 — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:284-295 | src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:305-319 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Modules/optflow/GPCForest5.cs:38 — src/OpenCvSharp/Modules/optflow/GPCForest5.cs:38-49 | src/OpenCvSharp/Modules/optflow/GPCTree.cs:32-43 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:262 — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:262-274 | src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:449-460 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2818 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2818-2830 | src/OpenCvSharp/Modules/xfeatures2d/PCTSignatures.cs:67-78 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Modules/dnn/TextRecognitionModel.cs:139 — src/OpenCvSharp/Modules/dnn/TextRecognitionModel.cs:139-150 | src/OpenCvSharp/Modules/shape/ShapeTransformer.cs:47-58 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Modules/core/NativeMatExpr.cs:582 — src/OpenCvSharp/Modules/core/NativeMatExpr.cs:582-594 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:603-614 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Modules/videoio/VideoWriter.cs:71 — src/OpenCvSharp/Modules/videoio/VideoWriter.cs:71-82 | src/OpenCvSharp/Modules/videoio/VideoWriter.cs:275-289 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:207 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:207-218 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:176-187 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×12
  • Edited copy of a member (4 corresponding lines) src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:77 — src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:77-80 | src/OpenCvSharp/Modules/rgbd/KinFuParams.cs:79-82 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:84 — src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:84-87 | src/OpenCvSharp/Modules/rgbd/KinFuParams.cs:86-89 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3b.cs:37 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3b.cs:37-40 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4b.cs:42-46 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3b.cs:47 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3b.cs:47-50 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4b.cs:53-57 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3i.cs:37 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3i.cs:37-40 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4i.cs:42-46 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3i.cs:47 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3i.cs:47-50 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4i.cs:53-57 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3s.cs:37 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3s.cs:37-40 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4s.cs:42-46 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3s.cs:47 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3s.cs:47-50 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4s.cs:53-57 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3w.cs:37 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3w.cs:37-40 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4w.cs:42-46 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3w.cs:47 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3w.cs:47-50 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4w.cs:53-57 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:148 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:148-151 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4f.cs:156-159 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/OpenCvSharp/Modules/dnn/Tokenizer.cs:13 — src/OpenCvSharp/Modules/dnn/Tokenizer.cs:13-16 | src/OpenCvSharp/Modules/imgcodecs/ImageCollection.cs:41-44 — These two members are one piece of code written twice and then edited apart: 4 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.
D31 · IaC & Container Security · Medium IaC · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×11
  • Edited copies of one member (3 members, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:602 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:602-611 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:632-640 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:663-672 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:328 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:328-338 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:899-907 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:927-936 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Modules/text/OCRHolisticWordRecognizer.cs:25 — src/OpenCvSharp/Modules/text/OCRHolisticWordRecognizer.cs:25-35 | src/OpenCvSharp/Modules/ximgproc/Segmentation/SelectiveSearchSegmentationStrategyMultiple.cs:118-126 | src/OpenCvSharp/Modules/ximgproc/Segmentation/SelectiveSearchSegmentationStrategyMultiple.cs:138-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1682 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1682-1690 | src/OpenCvSharp/Modules/stitching/PyRotationWarper.cs:84-94 | src/OpenCvSharp/Modules/stitching/PyRotationWarper.cs:101-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:152 — src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:152-160 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:174-182 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:258-266 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.cs:134 — src/OpenCvSharp/Cv2/Cv2_calib.cs:134-142 | src/OpenCvSharp/Cv2/Cv2_calib.cs:187-195 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1545-1557 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:1276 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:1276-1286 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:705-715 | src/OpenCvSharp/Modules/ptcloud/Volume.cs:70-78 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Modules/dnn/Model.cs:169 — src/OpenCvSharp/Modules/dnn/Model.cs:169-177 | src/OpenCvSharp/Modules/dnn/TextRecognitionModel.cs:122-130 | src/OpenCvSharp/Modules/ximgproc/FastLineDetector.cs:73-81 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Modules/aruco/Dictionary.cs:27 — src/OpenCvSharp/Modules/aruco/Dictionary.cs:27-36 | src/OpenCvSharp/Modules/core/Mat/Mat.cs:230-238 | src/OpenCvSharp/Modules/ptcloud/Odometry.cs:47-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Modules/ml/StatModel.cs:72 — src/OpenCvSharp/Modules/ml/StatModel.cs:72-80 | src/OpenCvSharp/Modules/video/Tracker.cs:41-52 | src/OpenCvSharp/Modules/videoio/VideoCapture.cs:1444-1454 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1340 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1340-1348 | src/OpenCvSharp/Modules/bgsegm/BackgroundSubtractorLSBPDesc.cs:21-29 | src/OpenCvSharp/Modules/flann/Index.cs:59-67 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 7+ corresponding lines) · ×11
  • Edited copies of one member (3 members, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:688 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:688-694 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:709-715 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:758-765 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2104 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2104-2110 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:459-466 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:783-789 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_photo.cs:224 — src/OpenCvSharp/Cv2/Cv2_photo.cs:224-231 | src/OpenCvSharp/Modules/optflow/Cv2.OptFlow.cs:51-59 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:744-750 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:2154 — src/OpenCvSharp/Cv2/Cv2_core.cs:2154-2160 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1959-1965 | src/OpenCvSharp/Modules/core/PCA.cs:128-135 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:1312 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:1312-1320 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:741-749 | src/OpenCvSharp/Modules/core/SparseMat.cs:200-206 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Modules/core/LDA.cs:150 — src/OpenCvSharp/Modules/core/LDA.cs:150-159 | src/OpenCvSharp/Modules/core/Mat/Mat.cs:1449-1458 | src/OpenCvSharp/Modules/core/PCA.cs:228-234 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Modules/optflow/DenseRLOFOpticalFlow.cs:68 — src/OpenCvSharp/Modules/optflow/DenseRLOFOpticalFlow.cs:68-75 | src/OpenCvSharp/Modules/optflow/RLOFOpticalFlowParameter.cs:25-31 | src/OpenCvSharp/Modules/optflow/SparseRLOFOpticalFlow.cs:41-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.cs:87 — src/OpenCvSharp/Cv2/Cv2_calib.cs:87-93 | src/OpenCvSharp/Cv2/Cv2_objdetect.cs:200-206 | src/OpenCvSharp/Modules/flann/Index.cs:76-85 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:316 — src/OpenCvSharp/Cv2/Cv2_core.cs:316-322 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:3041-3047 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:219-226 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:330 — src/OpenCvSharp/Cv2/Cv2_core.cs:330-336 | src/OpenCvSharp/Modules/face/FaceRecognizer/FaceRecognizer.cs:64-71 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:548-556 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1696 — src/OpenCvSharp/Cv2/Cv2_core.cs:1696-1702 | src/OpenCvSharp/Modules/core/Mat/Mat.cs:1466-1474 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:875-883 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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, 8+ corresponding lines) · ×10
  • Edited copies of one member (3 members, 8+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Rect.cs:380 — src/OpenCvSharp/Modules/core/Struct/Rect.cs:380-387 | src/OpenCvSharp/Modules/core/Struct/Rect2d.cs:389-396 | src/OpenCvSharp/Modules/core/Struct/Rect2f.cs:377-384 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1727 — src/OpenCvSharp/Cv2/Cv2_core.cs:1727-1734 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1261-1268 | src/OpenCvSharp/Modules/objdetect/FaceRecognizerSF.cs:140-150 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Modules/face/Cv2.Face.cs:125 — src/OpenCvSharp/Modules/face/Cv2.Face.cs:125-132 | src/OpenCvSharp/Modules/face/Facemark/FacemarkAAM.cs:176-183 | src/OpenCvSharp/Modules/imgproc/FontFace.cs:115-123 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:459 — src/OpenCvSharp/Cv2/Cv2_core.cs:459-466 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2120-2127 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:566-573 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:153 — src/OpenCvSharp/Cv2/Cv2_core.cs:153-161 | src/OpenCvSharp/Cv2/Cv2_photo.cs:249-256 | src/OpenCvSharp/Modules/xfeatures2d/PCTSignatures.cs:127-134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2735 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2735-2742 | src/OpenCvSharp/Modules/img_hash/ImgHashBase.cs:38-46 | src/OpenCvSharp/Modules/ml/SVM.cs:347-356 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:417 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:417-426 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:216-223 | src/OpenCvSharp/Modules/core/SparseMat.cs:44-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Modules/shape/Cv2.Shape.cs:85 — src/OpenCvSharp/Modules/shape/Cv2.Shape.cs:85-92 | src/OpenCvSharp/Modules/shape/ShapeDistanceExtractor.cs:23-34 | src/OpenCvSharp/Modules/xfeatures2d/PCTSignaturesSQFD.cs:45-53 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1282 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1282-1289 | src/OpenCvSharp/Modules/ptcloud/Octree.cs:156-163 | src/OpenCvSharp/Modules/stitching/ExposureCompensator.cs:95-102 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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, 8+ corresponding lines) src/OpenCvSharp/Modules/core/Mat/UMat.cs:199 — src/OpenCvSharp/Modules/core/Mat/UMat.cs:199-207 | src/OpenCvSharp/Modules/core/SparseMat.cs:58-69 | src/OpenCvSharp/Modules/xfeatures2d/BOWImgDescriptorExtractor.cs:36-43 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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 (10 corresponding lines) · ×10
  • Edited copy of a member (10 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:626 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:626-635 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:797-808 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2331 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2331-2344 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2409-2418 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.cs:159 — src/OpenCvSharp/Cv2/Cv2_calib.cs:159-168 | src/OpenCvSharp/Cv2/Cv2_calib.cs:214-223 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Modules/xfeatures2d/AffineFeature2D.cs:33 — src/OpenCvSharp/Modules/xfeatures2d/AffineFeature2D.cs:33-45 | src/OpenCvSharp/Modules/xfeatures2d/AffineFeature2D.cs:52-61 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Modules/stitching/Blender.cs:59 — src/OpenCvSharp/Modules/stitching/Blender.cs:59-68 | src/OpenCvSharp/Modules/stitching/Timelapser.cs:58-68 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:2593 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:2593-2603 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:1308-1317 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Modules/ml/LogisticRegression.cs:186 — src/OpenCvSharp/Modules/ml/LogisticRegression.cs:186-195 | src/OpenCvSharp/Modules/ml/StatModel.cs:132-141 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Modules/core/FileNode.cs:609 — src/OpenCvSharp/Modules/core/FileNode.cs:609-618 | src/OpenCvSharp/Modules/core/FileStorage.cs:263-272 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Modules/face/Facemark/FacemarkKazemi.cs:96 — src/OpenCvSharp/Modules/face/Facemark/FacemarkKazemi.cs:96-105 | src/OpenCvSharp/Modules/face/Facemark/FacemarkTrain.cs:64-73 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) src/OpenCvSharp/Modules/stitching/BestOf2NearestMatcher.cs:41 — src/OpenCvSharp/Modules/stitching/BestOf2NearestMatcher.cs:41-50 | src/OpenCvSharp/Modules/stitching/BestOf2NearestRangeMatcher.cs:42-52 — These two members are one piece of code written twice and then edited apart: 10 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.
D3 · God Classes · FileTooLong · ×9
  • FileTooLong: objdetect/HOGDescriptor.cs src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs — FileTooLong — 1629 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1129 over it, 3.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Cv2/Cv2_geometry.cs src/OpenCvSharp/Cv2/Cv2_geometry.cs — FileTooLong — 1494 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 994 over it, 2.99× 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: Mat/Mat.cs src/OpenCvSharp/Modules/core/Mat/Mat.cs — FileTooLong — 1371 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 871 over it, 2.74× 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: Cv2/Cv2_imgproc.cs src/OpenCvSharp/Cv2/Cv2_imgproc.cs — FileTooLong — 1167 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 667 over it, 2.33× 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: Cv2/Cv2_core.cs src/OpenCvSharp/Cv2/Cv2_core.cs — FileTooLong — 1037 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 537 over it, 2.07× 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: geometry/NativeMethods_geometry.cs src/OpenCvSharp/Internal/PInvoke/NativeMethods/geometry/NativeMethods_geometry.cs — FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 91 over it, 1.18× 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: videoio/VideoCapture.cs src/OpenCvSharp/Modules/videoio/VideoCapture.cs — FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 66 over it, 1.13× 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: core/FileStorage.cs src/OpenCvSharp/Modules/core/FileStorage.cs — FileTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 21 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Cv2/Cv2_calib.cs src/OpenCvSharp/Cv2/Cv2_calib.cs — FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6 over it, 1.01× 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.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×8
  • Edited copy of a member (15 corresponding lines) src/OpenCvSharp/Cv2/Cv2_features.cs:86 — src/OpenCvSharp/Cv2/Cv2_features.cs:86-100 | src/OpenCvSharp/Cv2/Cv2_features.cs:113-128 — 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.
  • Edited copy of a member (15 corresponding lines) src/OpenCvSharp/Modules/features/Feature2D.cs:197 — src/OpenCvSharp/Modules/features/Feature2D.cs:197-215 | src/OpenCvSharp/Modules/xfeatures2d/PCTSignaturesSQFD.cs:70-84 — 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.
  • Edited copy of a member (15 corresponding lines) src/OpenCvSharp/Modules/text/Cv2.Text.cs:70 — src/OpenCvSharp/Modules/text/Cv2.Text.cs:70-84 | src/OpenCvSharp/Modules/text/Cv2.Text.cs:101-117 — 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.
  • Edited copy of a member (15 corresponding lines) src/OpenCvSharp/Cv2/Cv2_core_nd.cs:13 — src/OpenCvSharp/Cv2/Cv2_core_nd.cs:13-27 | src/OpenCvSharp/Cv2/Cv2_core_nd.cs:35-49 — 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.
  • Edited copy of a member (15 corresponding lines) src/OpenCvSharp/Modules/objdetect/FaceDetectorYN.cs:40 — src/OpenCvSharp/Modules/objdetect/FaceDetectorYN.cs:40-58 | src/OpenCvSharp/Modules/objdetect/FaceRecognizerSF.cs:48-62 — 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.
  • Edited copy of a member (15 corresponding lines) src/OpenCvSharp/Modules/flann/Index.cs:125 — src/OpenCvSharp/Modules/flann/Index.cs:125-140 | src/OpenCvSharp/Modules/flann/Index.cs:176-190 — 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.
  • Edited copy of a member (15 corresponding lines) src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:262 — src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:262-277 | src/OpenCvSharp/Modules/face/MACE.cs:52-66 — 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.
  • Edited copy of a member (15 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:3202 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:3202-3216 | src/OpenCvSharp/Modules/core/Mat/Mat.cs:3239-3253 — 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 copy of a member (13 corresponding lines) · ×8
  • Edited copy of a member (13 corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.cs:58 — src/OpenCvSharp/Cv2/Cv2_calib.cs:58-70 | src/OpenCvSharp/Cv2/Cv2_features.cs:336-349 — 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) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3143 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3143-3156 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3173-3185 — 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) src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:67 — src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:67-83 | src/OpenCvSharp/Modules/barcode/BarcodeDetector.cs:116-128 — 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) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1580 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1580-1592 | src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:75-87 — 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) src/OpenCvSharp/Modules/features/Feature2D.cs:231 — src/OpenCvSharp/Modules/features/Feature2D.cs:231-243 | src/OpenCvSharp/Modules/xfeatures2d/AffineFeature2D.cs:104-117 — 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) src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptor.cs:134 — src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptor.cs:134-146 | src/OpenCvSharp/Modules/line_descriptors/LSDDetector.cs:76-89 — 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) src/OpenCvSharp/Modules/aruco/Dictionary.cs:164 — src/OpenCvSharp/Modules/aruco/Dictionary.cs:164-176 | src/OpenCvSharp/Modules/aruco/Dictionary.cs:189-202 — 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) src/OpenCvSharp/Modules/core/Mat/Mat.cs:978 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:978-990 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:409-421 — 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.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×8
  • Edited copy of a member (5 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:2098 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:2098-2102 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:999-1003 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/OpenCvSharp/Modules/core/MatExpr.cs:470 — src/OpenCvSharp/Modules/core/MatExpr.cs:470-474 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:167-175 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/OpenCvSharp/Modules/core/MatExpr.cs:477 — src/OpenCvSharp/Modules/core/MatExpr.cs:477-481 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:178-186 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/OpenCvSharp/Modules/core/MatExpr.cs:492 — src/OpenCvSharp/Modules/core/MatExpr.cs:492-496 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:235-243 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/OpenCvSharp/Modules/core/MatExpr.cs:499 — src/OpenCvSharp/Modules/core/MatExpr.cs:499-503 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:246-254 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/OpenCvSharp/Modules/core/MatExpr.cs:514 — src/OpenCvSharp/Modules/core/MatExpr.cs:514-518 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:303-311 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/OpenCvSharp/Modules/core/MatExpr.cs:521 — src/OpenCvSharp/Modules/core/MatExpr.cs:521-525 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:314-322 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/OpenCvSharp/Modules/core/MatExpr.cs:455 — src/OpenCvSharp/Modules/core/MatExpr.cs:455-459 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:113-121 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×8
  • Edited copy of a member (1 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3i.cs:77 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3i.cs:77-77 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4i.cs:86-86 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:2837 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:2837-2840 | src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:345-345 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:2832 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:2832-2835 | src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:344-344 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3s.cs:77 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3s.cs:77-77 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4s.cs:86-86 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:133 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:133-133 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:134-134 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:211 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:211-211 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:219-219 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:165 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:165-165 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4f.cs:173-173 — These two members are one piece of code written twice and then edited apart: 1 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 (1 corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:172 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:172-172 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4f.cs:180-180 — These two members are one piece of code written twice and then edited apart: 1 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, 6+ corresponding lines) · ×7
  • Edited copies of one member (4 members, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:186 — src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:186-195 | src/OpenCvSharp/Cv2/Cv2_video.cs:208-213 | src/OpenCvSharp/Modules/optflow/Cv2.OptFlow.cs:172-184 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:886-894 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Modules/stereo/StereoSGBM.cs:67 — src/OpenCvSharp/Modules/stereo/StereoSGBM.cs:67-75 | src/OpenCvSharp/Modules/xfeatures2d/AKAZE.cs:49-57 | src/OpenCvSharp/Modules/xfeatures2d/KAZE.cs:32-40 | src/OpenCvSharp/Modules/xfeatures2d/PCTSignatures.cs:33-38 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Modules/features/ANNIndex.cs:25 — src/OpenCvSharp/Modules/features/ANNIndex.cs:25-31 | src/OpenCvSharp/Modules/text/OCRHMMDecoderClassifierCallback.cs:58-66 | src/OpenCvSharp/Modules/xfeatures2d/BEBLID.cs:27-32 | src/OpenCvSharp/Modules/xfeatures2d/TEBLID.cs:27-32 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:170 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:170-176 | src/OpenCvSharp/Cv2/Cv2_photo.cs:65-70 | src/OpenCvSharp/Modules/intensity_transform/Cv2.IntensityTransform.cs:65-71 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:927-934 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Modules/bioinspired/Retina.cs:27 — src/OpenCvSharp/Modules/bioinspired/Retina.cs:27-32 | src/OpenCvSharp/Modules/bioinspired/TransientAreasSegmentation.cs:28-35 | src/OpenCvSharp/Modules/phase_unwrapping/HistogramPhaseUnwrapping.cs:48-56 | src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:60-67 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Modules/core/FileNode.cs:519 — src/OpenCvSharp/Modules/core/FileNode.cs:519-525 | src/OpenCvSharp/Modules/dnn/Net.cs:506-513 | src/OpenCvSharp/Modules/dnn/TextRecognitionModel.cs:108-114 | src/OpenCvSharp/Modules/dpm/DpmDetector.cs:71-76 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_photo.cs:313 — src/OpenCvSharp/Cv2/Cv2_photo.cs:313-319 | src/OpenCvSharp/Modules/aruco/Board.cs:160-167 | src/OpenCvSharp/Modules/features/ANNIndex.cs:64-70 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:470-475 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) · ×7
  • Edited copies of one member (3 members, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2691 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2691-2697 | src/OpenCvSharp/Modules/xphoto/Cv2.XPhoto.cs:59-64 | src/OpenCvSharp/Modules/xphoto/Cv2.XPhoto.cs:104-109 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:882 — src/OpenCvSharp/Cv2/Cv2_core.cs:882-888 | src/OpenCvSharp/Cv2/Cv2_ptcloud_processing.cs:16-22 | src/OpenCvSharp/Cv2/Cv2_stereo.cs:407-412 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1290 — src/OpenCvSharp/Cv2/Cv2_core.cs:1290-1296 | src/OpenCvSharp/Modules/fuzzy/Cv2.Fuzzy.cs:84-90 | src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:118-123 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:359 — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:359-364 | src/OpenCvSharp/Modules/core/SVD.cs:26-31 | src/OpenCvSharp/Modules/ptcloud/RgbdNormals.cs:50-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:543 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:543-549 | src/OpenCvSharp/Cv2/Cv2_photo.cs:17-23 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:136-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1429 — src/OpenCvSharp/Cv2/Cv2_core.cs:1429-1434 | src/OpenCvSharp/Cv2/Cv2_objdetect.cs:142-147 | src/OpenCvSharp/Cv2/Cv2_video.cs:34-39 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:301 — src/OpenCvSharp/Cv2/Cv2_core.cs:301-307 | src/OpenCvSharp/Modules/quality/QualityBRISQUE.cs:74-85 | src/OpenCvSharp/Modules/quality/QualityBase.cs:47-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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.
IC1 · Incompleteness & stubs · Unfinished branch · ×7
  • Unfinished branch — throws NotImplementedException src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:33 — The catch-all arm (reached by `Indexed`, `Gdi`, `Alpha`, `PAlpha` and 13 more) throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:102 — The branch `if (dst.IsSubmatrix())` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:372 — The branch `if (submat)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:411 — The `default:` section (reached by `Indexed`, `Gdi`, `Alpha`, `PAlpha` and 15 more) throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:151 — The branch `if (submat)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:236 — The branch `if (src.IsSubmatrix())` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws a "not implemented" exception src/OpenCvSharp/Modules/fuzzy/Cv2.Fuzzy.cs:108 — The branch `if (function != FuzzyFunction.Linear)` throws `ArgumentOutOfRangeException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×5
  • Edited copy of a member (19 corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:295 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:295-313 | src/OpenCvSharp/Cv2/Cv2_stereo.cs:93-114 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) src/OpenCvSharp/Modules/xfeatures2d/BRISK.cs:49 — src/OpenCvSharp/Modules/xfeatures2d/BRISK.cs:49-67 | src/OpenCvSharp/Modules/xfeatures2d/BRISK.cs:88-107 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:185 — src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:185-203 | src/OpenCvSharp/Cv2/Cv2_imgcodecs.cs:232-251 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:1082 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:1082-1100 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:513-531 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) src/OpenCvSharp/Fundamentals/MatSafeHandle.cs:32 — src/OpenCvSharp/Fundamentals/MatSafeHandle.cs:32-50 | src/OpenCvSharp/Fundamentals/OpenCvPtrSafeHandle.cs:45-63 — These two members are one piece of code written twice and then edited apart: 19 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, 13+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 13+ corresponding lines) src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:18 — src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:18-30 | src/OpenCvSharp/Modules/rgbd/DynaFu.cs:19-31 | src/OpenCvSharp/Modules/rgbd/KinFu.cs:18-30 | src/OpenCvSharp/Modules/rgbd/LargeKinfu.cs:19-34 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 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, 13+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_objdetect.cs:57 — src/OpenCvSharp/Cv2/Cv2_objdetect.cs:57-71 | src/OpenCvSharp/Cv2/Cv2_objdetect.cs:82-96 | src/OpenCvSharp/Modules/dnn/Net.cs:893-905 | src/OpenCvSharp/Modules/dnn/Net.cs:935-947 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 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, 13+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2989 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2989-3002 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:3019-3031 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:3115-3129 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:3142-3157 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 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, 13+ corresponding lines) src/OpenCvSharp/Modules/objdetect/QRCodeDetector.cs:83 — src/OpenCvSharp/Modules/objdetect/QRCodeDetector.cs:83-97 | src/OpenCvSharp/Modules/objdetect/QRCodeDetector.cs:107-119 | src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:104-118 | src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:128-142 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 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, 13+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1581 — src/OpenCvSharp/Cv2/Cv2_core.cs:1581-1593 | src/OpenCvSharp/Cv2/Cv2_core.cs:1603-1615 | src/OpenCvSharp/Cv2/Cv2_core.cs:1625-1637 | src/OpenCvSharp/Cv2/Cv2_core.cs:1647-1659 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 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 (14 corresponding lines) · ×5
  • Edited copy of a member (14 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1978 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1978-1991 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2008-2021 — 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) src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptorMatcher.cs:29 — src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptorMatcher.cs:29-42 | src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptorMatcher.cs:66-79 — 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) src/OpenCvSharp/Modules/optflow/Cv2.OptFlow.cs:351 — src/OpenCvSharp/Modules/optflow/Cv2.OptFlow.cs:351-366 | src/OpenCvSharp/Modules/optflow/DenseRLOFOpticalFlow.cs:47-60 — 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) src/OpenCvSharp/Modules/barcode/BarcodeDetector.cs:139 — src/OpenCvSharp/Modules/barcode/BarcodeDetector.cs:139-152 | src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:231-249 — 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) src/OpenCvSharp/Modules/dnn/Net.cs:154 — src/OpenCvSharp/Modules/dnn/Net.cs:154-167 | src/OpenCvSharp/Modules/dnn/Net.cs:209-222 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 10+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Rect.cs:337 — src/OpenCvSharp/Modules/core/Struct/Rect.cs:337-346 | src/OpenCvSharp/Modules/core/Struct/Rect2d.cs:346-355 | src/OpenCvSharp/Modules/core/Struct/Rect2f.cs:332-341 — 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.
  • Edited copies of one member (3 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:15 — src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:15-27 | src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:33-42 | src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:48-58 — 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.
  • Edited copies of one member (3 members, 10+ corresponding lines) src/OpenCvSharp/Modules/features/ALIKED.cs:35 — src/OpenCvSharp/Modules/features/ALIKED.cs:35-50 | src/OpenCvSharp/Modules/features/DISK.cs:36-49 | src/OpenCvSharp/Modules/features/XFeat.cs:25-34 — 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.
  • Edited copies of one member (3 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:201 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:201-210 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1651-1661 | src/OpenCvSharp/Cv2/Cv2_stereo.cs:252-263 — 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.
  • Edited copies of one member (3 members, 10+ corresponding lines) src/OpenCvSharp/Modules/core/FileNodeIterator.cs:154 — src/OpenCvSharp/Modules/core/FileNodeIterator.cs:154-165 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:622-634 | src/OpenCvSharp/Modules/xfeatures2d/BOWKMeansTrainer.cs:58-67 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 11+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:93 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:93-103 | src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:173-183 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:524-538 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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, 11+ corresponding lines) src/OpenCvSharp/Modules/stitching/Stitcher.cs:324 — src/OpenCvSharp/Modules/stitching/Stitcher.cs:324-338 | src/OpenCvSharp/Modules/stitching/Stitcher.cs:441-451 | src/OpenCvSharp/Modules/stitching/Stitcher.cs:461-474 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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, 11+ corresponding lines) src/OpenCvSharp/Modules/photo/AlignMTB.cs:28 — src/OpenCvSharp/Modules/photo/AlignMTB.cs:28-38 | src/OpenCvSharp/Modules/photo/AlignMTB.cs:42-54 | src/OpenCvSharp/Modules/photo/MergeRobertson.cs:24-34 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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, 11+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1197 — src/OpenCvSharp/Cv2/Cv2_core.cs:1197-1208 | src/OpenCvSharp/Cv2/Cv2_core.cs:1256-1267 | src/OpenCvSharp/Modules/ptcloud/Odometry.cs:96-106 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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, 11+ corresponding lines) src/OpenCvSharp/Modules/dnn/TextDetectionModel.cs:34 — src/OpenCvSharp/Modules/dnn/TextDetectionModel.cs:34-45 | src/OpenCvSharp/Modules/dnn/TextDetectionModel.cs:55-66 | src/OpenCvSharp/Modules/saliency/ObjectnessBING.cs:41-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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.
D10 · Test Quality · Skipped test · ×4
  • Skipped test: Issue349 test/OpenCvSharp.Tests/core/MatTest.cs:1256 — Skipped — heavy
  • Skipped test: RunTest test/OpenCvSharp.Tests/highgui/TrackbarTest.cs:10 — Skipped — GUI Test
  • Skipped test: ImReadDoesNotSupportGif test/OpenCvSharp.Tests/imgcodecs/ImgCodecsTest.cs:52 — Skipped — supported?
  • Skipped test: HaveImageWriterJapanese test/OpenCvSharp.Tests/imgcodecs/ImgCodecsTest.cs:357 — Skipped — AccessViolationException
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×4
  • Edited copy of a member (30 corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.cs:442 — src/OpenCvSharp/Cv2/Cv2_calib.cs:442-471 | src/OpenCvSharp/Cv2/Cv2_calib.cs:586-620 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) src/OpenCvSharp/Modules/optflow/GPCForest5.cs:62 — src/OpenCvSharp/Modules/optflow/GPCForest5.cs:62-91 | src/OpenCvSharp/Modules/optflow/GPCTrainingSamples.cs:27-56 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:732 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:732-761 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:868-897 — These two members are one piece of code written twice and then edited apart: 30 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 (30 corresponding lines) src/OpenCvSharp/Modules/objdetect/QRCodeDetector.cs:176 — src/OpenCvSharp/Modules/objdetect/QRCodeDetector.cs:176-205 | src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:190-219 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×4
  • Edited copy of a member (17 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1407 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1407-1424 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1438-1454 — These two members are one piece of code written twice and then edited apart: 17 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 (17 corresponding lines) src/OpenCvSharp.Analyzers/RowColInLoopBodyAnalyzer.cs:47 — src/OpenCvSharp.Analyzers/RowColInLoopBodyAnalyzer.cs:47-63 | src/OpenCvSharp.Analyzers/RowColNotDisposedAnalyzer.cs:52-68 — These two members are one piece of code written twice and then edited apart: 17 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 (17 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1756 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1756-1772 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1824-1841 — These two members are one piece of code written twice and then edited apart: 17 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 (17 corresponding lines) src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:37 — src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:37-53 | src/OpenCvSharp/Modules/tracking/TrackerCSRT.cs:41-57 — These two members are one piece of code written twice and then edited apart: 17 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, 14+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 14+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:651 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:651-664 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:687-704 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1812-1832 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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, 14+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:124 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:124-140 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1194-1207 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1233-1246 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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, 14+ corresponding lines) src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:231 — src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:231-244 | src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:260-273 | src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:287-301 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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, 14+ corresponding lines) src/OpenCvSharp/Internal/Vectors/VectorOfDTreesNode.cs:58 — src/OpenCvSharp/Internal/Vectors/VectorOfDTreesNode.cs:58-71 | src/OpenCvSharp/Internal/Vectors/VectorOfDTreesSplit.cs:58-71 | src/OpenCvSharp/Internal/Vectors/VectorOfKeyLine.cs:71-84 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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 (11 corresponding lines) · ×4
  • Edited copy of a member (11 corresponding lines) src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:217 — src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:217-227 | src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:236-249 — These two members are one piece of code written twice and then edited apart: 11 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 (11 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:156 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:156-167 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1258-1268 — These two members are one piece of code written twice and then edited apart: 11 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 (11 corresponding lines) src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:144 — src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:144-154 | src/OpenCvSharp/Modules/xfeatures2d/PCTSignatures.cs:100-111 — These two members are one piece of code written twice and then edited apart: 11 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 (11 corresponding lines) src/OpenCvSharp/Modules/wechat_qrcode/WeChatQRCode.cs:72 — src/OpenCvSharp/Modules/wechat_qrcode/WeChatQRCode.cs:72-82 | src/OpenCvSharp/Modules/wechat_qrcode/WeChatQRCode.cs:96-106 — These two members are one piece of code written twice and then edited apart: 11 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 (6 members, 10+ corresponding lines) · ×4
  • Edited copies of one member (6 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1511 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1511-1523 | src/OpenCvSharp/Modules/geometry/RegionGrowing3D.cs:49-61 | src/OpenCvSharp/Modules/ml/EM.cs:202-219 | src/OpenCvSharp/Modules/ml/EM.cs:295-315 | src/OpenCvSharp/Modules/ptcloud/Octree.cs:142-151 | src/OpenCvSharp/Modules/ptcloud/Odometry.cs:156-165 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:2752 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:2752-2764 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2774-2786 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2867-2877 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2891-2900 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2914-2923 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2937-2946 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 10+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec4b.cs:105 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec4b.cs:105-114 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:129-138 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4f.cs:130-139 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4i.cs:106-115 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4s.cs:106-115 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4w.cs:105-114 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 10+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec6b.cs:114 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6b.cs:114-123 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:144-153 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:145-154 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6i.cs:115-124 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6s.cs:115-124 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6w.cs:114-123 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×4
  • Edited copies of one member (4 members, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_features.cs:42 — src/OpenCvSharp/Cv2/Cv2_features.cs:42-48 | src/OpenCvSharp/Cv2/Cv2_features.cs:61-67 | src/OpenCvSharp/Cv2/Cv2_highgui.cs:458-468 | src/OpenCvSharp/Modules/text/Cv2.Text.cs:31-44 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Modules/plot/Plot2d.cs:21 — src/OpenCvSharp/Modules/plot/Plot2d.cs:21-28 | src/OpenCvSharp/Modules/quality/QualityGMSD.cs:26-32 | src/OpenCvSharp/Modules/quality/QualityMSE.cs:23-30 | src/OpenCvSharp/Modules/quality/QualitySSIM.cs:25-31 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:2131 — src/OpenCvSharp/Cv2/Cv2_core.cs:2131-2139 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1696-1704 | src/OpenCvSharp/Cv2/Cv2_ptcloud_processing.cs:126-132 | src/OpenCvSharp/Cv2/Cv2_video.cs:223-231 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 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, 7+ corresponding lines) src/OpenCvSharp/Modules/imgcodecs/Animation.cs:133 — src/OpenCvSharp/Modules/imgcodecs/Animation.cs:133-139 | src/OpenCvSharp/Modules/imgcodecs/ImageCollection.cs:83-89 | src/OpenCvSharp/Modules/ximgproc/DisparityWLSFilter.cs:158-164 | src/OpenCvSharp/Modules/xstereo/QuasiDenseStereo.cs:143-149 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 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 (6 members, 8+ corresponding lines) · ×4
  • Edited copies of one member (6 members, 8+ corresponding lines) src/OpenCvSharp/Modules/bgsegm/BackgroundSubtractorGSOC.cs:39 — src/OpenCvSharp/Modules/bgsegm/BackgroundSubtractorGSOC.cs:39-47 | src/OpenCvSharp/Modules/bgsegm/BackgroundSubtractorLSBP.cs:42-50 | src/OpenCvSharp/Modules/features/MSER.cs:43-50 | src/OpenCvSharp/Modules/hfs/HfsSegment.cs:39-50 | src/OpenCvSharp/Modules/imgproc/LineSegmentDetector.cs:34-48 | src/OpenCvSharp/Modules/ximgproc/EdgeBoxes.cs:48-55 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 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.
  • Edited copies of one member (6 members, 8+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:2225 — src/OpenCvSharp/Cv2/Cv2_core.cs:2225-2232 | src/OpenCvSharp/Cv2/Cv2_core.cs:2245-2252 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1011-1020 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1875-1882 | src/OpenCvSharp/Modules/ximgproc/ContourFitting.cs:47-57 | src/OpenCvSharp/Modules/ximgproc/StructuredEdgeDetection.cs:98-107 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 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.
  • Edited copies of one member (6 members, 8+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec2b.cs:92 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec2b.cs:92-99 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec2d.cs:102-109 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec2f.cs:103-110 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec2i.cs:86-93 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec2s.cs:86-93 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec2w.cs:85-92 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 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.
  • Edited copies of one member (6 members, 8+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec4b.cs:96 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec4b.cs:96-103 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:120-127 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4f.cs:121-128 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4i.cs:97-104 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4s.cs:97-104 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec4w.cs:96-103 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 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 · Duplicated block (12 lines × 2) · ×4
  • Duplicated block (12 lines × 2) src/OpenCvSharp/Cv2/Cv2_calib.cs:260 — src/OpenCvSharp/Cv2/Cv2_calib.cs:260-271 | src/OpenCvSharp/Cv2/Cv2_calib.cs:385-396 — both copies are in the same file, so extract the 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/OpenCvSharp/Cv2/Cv2_calib.cs:260` 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/OpenCvSharp/Modules/stitching/GraphCutSeamFinder.cs:44 — src/OpenCvSharp/Modules/stitching/GraphCutSeamFinder.cs:44-55 | src/OpenCvSharp/Modules/stitching/SeamFinder.cs:61-72 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/stitching/GraphCutSeamFinder.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:144 — src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:144-155 | src/OpenCvSharp/Modules/features/FlannBasedMatcher.cs:84-95 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:243 — src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:243-254 | src/OpenCvSharp/Modules/stitching/Estimator.cs:47-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 both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `features` to `StdVector<KeyPoint>?[] keypointVecs) ToWImageFeaturesArray( IReadOnlyList<ImageFeatures>` in one and `IReadOnlyList<ImageFeatures>` 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 · Duplicated block (8 lines × 2) · ×4
  • Duplicated block (8 lines × 2) src/OpenCvSharp/Modules/core/Mat/MatPixelBlit.cs:45 — src/OpenCvSharp/Modules/core/Mat/MatPixelBlit.cs:45-52 | src/OpenCvSharp/Modules/core/Mat/MatPixelBlit.cs:91-98 — both copies are in the same file, so extract the 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/OpenCvSharp/Modules/core/Mat/MatPixelBlit.cs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/OpenCvSharp/Cv2/Cv2_stereo.cs:371 — src/OpenCvSharp/Cv2/Cv2_stereo.cs:371-379 | src/OpenCvSharp/Cv2/Cv2_stereo.cs:380-387 — both copies are in the same file, so extract the 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/OpenCvSharp/Cv2/Cv2_stereo.cs:371` 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 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/OpenCvSharp/Cv2/Cv2_stereo.cs:379` calls `KeepAlive` and `src/OpenCvSharp/Cv2/Cv2_stereo.cs:387` 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 (8 lines × 2) src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:325 — src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:325-333 | src/OpenCvSharp/Modules/core/Algorithm.cs:31-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:339 — src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:339-347 | src/OpenCvSharp/Modules/core/Algorithm.cs:45-52 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×4
  • Duplicated block (9 lines × 2) src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:122 — src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:122-130 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1850-1858 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:122` 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/OpenCvSharp/Cv2/Cv2_geometry.cs:1755 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1755-1763 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1787-1795 — both copies are in the same file, so extract the 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/OpenCvSharp/Cv2/Cv2_geometry.cs:1755` 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 (9 lines × 2) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:237 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:237-245 | src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:341-349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (9 lines × 2) src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:163 — src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:163-171 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1881-1889 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:163` 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 (22 corresponding lines) · ×3
  • Edited copy of a member (22 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:217 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:217-238 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:297-326 — These two members are one piece of code written twice and then edited apart: 22 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 (22 corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2791 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2791-2815 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2857-2878 — These two members are one piece of code written twice and then edited apart: 22 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 (22 corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1302 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1302-1323 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1335-1356 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×3
  • Edited copy of a member (16 corresponding lines) src/OpenCvSharp/Modules/ml/EM.cs:250 — src/OpenCvSharp/Modules/ml/EM.cs:250-273 | src/OpenCvSharp/Modules/ml/TrainData.cs:41-56 — These two members are one piece of code written twice and then edited apart: 16 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 (16 corresponding lines) src/OpenCvSharp/Modules/face/Facemark/FacemarkKazemi.cs:26 — src/OpenCvSharp/Modules/face/Facemark/FacemarkKazemi.cs:26-41 | src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptor.cs:22-38 — These two members are one piece of code written twice and then edited apart: 16 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 (16 corresponding lines) src/OpenCvSharp/Modules/features/Feature2D.cs:92 — src/OpenCvSharp/Modules/features/Feature2D.cs:92-109 | src/OpenCvSharp/Modules/features/Feature2D.cs:119-134 — These two members are one piece of code written twice and then edited apart: 16 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 (5 members, 10+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 10+ corresponding lines) src/OpenCvSharp/Modules/imgproc/GeneralizedHough.cs:185 — src/OpenCvSharp/Modules/imgproc/GeneralizedHough.cs:185-195 | src/OpenCvSharp/Modules/imgproc/LineSegmentDetector.cs:63-72 | src/OpenCvSharp/Modules/video/SparseOpticalFlow.cs:39-52 | src/OpenCvSharp/Modules/ximgproc/DisparityFilter.cs:36-49 | src/OpenCvSharp/Modules/ximgproc/SparseMatchInterpolator.cs:28-40 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:3093 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:3093-3102 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1585-1596 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3292-3303 | src/OpenCvSharp/Modules/ml/KNearest.cs:155-169 | src/OpenCvSharp/Modules/ml/NormalBayesClassifier.cs:73-83 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_objdetect.cs:288 — src/OpenCvSharp/Cv2/Cv2_objdetect.cs:288-299 | src/OpenCvSharp/Modules/quality/QualityGMSD.cs:42-51 | src/OpenCvSharp/Modules/quality/QualityMSE.cs:43-52 | src/OpenCvSharp/Modules/quality/QualityPSNR.cs:65-74 | src/OpenCvSharp/Modules/quality/QualitySSIM.cs:41-50 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 12+ corresponding lines) src/OpenCvSharp/Modules/dnn/Net.cs:403 — src/OpenCvSharp/Modules/dnn/Net.cs:403-414 | src/OpenCvSharp/Modules/face/FaceRecognizer/FaceRecognizer.cs:25-37 | src/OpenCvSharp/Modules/face/FaceRecognizer/FaceRecognizer.cs:45-56 | src/OpenCvSharp/Modules/photo/CalibrateCRF.cs:22-36 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 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, 12+ corresponding lines) src/OpenCvSharp/Modules/face/Cv2.Face.cs:43 — src/OpenCvSharp/Modules/face/Cv2.Face.cs:43-54 | src/OpenCvSharp/Modules/face/Cv2.Face.cs:65-77 | src/OpenCvSharp/Modules/face/Cv2.Face.cs:88-99 | src/OpenCvSharp/Modules/face/Cv2.Face.cs:108-119 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 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, 12+ corresponding lines) src/OpenCvSharp/Modules/flann/Index.cs:151 — src/OpenCvSharp/Modules/flann/Index.cs:151-165 | src/OpenCvSharp/Modules/flann/Index.cs:202-213 | src/OpenCvSharp/Modules/flann/Index.cs:225-239 | src/OpenCvSharp/Modules/flann/Index.cs:251-263 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 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 (5 members, 8+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 8+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:2090 — src/OpenCvSharp/Cv2/Cv2_core.cs:2090-2098 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:989-999 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2174-2184 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:2232-2242 | src/OpenCvSharp/Modules/core/SVD.cs:117-124 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 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.
  • Edited copies of one member (5 members, 8+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:192 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:192-199 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:221-228 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:241-248 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:283-291 | src/OpenCvSharp/Modules/imgproc/GeneralizedHough.cs:144-155 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 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.
  • Edited copies of one member (5 members, 8+ corresponding lines) src/OpenCvSharp/Modules/features/SimpleBlobDetector.cs:304 — src/OpenCvSharp/Modules/features/SimpleBlobDetector.cs:304-311 | src/OpenCvSharp/Modules/imgcodecs/Animation.cs:80-87 | src/OpenCvSharp/Modules/tracking/Legacy/MultiTracker.cs:75-84 | src/OpenCvSharp/Modules/tracking/Legacy/MultiTrackerAlt.cs:131-138 | src/OpenCvSharp/Modules/xstereo/QuasiDenseStereo.cs:76-83 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 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, 9+ corresponding lines) · ×3
  • Edited copies of one member (6 members, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:68 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:68-77 | src/OpenCvSharp/Cv2/Cv2_core.cs:68-78 | src/OpenCvSharp/Cv2/Cv2_core.cs:90-100 | src/OpenCvSharp/Cv2/Cv2_core.cs:1987-1995 | src/OpenCvSharp/Cv2/Cv2_core.cs:2029-2037 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2276-2284 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 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.
  • Edited copies of one member (6 members, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1160 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1160-1168 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1616-1626 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1651-1660 | src/OpenCvSharp/Modules/core/LDA.cs:187-196 | src/OpenCvSharp/Modules/core/LDA.cs:206-215 | src/OpenCvSharp/Modules/photo/ColorCorrectionModel.cs:63-71 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 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.
  • Edited copies of one member (6 members, 9+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Vec/Vec3b.cs:95 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3b.cs:95-103 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec3d.cs:116-124 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec3f.cs:116-124 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec3i.cs:96-104 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec3s.cs:96-104 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec3w.cs:95-103 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 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 (4 members, 9+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 9+ corresponding lines) src/OpenCvSharp/Modules/phase_unwrapping/PhaseUnwrapping.cs:28 — src/OpenCvSharp/Modules/phase_unwrapping/PhaseUnwrapping.cs:28-39 | src/OpenCvSharp/Modules/photo/AlignMTB.cs:79-87 | src/OpenCvSharp/Modules/video/DenseOpticalFlow.cs:33-42 | src/OpenCvSharp/Modules/video/VariationalRefinement.cs:37-47 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:3369 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:3369-3377 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:3394-3402 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:3419-3427 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:3444-3452 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 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, 9+ corresponding lines) src/OpenCvSharp/Modules/aruco/Dictionary.cs:124 — src/OpenCvSharp/Modules/aruco/Dictionary.cs:124-134 | src/OpenCvSharp/Modules/core/FileNodeIterator.cs:168-179 | src/OpenCvSharp/Modules/stitching/Cv2.Detail.Utilities.cs:25-33 | src/OpenCvSharp/Modules/videoio/VideoCapture.cs:1526-1536 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 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 (5 members, 6+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1338 — src/OpenCvSharp/Cv2/Cv2_core.cs:1338-1346 | src/OpenCvSharp/Cv2/Cv2_core.cs:1359-1367 | src/OpenCvSharp/Modules/core/RNG.cs:278-285 | src/OpenCvSharp/Modules/rgbd/DynaFu.cs:156-161 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:1140-1147 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 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.
  • Edited copies of one member (5 members, 6+ corresponding lines) src/OpenCvSharp/Modules/ml/RTrees.cs:150 — src/OpenCvSharp/Modules/ml/RTrees.cs:150-157 | src/OpenCvSharp/Modules/stitching/Blender.cs:87-92 | src/OpenCvSharp/Modules/stitching/Timelapser.cs:77-84 | src/OpenCvSharp/Modules/ximgproc/EdgeFilter/DTFilter.cs:54-62 | src/OpenCvSharp/Modules/ximgproc/EdgeFilter/GuidedFilter.cs:48-56 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 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.
  • Edited copies of one member (5 members, 6+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_photo.cs:41 — src/OpenCvSharp/Cv2/Cv2_photo.cs:41-46 | src/OpenCvSharp/Cv2/Cv2_stereo.cs:442-449 | src/OpenCvSharp/Modules/intensity_transform/Cv2.IntensityTransform.cs:54-59 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:1092-1099 | src/OpenCvSharp/Modules/xphoto/Cv2.XPhoto.cs:205-211 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 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 (3 members, 5+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 5+ corresponding lines) src/OpenCvSharp/Modules/barcode/BarcodeDetector.cs:20 — src/OpenCvSharp/Modules/barcode/BarcodeDetector.cs:20-27 | src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:28-33 | src/OpenCvSharp/Modules/stitching/Stitcher.cs:71-75 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 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, 5+ corresponding lines) src/OpenCvSharp/Internal/Vectors/VectorOfMat.cs:21 — src/OpenCvSharp/Internal/Vectors/VectorOfMat.cs:21-25 | src/OpenCvSharp/Internal/Vectors/VectorOfString.cs:23-27 | src/OpenCvSharp/Internal/Vectors/VectorOfVectorPoint.cs:23-27 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 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, 5+ corresponding lines) src/OpenCvSharp/Modules/photo/ColorCorrectionModel.cs:16 — src/OpenCvSharp/Modules/photo/ColorCorrectionModel.cs:16-20 | src/OpenCvSharp/Modules/tracking/Legacy/MultiTrackerAlt.cs:23-27 | src/OpenCvSharp/Modules/video/KalmanFilter.cs:19-23 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 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 · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:43 — src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:43-52 | src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:264-273 — both copies are in the same file, so extract the 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/OpenCvSharp/Modules/aruco/ArucoDetector.cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/OpenCvSharp/Cv2/Cv2_geometry.cs:39 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:39-48 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:59-68 — both copies are in the same file, so extract the 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/OpenCvSharp/Cv2/Cv2_geometry.cs:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `matrix` to `out double[,]` in one and `double[,]` 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 (10 lines × 2) src/OpenCvSharp/Modules/ximgproc/Segmentation/SelectiveSearchSegmentationStrategy.cs:36 — src/OpenCvSharp/Modules/ximgproc/Segmentation/SelectiveSearchSegmentationStrategy.cs:36-45 | src/OpenCvSharp/Modules/ximgproc/Segmentation/SelectiveSearchSegmentationStrategyMultiple.cs:28-37 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:267 — src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:267-273 | src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:295-301 — both copies are in the same file, so extract the 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/OpenCvSharp/Modules/features/DescriptorMatcher.cs:267` 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 (7 lines × 2) src/OpenCvSharp/Cv2/Cv2_core.cs:1340 — src/OpenCvSharp/Cv2/Cv2_core.cs:1340-1346 | src/OpenCvSharp/Cv2/Cv2_core.cs:1361-1367 — both copies are in the same file, so extract the 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/OpenCvSharp/Cv2/Cv2_core.cs:1340` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `angle` to `InputArray` in one and `OutputArray` 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 (7 lines × 2) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1374 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1374-1382 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:1856-1862 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Cv2/Cv2_geometry.cs:1374` 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1817 — src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1817-1821 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1949-1953 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1947` calls `ThrowIfNull` and `src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1815` 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 (5 lines × 2) src/OpenCvSharp/Modules/rgbd/LargeKinfu.cs:50 — src/OpenCvSharp/Modules/rgbd/LargeKinfu.cs:50-54 | src/OpenCvSharp/Modules/rgbd/LargeKinfuParams.cs:50-54 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/rgbd/LargeKinfu.cs:50` 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 `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 (5 lines × 2) src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:265 — src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:265-269 | src/OpenCvSharp/Modules/stitching/Estimator.cs:60-64 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/stitching/Cv2.Detail.cs:265` 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×3
  • Swallowed exception (empty catch) src/OpenCvSharp/Cv2/Cv2_highgui.cs:87 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/OpenCvSharp/Cv2/Cv2_highgui.cs:110 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/OpenCvSharp/Modules/tracking/TrackerKCF.cs:117 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D3 · God Classes · ClassTooLong · ×2
  • ClassTooLong: NativeMethods src/OpenCvSharp/Internal/PInvoke/NativeMethods/core/NativeMethods_core_Mat.cs — ClassTooLong — 12147 significant lines (blank, comment-only and punctuation-only lines excluded), 4738 methods, declared across 172 files: core/NativeMethods_core_Mat.cs (202), NativeMethods/NativeMethods_stdvector.cs (189), geometry/NativeMethods_geometry.cs (183), core/NativeMethods_core.cs (165), +168 more file(s). The bar is 400 significant lines; this is 11747 over it, 30.37× the bar. Its members are declarations rather than behaviour over shared data — the type holds no instance state — so there is nothing to group them by and nothing to delegate. To reduce it, split it by area instead: move each cohesive group of declarations onto its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: HOGDescriptor src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs — ClassTooLong — 1618 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 1218 over it, 4.05× 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.
D3 · God Classes · MethodTooLong · ×2
  • MethodTooLong: BitmapConverter.ToMat src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:45 — MethodTooLong — ToMat runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CvExtensions.HoughLinesProbabilisticEx src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:24 — MethodTooLong — HoughLinesProbabilisticEx runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:91 — src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:91-115 | src/OpenCvSharp/Modules/text/OCRHMMDecoder.cs:90-114 | src/OpenCvSharp/Modules/text/OCRHolisticWordRecognizer.cs:54-78 | src/OpenCvSharp/Modules/text/OCRTesseract.cs:69-92 — 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/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:126 — src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:126-154 | src/OpenCvSharp/Modules/text/OCRHMMDecoder.cs:125-153 | src/OpenCvSharp/Modules/text/OCRHolisticWordRecognizer.cs:99-127 | src/OpenCvSharp/Modules/text/OCRTesseract.cs:118-144 — 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 (25 corresponding lines) · ×2
  • Edited copy of a member (25 corresponding lines) src/OpenCvSharp/Internal/Vectors/StdVector.cs:184 — src/OpenCvSharp/Internal/Vectors/StdVector.cs:184-208 | src/OpenCvSharp/Internal/Vectors/StdVector.cs:211-235 — These two members are one piece of code written twice and then edited apart: 25 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 (25 corresponding lines) src/OpenCvSharp/Modules/video/TrackerDaSiamRPN.cs:24 — src/OpenCvSharp/Modules/video/TrackerDaSiamRPN.cs:24-51 | src/OpenCvSharp/Modules/video/TrackerNano.cs:25-49 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×2
  • Edited copy of a member (23 corresponding lines) src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1981 — src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1981-2014 | src/OpenCvSharp/Modules/stitching/Stitcher.cs:223-245 — These two members are one piece of code written twice and then edited apart: 23 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 (23 corresponding lines) src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:15 — src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:15-38 | src/OpenCvSharp/Modules/rgbd/KinFuParams.cs:18-40 — These two members are one piece of code written twice and then edited apart: 23 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, 22+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 22+ corresponding lines) src/OpenCvSharp/Modules/core/Mat/Mat.cs:334 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:334-355 | src/OpenCvSharp/Modules/core/Mat/Mat.cs:370-393 | src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:234-256 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 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, 22+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:1401 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:1401-1430 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1469-1490 | src/OpenCvSharp/Cv2/Cv2_stereo.cs:288-315 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 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, 12+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 12+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:147 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:147-158 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:3261-3272 | src/OpenCvSharp/Modules/ccalib/Cv2.Omnidir.cs:25-36 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 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, 12+ corresponding lines) src/OpenCvSharp/Modules/ptcloud/Odometry.cs:116 — src/OpenCvSharp/Modules/ptcloud/Odometry.cs:116-127 | src/OpenCvSharp/Modules/tracking/Legacy/MultiTracker.cs:37-51 | src/OpenCvSharp/Modules/tracking/Legacy/MultiTrackerAlt.cs:71-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 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 (4 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 15+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:1174 — src/OpenCvSharp/Cv2/Cv2_core.cs:1174-1188 | src/OpenCvSharp/Cv2/Cv2_core.cs:1233-1247 | src/OpenCvSharp/Modules/rapid/CvRapid.cs:71-89 | src/OpenCvSharp/Modules/xphoto/Cv2.XPhoto.cs:151-165 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 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, 15+ corresponding lines) src/OpenCvSharp/Modules/face/Facemark/FacemarkAAM.cs:267 — src/OpenCvSharp/Modules/face/Facemark/FacemarkAAM.cs:267-282 | src/OpenCvSharp/Modules/face/Facemark/FacemarkAAM.cs:289-303 | src/OpenCvSharp/Modules/face/Facemark/FacemarkLBF.cs:205-220 | src/OpenCvSharp/Modules/face/Facemark/FacemarkLBF.cs:227-241 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 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, 11+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 11+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:790 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:790-800 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:816-826 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:843-854 | src/OpenCvSharp/Cv2/Cv2_video.cs:128-138 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 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, 11+ corresponding lines) src/OpenCvSharp/Modules/face/Facemark/FacemarkAAM.cs:197 — src/OpenCvSharp/Modules/face/Facemark/FacemarkAAM.cs:197-210 | src/OpenCvSharp/Modules/face/Facemark/FacemarkKazemi.cs:152-162 | src/OpenCvSharp/Modules/face/Facemark/FacemarkLBF.cs:99-112 | src/OpenCvSharp/Modules/line_descriptors/BinaryDescriptor.cs:237-249 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 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, 10+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_geometry.cs:91 — src/OpenCvSharp/Cv2/Cv2_geometry.cs:91-102 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1752-1763 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1784-1795 | src/OpenCvSharp/Cv2/Cv2_video.cs:256-265 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_photo.cs:156 — src/OpenCvSharp/Cv2/Cv2_photo.cs:156-165 | src/OpenCvSharp/Modules/ximgproc/Cv2.XImgProc.cs:357-368 | src/OpenCvSharp/Modules/ximgproc/RFFeatureGetter.cs:56-69 | src/OpenCvSharp/Modules/xphoto/Cv2.XPhoto.cs:126-137 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 12+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 12+ corresponding lines) src/OpenCvSharp/Modules/tracking/Legacy/LegacyTracker.cs:29 — src/OpenCvSharp/Modules/tracking/Legacy/LegacyTracker.cs:29-40 | src/OpenCvSharp/Modules/tracking/Legacy/LegacyTracker.cs:55-66 | src/OpenCvSharp/Modules/tracking/Legacy/MultiTracker.cs:58-69 | src/OpenCvSharp/Modules/tracking/Legacy/MultiTrackerAlt.cs:98-109 | src/OpenCvSharp/Modules/tracking/Legacy/MultiTrackerTLD.cs:61-72 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 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.
  • Edited copies of one member (5 members, 12+ corresponding lines) src/OpenCvSharp/Modules/videoio/VideoWriter.cs:96 — src/OpenCvSharp/Modules/videoio/VideoWriter.cs:96-107 | src/OpenCvSharp/Modules/videoio/VideoWriter.cs:120-132 | src/OpenCvSharp/Modules/videoio/VideoWriter.cs:148-159 | src/OpenCvSharp/Modules/videoio/VideoWriter.cs:174-186 | src/OpenCvSharp/Modules/videoio/VideoWriter.cs:335-349 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 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, 6+ corresponding lines) · ×2
  • Edited copies of one member (6 members, 6+ corresponding lines) src/OpenCvSharp/Modules/flann/IndexParams/SearchParams.cs:40 — src/OpenCvSharp/Modules/flann/IndexParams/SearchParams.cs:40-48 | src/OpenCvSharp/Modules/photo/AlignMTB.cs:18-24 | src/OpenCvSharp/Modules/photo/CalibrateDebevec.cs:27-32 | src/OpenCvSharp/Modules/video/BackgroundSubtractorKNN.cs:24-30 | src/OpenCvSharp/Modules/video/BackgroundSubtractorMog2.cs:26-32 | src/OpenCvSharp/Modules/ximgproc/EdgeFilter/AdaptiveManifoldFilter.cs:45-52 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 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.
  • Edited copies of one member (6 members, 6+ corresponding lines) src/OpenCvSharp/Modules/bgsegm/BackgroundSubtractorMOG.cs:21 — src/OpenCvSharp/Modules/bgsegm/BackgroundSubtractorMOG.cs:21-27 | src/OpenCvSharp/Modules/flann/IndexParams/AutotunedIndexParams.cs:35-43 | src/OpenCvSharp/Modules/flann/IndexParams/HierarchicalClusteringIndexParams.cs:30-38 | src/OpenCvSharp/Modules/flann/IndexParams/KMeansIndexParams.cs:29-37 | src/OpenCvSharp/Modules/photo/TonemapReinhard.cs:32-37 | src/OpenCvSharp/Modules/xfeatures2d/TBMR.cs:28-33 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 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, 4+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 4+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Rect.cs:293 — src/OpenCvSharp/Modules/core/Struct/Rect.cs:293-296 | src/OpenCvSharp/Modules/core/Struct/Rect2d.cs:302-305 | src/OpenCvSharp/Modules/core/Struct/Rect2f.cs:287-290 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 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, 4+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Rect.cs:361 — src/OpenCvSharp/Modules/core/Struct/Rect.cs:361-364 | src/OpenCvSharp/Modules/core/Struct/Rect2d.cs:370-373 | src/OpenCvSharp/Modules/core/Struct/Rect2f.cs:357-360 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 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, 3+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 3+ corresponding lines) src/OpenCvSharp/Modules/core/Struct/Point.cs:136 — src/OpenCvSharp/Modules/core/Struct/Point.cs:136-138 | src/OpenCvSharp/Modules/core/Struct/Point2d.cs:134-136 | src/OpenCvSharp/Modules/core/Struct/Point2f.cs:139-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 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, 3+ corresponding lines) src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:599 — src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:599-601 | src/OpenCvSharp/Modules/core/Mat/UMat.cs:1011-1013 | src/OpenCvSharp/Modules/core/NativeMatExpr.cs:542-544 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 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 · Duplicated block (21 lines × 2) · ×2
  • Duplicated block (21 lines × 2) src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:18 — src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:18-38 | src/OpenCvSharp/Modules/rgbd/KinFuParams.cs:20-40 — before extracting anything, compare `src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs` and `src/OpenCvSharp/Modules/rgbd/KinFuParams.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:18` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `p` to `CvColoredKinFuParams` in one and `CvKinFuParams` 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 (21 lines × 2) src/OpenCvSharp/Modules/rgbd/DynaFu.cs:36 — src/OpenCvSharp/Modules/rgbd/DynaFu.cs:36-56 | src/OpenCvSharp/Modules/rgbd/KinFu.cs:35-55 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:47 — src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:47-52 | src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:57-62 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:47` 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 (6 lines × 2) src/OpenCvSharp/Cv2/Cv2_core.cs:2092 — src/OpenCvSharp/Cv2/Cv2_core.cs:2092-2098 | src/OpenCvSharp/Modules/core/SVD.cs:119-124 — 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/OpenCvSharp/Cv2/Cv2_core.cs:2092` 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.
X18 · Disposal-pattern correctness · Finalizer on a type that owns no unmanaged resource · ×2
  • Finalizer on a type that owns no unmanaged resource src/OpenCvSharp/Modules/aruco/CharucoParameters.cs:36 — `CharucoParameters` declares a finalizer (line 36), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
  • Finalizer on a type that owns no unmanaged resource src/OpenCvSharp/Modules/stitching/ImageFeatures.cs:36 — `ImageFeatures` declares a finalizer (line 36), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
D1 · Cyclomatic Complexity · InputArray.EstimateType (cyclomatic 45) · ×1
  • InputArray.EstimateType (cyclomatic 45) src/OpenCvSharp/Modules/core/InputArray.cs:326 — InputArray.EstimateType has cyclomatic complexity 45 (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.
D1 · Cyclomatic Complexity · BitmapConverter.ToMat (cyclomatic 40) · ×1
  • BitmapConverter.ToMat (cyclomatic 40) src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:45 — BitmapConverter.ToMat has cyclomatic complexity 40 (threshold 15). Of this number, 34 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CvExtensions.HoughLinesProbabilisticEx (cyclomatic 36) · ×1
  • CvExtensions.HoughLinesProbabilisticEx (cyclomatic 36) src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:24 — CvExtensions.HoughLinesProbabilisticEx has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · StdVector.New1 (cyclomatic 23) · ×1
  • StdVector.New1 (cyclomatic 23) src/OpenCvSharp/Internal/Vectors/StdVector.cs:117 — StdVector.New1 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. This shape REPEATS in the file: 3 other methods here (StdVector.GetSize, StdVector.GetPointer, StdVector.Delete) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
D1 · Cyclomatic Complexity · StdVector.GetSize (cyclomatic 23) · ×1
  • StdVector.GetSize (cyclomatic 23) src/OpenCvSharp/Internal/Vectors/StdVector.cs:183 — StdVector.GetSize 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. This shape REPEATS in the file: 3 other methods here (StdVector.New1, StdVector.GetPointer, StdVector.Delete) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
D1 · Cyclomatic Complexity · StdVector.GetPointer (cyclomatic 23) · ×1
  • StdVector.GetPointer (cyclomatic 23) src/OpenCvSharp/Internal/Vectors/StdVector.cs:210 — StdVector.GetPointer 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. This shape REPEATS in the file: 3 other methods here (StdVector.New1, StdVector.GetSize, StdVector.Delete) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
D1 · Cyclomatic Complexity · StdVector.Delete (cyclomatic 23) · ×1
  • StdVector.Delete (cyclomatic 23) src/OpenCvSharp/Internal/Vectors/StdVector.cs:237 — StdVector.Delete 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. This shape REPEATS in the file: 3 other methods here (StdVector.New1, StdVector.GetSize, StdVector.GetPointer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
D1 · Cyclomatic Complexity · LineSegmentPoint.IntersectedSegments (cyclomatic 21) · ×1
  • LineSegmentPoint.IntersectedSegments (cyclomatic 21) src/OpenCvSharp/Modules/imgproc/Model/LineSegmentPoint.cs:186 — LineSegmentPoint.IntersectedSegments has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BitmapConverter.ToBitmap (cyclomatic 20) · ×1
  • BitmapConverter.ToBitmap (cyclomatic 20) src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:321 — BitmapConverter.ToBitmap has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BitmapSourceConverter.ToMat (cyclomatic 18) · ×1
  • BitmapSourceConverter.ToMat (cyclomatic 18) src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:121 — BitmapSourceConverter.ToMat has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · StdVector.New3 (cyclomatic 17) · ×1
  • StdVector.New3 (cyclomatic 17) src/OpenCvSharp/Internal/Vectors/StdVector.cs:162 — StdVector.New3 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.
D1 · Cyclomatic Complexity · CvVideoStab.Stabilize (cyclomatic 17) · ×1
  • CvVideoStab.Stabilize (cyclomatic 17) src/OpenCvSharp/Modules/videostab/CvVideoStab.cs:14 — CvVideoStab.Stabilize has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · WriteableBitmapConverter.GetOptimumPixelFormats (cyclomatic 16) · ×1
  • WriteableBitmapConverter.GetOptimumPixelFormats (cyclomatic 16) src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:98 — WriteableBitmapConverter.GetOptimumPixelFormats 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.
D17 · Explicit Debt · BareSuppressMessage repeated across 68 files · ×1
  • BareSuppressMessage repeated across 68 files src/OpenCvSharp/Cv2/Cv2_calib.cs:723 — The identical BareSuppressMessage (`SuppressMessage`) appears in 68 files (111 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 111 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · BarePragmaDisable repeated across 56 files · ×1
  • BarePragmaDisable repeated across 56 files src/OpenCvSharp/Modules/core/FileNodeIterator.cs:128 — The identical BarePragmaDisable (`#pragma warning disable 1591`) appears in 56 files (71 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 71 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · DeadPreprocessorBranch · ×1
  • DeadPreprocessorBranch src/OpenCvSharp/Modules/features/DenseFeatureDetector.cs:1 — #if false — 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.
D2 · Cognitive Complexity · CvExtensions.HoughLinesProbabilisticEx (cognitive 88) · ×1
  • CvExtensions.HoughLinesProbabilisticEx (cognitive 88) src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:24 — CvExtensions.HoughLinesProbabilisticEx has cognitive complexity 88 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BitmapConverter.ToMat (cognitive 57) · ×1
  • BitmapConverter.ToMat (cognitive 57) src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:45 — BitmapConverter.ToMat has cognitive complexity 57 (threshold 15). Of this number, 47 points are the body's own statements and 10 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BitmapSourceConverter.ToMat (cognitive 47) · ×1
  • BitmapSourceConverter.ToMat (cognitive 47) src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:121 — BitmapSourceConverter.ToMat has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InputArray.EstimateType (cognitive 36) · ×1
  • InputArray.EstimateType (cognitive 36) src/OpenCvSharp/Modules/core/InputArray.cs:326 — InputArray.EstimateType has cognitive complexity 36 (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.
D2 · Cognitive Complexity · BitmapConverter.ToBitmap (cognitive 34) · ×1
  • BitmapConverter.ToBitmap (cognitive 34) src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:321 — BitmapConverter.ToBitmap has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WriteableBitmapConverter.ToWriteableBitmap (cognitive 30) · ×1
  • WriteableBitmapConverter.ToWriteableBitmap (cognitive 30) src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:211 — WriteableBitmapConverter.ToWriteableBitmap has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WriteableBitmapConverter.ToMat (cognitive 30) · ×1
  • WriteableBitmapConverter.ToMat (cognitive 30) src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:318 — WriteableBitmapConverter.ToMat has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LineSegmentPoint.IntersectedSegments (cognitive 26) · ×1
  • LineSegmentPoint.IntersectedSegments (cognitive 26) src/OpenCvSharp/Modules/imgproc/Model/LineSegmentPoint.cs:186 — LineSegmentPoint.IntersectedSegments has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StdVector.New1 (cognitive 22) · ×1
  • StdVector.New1 (cognitive 22) src/OpenCvSharp/Internal/Vectors/StdVector.cs:117 — StdVector.New1 has cognitive complexity 22 (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. This shape REPEATS in the file: 3 other methods here (StdVector.GetSize, StdVector.GetPointer, StdVector.Delete) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
D2 · Cognitive Complexity · StdVector.GetSize (cognitive 22) · ×1
  • StdVector.GetSize (cognitive 22) src/OpenCvSharp/Internal/Vectors/StdVector.cs:183 — StdVector.GetSize has cognitive complexity 22 (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. This shape REPEATS in the file: 3 other methods here (StdVector.New1, StdVector.GetPointer, StdVector.Delete) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
D2 · Cognitive Complexity · StdVector.GetPointer (cognitive 22) · ×1
  • StdVector.GetPointer (cognitive 22) src/OpenCvSharp/Internal/Vectors/StdVector.cs:210 — StdVector.GetPointer has cognitive complexity 22 (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. This shape REPEATS in the file: 3 other methods here (StdVector.New1, StdVector.GetSize, StdVector.Delete) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
D2 · Cognitive Complexity · StdVector.Delete (cognitive 22) · ×1
  • StdVector.Delete (cognitive 22) src/OpenCvSharp/Internal/Vectors/StdVector.cs:237 — StdVector.Delete has cognitive complexity 22 (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. This shape REPEATS in the file: 3 other methods here (StdVector.New1, StdVector.GetSize, StdVector.GetPointer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
D2 · Cognitive Complexity · StdVector.New3 (cognitive 16) · ×1
  • StdVector.New3 (cognitive 16) src/OpenCvSharp/Internal/Vectors/StdVector.cs:162 — StdVector.New3 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.
D2 · Cognitive Complexity · CvVideoStab.Stabilize (cognitive 16) · ×1
  • CvVideoStab.Stabilize (cognitive 16) src/OpenCvSharp/Modules/videostab/CvVideoStab.cs:14 — CvVideoStab.Stabilize has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/OpenCvSharp/Modules/core/Struct/Vec/Vec6b.cs:125 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6b.cs:125-136 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:155-166 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:156-167 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6i.cs:126-137 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6s.cs:126-137 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6w.cs:125-136 — 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 · Edited copies of one member (3 members, 36+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 36+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.cs:732 — src/OpenCvSharp/Cv2/Cv2_calib.cs:732-772 | src/OpenCvSharp/Cv2/Cv2_calib.cs:812-847 | src/OpenCvSharp/Cv2/Cv2_calib.cs:887-929 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 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 (69 corresponding lines) · ×1
  • Edited copy of a member (69 corresponding lines) src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:212 — src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:212-288 | src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:319-387 — These two members are one piece of code written twice and then edited apart: 69 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, 26+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 26+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:236 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:236-261 | src/OpenCvSharp/Cv2/Cv2_calib.cs:259-285 | src/OpenCvSharp/Cv2/Cv2_calib.cs:384-411 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 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, 21+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 21+ corresponding lines) src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:34 — src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:34-55 | src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:45-65 | src/OpenCvSharp/Modules/rgbd/KinFuParams.cs:47-67 | src/OpenCvSharp/Modules/rgbd/LargeKinfu.cs:38-61 | src/OpenCvSharp/Modules/rgbd/LargeKinfuParams.cs:39-61 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 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, 19+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 19+ corresponding lines) src/OpenCvSharp/Modules/stitching/ExposureCompensator.cs:65 — src/OpenCvSharp/Modules/stitching/ExposureCompensator.cs:65-85 | src/OpenCvSharp/Modules/stitching/FeatherBlender.cs:52-75 | src/OpenCvSharp/Modules/stitching/GraphCutSeamFinder.cs:43-61 | src/OpenCvSharp/Modules/stitching/SeamFinder.cs:60-78 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) src/OpenCvSharp/Modules/aruco/Cv2.Aruco.cs:37 — src/OpenCvSharp/Modules/aruco/Cv2.Aruco.cs:37-57 | src/OpenCvSharp/Modules/aruco/Cv2.Aruco.cs:150-173 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) src/OpenCvSharp/Modules/core/Mat/MatPixelBlit.cs:24 — src/OpenCvSharp/Modules/core/Mat/MatPixelBlit.cs:24-52 | src/OpenCvSharp/Modules/core/Mat/MatPixelBlit.cs:70-98 — 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.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) src/OpenCvSharp/Modules/objdetect/FaceDetectorYN.cs:82 — src/OpenCvSharp/Modules/objdetect/FaceDetectorYN.cs:82-105 | src/OpenCvSharp/Modules/objdetect/FaceRecognizerSF.cs:78-97 — These two members are one piece of code written twice and then edited apart: 20 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, 20+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 20+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:682 — src/OpenCvSharp/Cv2/Cv2_core.cs:682-705 | src/OpenCvSharp/Cv2/Cv2_core.cs:915-934 | src/OpenCvSharp/Cv2/Cv2_core.cs:958-977 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 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, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:310 — src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:310-327 | src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:341-359 | src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:371-389 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 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, 17+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 17+ corresponding lines) src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:121 — src/OpenCvSharp/Modules/objdetect/CascadeClassifier.cs:121-137 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1781-1798 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1814-1833 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1849-1865 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1881-1899 | src/OpenCvSharp/Modules/objdetect/HOGDescriptor.cs:1945-1964 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) src/OpenCvSharp/Modules/face/Facemark/FacemarkAAM.cs:23 — src/OpenCvSharp/Modules/face/Facemark/FacemarkAAM.cs:23-48 | src/OpenCvSharp/Modules/face/Facemark/FacemarkLBF.cs:23-48 — These two members are one piece of code written twice and then edited apart: 26 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 (6 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 16+ corresponding lines) src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:99 — src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:99-117 | src/OpenCvSharp/Modules/aruco/ArucoDetector.cs:133-151 | src/OpenCvSharp/Modules/aruco/CharucoDetector.cs:66-86 | src/OpenCvSharp/Modules/aruco/CharucoDetector.cs:97-117 | src/OpenCvSharp/Modules/dnn/DetectionModel.cs:86-101 | src/OpenCvSharp/Modules/imgproc/LineSegmentDetector.cs:87-103 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 16 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, 16+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 16+ corresponding lines) src/OpenCvSharp/Internal/Vectors/VectorOfVectorByte.cs:57 — src/OpenCvSharp/Internal/Vectors/VectorOfVectorByte.cs:57-72 | src/OpenCvSharp/Internal/Vectors/VectorOfVectorDMatch.cs:57-72 | src/OpenCvSharp/Internal/Vectors/VectorOfVectorDouble.cs:57-72 | src/OpenCvSharp/Internal/Vectors/VectorOfVectorInt32.cs:57-72 | src/OpenCvSharp/Internal/Vectors/VectorOfVectorKeyLine.cs:59-74 | src/OpenCvSharp/Internal/Vectors/VectorOfVectorKeyPoint.cs:71-86 | src/OpenCvSharp/Internal/Vectors/VectorOfVectorPoint.cs:68-83 | src/OpenCvSharp/Internal/Vectors/VectorOfVectorPoint2f.cs:58-73 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 16 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 (6 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 14+ corresponding lines) src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:284 — src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:284-297 | src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:314-327 | src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:344-357 | src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:375-390 | src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:408-423 | src/OpenCvSharp/Modules/dnn/Cv2.Dnn.cs:444-459 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 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 (4 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 14+ corresponding lines) src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:33 — src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:33-48 | src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:68-81 | src/OpenCvSharp/Modules/text/OCRHMMDecoder.cs:32-47 | src/OpenCvSharp/Modules/text/OCRHMMDecoder.cs:67-80 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 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, 16+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 16+ corresponding lines) src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:106 — src/OpenCvSharp/Modules/rgbd/ColoredKinFu.cs:106-121 | src/OpenCvSharp/Modules/rgbd/DynaFu.cs:107-122 | src/OpenCvSharp/Modules/rgbd/KinFu.cs:108-123 | src/OpenCvSharp/Modules/rgbd/LargeKinfu.cs:112-127 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 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, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) src/OpenCvSharp/Modules/videoio/VideoCapture.cs:1147 — src/OpenCvSharp/Modules/videoio/VideoCapture.cs:1147-1164 | src/OpenCvSharp/Modules/videoio/VideoCapture.cs:1185-1203 | src/OpenCvSharp/Modules/videoio/VideoCapture.cs:1237-1252 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 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 (7 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 10+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_objdetect.cs:181 — src/OpenCvSharp/Cv2/Cv2_objdetect.cs:181-190 | src/OpenCvSharp/Modules/face/Facemark/FacemarkKazemi.cs:81-90 | src/OpenCvSharp/Modules/face/Facemark/FacemarkTrain.cs:49-58 | src/OpenCvSharp/Modules/objdetect/QRCodeDetector.cs:62-72 | src/OpenCvSharp/Modules/objdetect/QRCodeDetector.cs:128-138 | src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:82-93 | src/OpenCvSharp/Modules/objdetect/QRCodeDetectorAruco.cs:151-162 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) src/OpenCvSharp/Modules/face/Facemark/Facemark.cs:45 — src/OpenCvSharp/Modules/face/Facemark/Facemark.cs:45-59 | src/OpenCvSharp/Modules/features/MSER.cs:146-159 | src/OpenCvSharp/Modules/xfeatures2d/BOWImgDescriptorExtractor.cs:117-129 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 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, 11+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 11+ corresponding lines) src/OpenCvSharp/Modules/features/AffineFeature.cs:32 — src/OpenCvSharp/Modules/features/AffineFeature.cs:32-42 | src/OpenCvSharp/Modules/features/DISK.cs:64-74 | src/OpenCvSharp/Modules/features/LightGlueMatcher.cs:55-65 | src/OpenCvSharp/Modules/text/ERFilter.cs:30-41 | src/OpenCvSharp/Modules/text/ERFilter.cs:76-86 | src/OpenCvSharp/Modules/ximgproc/DisparityWLSFilter.cs:28-38 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 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 (7 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 7+ corresponding lines) src/OpenCvSharp/Modules/quality/QualityPSNR.cs:48 — src/OpenCvSharp/Modules/quality/QualityPSNR.cs:48-54 | src/OpenCvSharp/Modules/ximgproc/EdgeFilter/DTFilter.cs:36-44 | src/OpenCvSharp/Modules/ximgproc/EdgeFilter/FastBilateralSolverFilter.cs:34-42 | src/OpenCvSharp/Modules/ximgproc/EdgeFilter/FastGlobalSmootherFilter.cs:32-40 | src/OpenCvSharp/Modules/ximgproc/EdgeFilter/GuidedFilter.cs:31-39 | src/OpenCvSharp/Modules/ximgproc/Superpixel/SuperpixelLSC.cs:41-49 | src/OpenCvSharp/Modules/ximgproc/Superpixel/SuperpixelSLIC.cs:41-49 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 7 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 copies of one member (5 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 7+ corresponding lines) src/OpenCvSharp/Modules/optflow/DualTVL1OpticalFlow.cs:44 — src/OpenCvSharp/Modules/optflow/DualTVL1OpticalFlow.cs:44-52 | src/OpenCvSharp/Modules/xfeatures2d/MSDDetector.cs:33-40 | src/OpenCvSharp/Modules/ximgproc/FastLineDetector.cs:32-38 | src/OpenCvSharp/Modules/ximgproc/ScanSegment.cs:44-51 | src/OpenCvSharp/Modules/ximgproc/Superpixel/SuperpixelSEEDS.cs:58-66 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 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 (7 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 9+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_photo.cs:91 — src/OpenCvSharp/Cv2/Cv2_photo.cs:91-103 | src/OpenCvSharp/Cv2/Cv2_photo.cs:124-134 | src/OpenCvSharp/Modules/dnn/Net.cs:387-395 | src/OpenCvSharp/Modules/photo/MergeMertens.cs:41-51 | src/OpenCvSharp/Modules/stitching/Stitcher.cs:303-314 | src/OpenCvSharp/Modules/stitching/Stitcher.cs:383-393 | src/OpenCvSharp/Modules/stitching/Stitcher.cs:419-431 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 9 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 copies of one member (7 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 6+ corresponding lines) src/OpenCvSharp/Modules/face/FaceRecognizer/LBPHFaceRecognizer.cs:40 — src/OpenCvSharp/Modules/face/FaceRecognizer/LBPHFaceRecognizer.cs:40-47 | src/OpenCvSharp/Modules/features/SIFT.cs:35-43 | src/OpenCvSharp/Modules/flann/IndexParams/CompositeIndexParams.cs:31-39 | src/OpenCvSharp/Modules/shape/ShapeContextDistanceExtractor.cs:36-42 | src/OpenCvSharp/Modules/xfeatures2d/HarrisLaplaceFeatureDetector.cs:28-34 | src/OpenCvSharp/Modules/xfeatures2d/StarDetector.cs:31-38 | src/OpenCvSharp/Modules/xphoto/TonemapDurand.cs:37-42 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 6 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 copies of one member (4 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 8+ corresponding lines) src/OpenCvSharp/Modules/shape/ChiHistogramCostExtractor.cs:20 — src/OpenCvSharp/Modules/shape/ChiHistogramCostExtractor.cs:20-27 | src/OpenCvSharp/Modules/shape/EMDHistogramCostExtractor.cs:22-29 | src/OpenCvSharp/Modules/shape/EMDL1HistogramCostExtractor.cs:20-27 | src/OpenCvSharp/Modules/shape/NormHistogramCostExtractor.cs:22-29 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 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 (8 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 8+ corresponding lines) src/OpenCvSharp/Modules/dnn/ClassificationModel.cs:38 — src/OpenCvSharp/Modules/dnn/ClassificationModel.cs:38-45 | src/OpenCvSharp/Modules/dnn/DetectionModel.cs:39-46 | src/OpenCvSharp/Modules/dnn/KeypointsModel.cs:39-46 | src/OpenCvSharp/Modules/dnn/Model.cs:47-54 | src/OpenCvSharp/Modules/dnn/SegmentationModel.cs:38-45 | src/OpenCvSharp/Modules/dnn/TextDetectionModelDB.cs:35-42 | src/OpenCvSharp/Modules/dnn/TextDetectionModelEAST.cs:35-42 | src/OpenCvSharp/Modules/dnn/TextRecognitionModel.cs:40-47 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 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 (4 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 5+ corresponding lines) src/OpenCvSharp/Cv2/Cv2_core.cs:568 — src/OpenCvSharp/Cv2/Cv2_core.cs:568-573 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:2691-2695 | src/OpenCvSharp/Modules/dnn/ClassificationModel.cs:77-83 | src/OpenCvSharp/Modules/face/FaceRecognizer/FaceRecognizer.cs:80-86 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 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 · Duplicated block (59 lines × 2) · ×1
  • Duplicated block (59 lines × 2) src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:117 — src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:117-175 | src/OpenCvSharp/Modules/rgbd/KinFuParams.cs:115-173 — before extracting anything, compare `src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs` and `src/OpenCvSharp/Modules/rgbd/KinFuParams.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:75 — src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:75-107 | src/OpenCvSharp/Modules/tracking/TrackerCSRT.cs:76-108 — before extracting anything, compare `src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs` and `src/OpenCvSharp/Modules/tracking/TrackerCSRT.cs` as WHOLE FILES: 82% 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/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:75` 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 · Duplicated block (26–30 lines × 2) · ×1
  • Duplicated block (26–30 lines × 2) src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:152 — src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:152-177 | src/OpenCvSharp/Modules/imgproc/CvExtensions.cs:204-233 — both copies are in the same file, so extract the 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/OpenCvSharp/Modules/imgproc/CvExtensions.cs:152` 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.
D4 · Code Duplication · Duplicated block (21–27 lines × 4) · ×1
  • Duplicated block (21–27 lines × 4) src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:90 — src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:90-116 | src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs:173-193 | src/OpenCvSharp/Modules/tracking/TrackerCSRT.cs:91-117 | src/OpenCvSharp/Modules/tracking/TrackerCSRT.cs:173-193 — before extracting anything, compare `src/OpenCvSharp/Modules/tracking/Legacy/TrackerCSRT.cs` and `src/OpenCvSharp/Modules/tracking/TrackerCSRT.cs` as WHOLE FILES: 82% 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.
D4 · Code Duplication · Duplicated block (25 lines × 4) · ×1
  • Duplicated block (25 lines × 4) src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:128 — src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:128-152 | src/OpenCvSharp/Modules/text/OCRHMMDecoder.cs:127-151 | src/OpenCvSharp/Modules/text/OCRHolisticWordRecognizer.cs:101-125 | src/OpenCvSharp/Modules/text/OCRTesseract.cs:119-143 — 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 4 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/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:127` calls `ThrowIfDisposed` and `src/OpenCvSharp/Modules/text/OCRTesseract.cs:118` 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.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1
  • Duplicated block (20 lines × 3) src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:120 — src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs:120-139 | src/OpenCvSharp/Modules/rgbd/KinFuParams.cs:118-137 | src/OpenCvSharp/Modules/rgbd/LargeKinfuParams.cs:96-115 — before extracting anything, compare `src/OpenCvSharp/Modules/rgbd/ColoredKinFuParams.cs` and `src/OpenCvSharp/Modules/rgbd/KinFuParams.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (23 lines × 4) · ×1
  • Duplicated block (23 lines × 4) src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:93 — src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:93-115 | src/OpenCvSharp/Modules/text/OCRHMMDecoder.cs:92-114 | src/OpenCvSharp/Modules/text/OCRHolisticWordRecognizer.cs:56-78 | src/OpenCvSharp/Modules/text/OCRTesseract.cs:70-92 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:93` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/OpenCvSharp/Modules/text/OCRBeamSearchDecoder.cs:92` calls `ThrowIfDisposed` and `src/OpenCvSharp/Modules/text/OCRTesseract.cs:69` 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) src/OpenCvSharp/Internal/PInvoke/NativeMethods/rgbd/NativeMethods_rgbd_colored_kinfu.cs:23 — src/OpenCvSharp/Internal/PInvoke/NativeMethods/rgbd/NativeMethods_rgbd_colored_kinfu.cs:23-38 | src/OpenCvSharp/Internal/PInvoke/NativeMethods/rgbd/NativeMethods_rgbd_kinfu.cs:23-38 — 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) src/OpenCvSharp/Modules/core/Mat/Mat.cs:339 — src/OpenCvSharp/Modules/core/Mat/Mat.cs:339-354 | src/OpenCvSharp/Modules/core/Mat/MatOfT.cs:241-255 — 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. 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 `data` to `IntPtr` in one and `Array` 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/OpenCvSharp/Modules/core/Mat/MatOfT.cs:241` calls `GetMatType` and `src/OpenCvSharp/Modules/core/Mat/Mat.cs:339` does not — after which the two agree again for 5 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) src/OpenCvSharp/Cv2/Cv2_core.cs:916 — src/OpenCvSharp/Cv2/Cv2_core.cs:916-928 | src/OpenCvSharp/Cv2/Cv2_core.cs:959-971 — both copies are in the same file, so extract the 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/OpenCvSharp/Cv2/Cv2_core.cs:916` 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 · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:342 — src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:342-352 | src/OpenCvSharp/Modules/features/DescriptorMatcher.cs:372-382 — both copies are in the same file, so extract the 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/OpenCvSharp/Modules/features/DescriptorMatcher.cs:342` 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 · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) src/OpenCvSharp/Modules/ximgproc/EdgeBoxes.cs:304 — src/OpenCvSharp/Modules/ximgproc/EdgeBoxes.cs:304-315 | src/OpenCvSharp/Modules/ximgproc/StructuredEdgeDetection.cs:43-53 — 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.
D4 · Code Duplication · Duplicated block (9–11 lines × 3) · ×1
  • Duplicated block (9–11 lines × 3) src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:121 — src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:121-130 | src/OpenCvSharp/Cv2/Cv2_geometry.cs:1914-1924 | src/OpenCvSharp/Modules/ccalib/Cv2.Omnidir.cs:49-57 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Cv2/Cv2_calib.FishEye.cs:121` 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.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) src/OpenCvSharp/Modules/core/Struct/Vec/Vec6b.cs:127 — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6b.cs:127-136 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:157-166 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:158-167 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6i.cs:128-137 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6s.cs:128-137 | src/OpenCvSharp/Modules/core/Struct/Vec/Vec6w.cs:127-136 — 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 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Modules/core/Struct/Vec/Vec6b.cs:127` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `Item0` to `byte` in one and `int` 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 after the matched lines, `src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.cs:174` calls `ToVec6i`, `ToVec6d` and `src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:172` 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) src/OpenCvSharp/Cv2/Cv2_core.cs:2114 — src/OpenCvSharp/Cv2/Cv2_core.cs:2114-2121 | src/OpenCvSharp/Modules/core/SVD.cs:152-158 | src/OpenCvSharp/Modules/ximgproc/SparseMatchInterpolator.cs:33-40 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OpenCvSharp/Cv2/Cv2_core.cs:2114` 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 3) · ×1
  • Duplicated block (6–7 lines × 3) src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:18 — src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:18-24 | src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:36-41 | src/OpenCvSharp/Cv2/Cv2_ptcloud.cs:51-56 — 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/OpenCvSharp/Cv2/Cv2_ptcloud.cs:18` 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) src/OpenCvSharp/Modules/rgbd/DynaFu.cs:48 — src/OpenCvSharp/Modules/rgbd/DynaFu.cs:48-53 | src/OpenCvSharp/Modules/rgbd/KinFu.cs:47-52 | src/OpenCvSharp/Modules/rgbd/KinFuParams.cs:59-64 — 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/OpenCvSharp/Modules/rgbd/DynaFu.cs:48` 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) src/OpenCvSharp/Cv2/Cv2_imgproc.cs:902 — src/OpenCvSharp/Cv2/Cv2_imgproc.cs:902-907 | src/OpenCvSharp/Cv2/Cv2_imgproc.cs:930-936 — both copies are in the same file, so extract the 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/OpenCvSharp/Cv2/Cv2_imgproc.cs:902` 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: OpenCvSharp src/OpenCvSharp/OpenCvSharp.csproj:1 — OpenCvSharp: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — test suite did not build — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
GD1 · Unfinished & placeholder code · Unfinished stub · ×1
  • Unfinished stub — throws NotImplementedException src/OpenCvSharp/Modules/core/FileNodeIterator.cs:78 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×1
  • Unfinished stub — throws NotImplementedException src/OpenCvSharp/Modules/core/FileNodeIterator.cs:78 — `Reset` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Dead `#if false` region · ×1
  • Dead `#if false` region src/OpenCvSharp/Modules/features/DenseFeatureDetector.cs:1 — Code inside a `#if false` block is permanently excluded from the build — disabled code that should be removed or restored.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging or diagnostics emission found. This codebase ships libraries rather than a process it operates, so structured logging itself is the HOST application's to configure — but a library that emits nothing at all gives its consumers no way to see what it did.
Minor — 152 finding(s)
D24 · Comment Value · redundant comment · ×74
  • redundant comment src/OpenCvSharp.GdipExtensions/Properties/AssemblyInfo.cs:4 — "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/OpenCvSharp.GdipExtensions/Properties/AssemblyInfo.cs:12 — "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/OpenCvSharp.GdipExtensions/Properties/AssemblyInfo.cs:17 — "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/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_img_hash.cs:54 — "BlockMeanHash" repeats the code it sits on: 3 of its 3 words (block, mean, hash) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_img_hash.cs:71 — "ColorMomentHash" repeats the code it sits on: 3 of its 3 words (color, moment, hash) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_img_hash.cs:82 — "MarrHildrethHash" repeats the code it sits on: 3 of its 3 words (marr, hildreth, hash) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_img_hash.cs:113 — "RadialVarianceHash" repeats the code it sits on: 3 of its 3 words (radial, variance, hash) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_xfeatures2d.cs:13 — "BriefDescriptorExtractor" repeats the code it sits on: 3 of its 3 words (brief, descriptor, extractor) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_xfeatures2d_BOW.cs:29 — "BOWKMeansTrainer" repeats the code it sits on: 3 of its 3 words (bowk, means, trainer) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_xfeatures2d_BOW.cs:46 — "BOWImgDescriptorExtractor" repeats the code it sits on: 4 of its 4 words (bow, img, descriptor, extractor) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_xfeatures2d_HarrisLaplace.cs:13 — "HarrisLaplaceFeatureDetector" repeats the code it sits on: 4 of its 4 words (harris, laplace, feature, detector) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_xfeatures2d_PCTSignatures.cs:156 — "PCTSignaturesSQFD" repeats the code it sits on: 3 of its 3 words (pct, signatures, sqfd) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/dnn/NativeMethods_dnn.cs:45 — 5 comments in this file only repeat the code they sit on (lines 45, 112, 124, 143, 155), for example "readTensorFromONNX". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/dnn/NativeMethods_dnn_TextModel.cs:14 — "------------------------------------------------------------------------ TextRecognitionModel ------------------------------------------------------------------ …" repeats the code it sits on: 3 of its 3 words (text, recognition, model) are already in `[LibraryImport(DllExtern, EntryPoint = "dnn_TextRecognitionModel_new_String"), UnmanagedCallConv(CallConvs = [typeof(Cal …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/dnn/NativeMethods_dnn_TextModel.cs:67 — "------------------------------------------------------------------------ TextDetectionModel_EAST --------------------------------------------------------------- …" repeats the code it sits on: 4 of its 4 words (text, detection, model, east) are already in `[LibraryImport(DllExtern, EntryPoint = "dnn_TextDetectionModel_EAST_new_String"), UnmanagedCallConv(CallConvs = [typeof( …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/dnn/NativeMethods_dnn_TextModel.cs:95 — "------------------------------------------------------------------------ TextDetectionModel_DB ----------------------------------------------------------------- …" repeats the code it sits on: 4 of its 4 words (text, detection, model, db) are already in `[LibraryImport(DllExtern, EntryPoint = "dnn_TextDetectionModel_DB_new_String"), UnmanagedCallConv(CallConvs = [typeof(Ca …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/features/NativeMethods_features_DescriptorMatcher.cs:97 — "FlannBasedMatcher" repeats the code it sits on: 3 of its 3 words (flann, based, matcher) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/imgproc/NativeMethods_imgproc_GeneralizedHough.cs:68 — "GeneralizedHoughBallard" repeats the code it sits on: 3 of its 3 words (generalized, hough, ballard) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/imgproc/NativeMethods_imgproc_GeneralizedHough.cs:95 — "GeneralizedHoughGuil" repeats the code it sits on: 3 of its 3 words (generalized, hough, guil) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/ptcloud/NativeMethods_ptcloud_io.cs:15 — "loadPointCloud" repeats the code it sits on: 3 of its 3 words (load, point, cloud) are already in `[LibraryImport(DllExtern, EntryPoint = "ptcloud_loadPointCloud"), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)]) …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/ptcloud/NativeMethods_ptcloud_io.cs:30 — "savePointCloud" repeats the code it sits on: 3 of its 3 words (save, point, cloud) are already in `[LibraryImport(DllExtern, EntryPoint = "ptcloud_savePointCloud"), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)]) …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/shape/NativeMethods_shape_HistogramCostExtractor.cs:38 — "NormHistogramCostExtractor" repeats the code it sits on: 4 of its 4 words (norm, histogram, cost, extractor) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/shape/NativeMethods_shape_HistogramCostExtractor.cs:50 — "EMDHistogramCostExtractor" repeats the code it sits on: 4 of its 4 words (emd, histogram, cost, extractor) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/shape/NativeMethods_shape_HistogramCostExtractor.cs:62 — "ChiHistogramCostExtractor" repeats the code it sits on: 4 of its 4 words (chi, histogram, cost, extractor) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/OpenCvSharp/Internal/PInvoke/NativeMethods/shape/NativeMethods_shape_HistogramCostExtractor.cs:68 — "EMDL1HistogramCostExtractor" repeats the code it sits on: 4 of its 4 words (emdl, histogram, cost, extractor) are already in `[LibraryImport(DllExtern), UnmanagedCallConv(CallConvs = [typeof(CallConvCdecl)])]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 49 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Commented-out code · ×29
  • Commented-out code src/OpenCvSharp.Analyzers/RowColNotDisposedAnalyzer.cs:74 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:333 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp.GdipExtensions/BitmapConverter.cs:376 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:187 — 13 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:218 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.cs:325 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Cv2/Cv2_core.cs:2691 — 6 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Cv2/Cv2_core.cs:2701 — 5 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Internal/PInvoke/NativeMethods/core/NativeMethods_core.cs:67 — 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:14 — 9 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:24 — 10 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:60 — 7 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Internal/PInvoke/NativeMethods/text/NativeMethods_text.cs:68 — 8 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/Mat.cs:982 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/Mat.cs:1009 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/Mat.cs:1036 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/Mat.cs:1061 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/Mat.cs:1086 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/UMat.cs:413 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/UMat.cs:440 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/UMat.cs:467 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/UMat.cs:492 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Mat/UMat.cs:517 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Struct/MatType.cs:246 — 43 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code src/OpenCvSharp/Modules/core/Struct/RotatedRect.cs:92 — 3 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • + 4 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×16
  • Duplicated predicate src/OpenCvSharp/Modules/core/Struct/Rect.cs:361 — `(X < rect.X + rect.Width) && (X + Width > rect.X) && (Y < rect.Y + rect.Height) && (Y + Height > rect.Y)` appears character-identically in 3 files — src/OpenCvSharp/Modules/core/Struct/Rect.cs, src/OpenCvSharp/Modules/core/Struct/Rect2d.cs, src/OpenCvSharp/Modules/core/Struct/Rect2f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec2d.cs:118 — `Item0.Equals(other.Item0) && Item1.Equals(other.Item1)` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec2d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec2f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec3d.cs:133 — `Item0.Equals(other.Item0) && Item1.Equals(other.Item1) && Item2.Equals(other.Item2)` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec3f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:148 — `Item0.Equals(other.Item0) && Item1.Equals(other.Item1) && Item2.Equals(other.Item2) && Item3.Equals(other.Item3)` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec4f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs:176 — `Item0.Equals(other.Item0) && Item1.Equals(other.Item1) && Item2.Equals(other.Item2) && Item3.Equals(other.Item3) && Item4.Equals(other.Item4…` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec6d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec6f.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/OpenCvSharp/Modules/core/Struct/Rect.cs:293 — `X <= rect.X && (rect.X + rect.Width) <= (X + Width) && Y <= rect.Y && (rect.Y + rect.Height) <= (Y + Height)` appears character-identically in 3 files — src/OpenCvSharp/Modules/core/Struct/Rect.cs, src/OpenCvSharp/Modules/core/Struct/Rect2d.cs, src/OpenCvSharp/Modules/core/Struct/Rect2f.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/OpenCvSharp/Modules/core/Struct/Rect.cs:277 — `X <= x && Y <= y && X + Width > x && Y + Height > y` appears character-identically in 3 files — src/OpenCvSharp/Modules/core/Struct/Rect.cs, src/OpenCvSharp/Modules/core/Struct/Rect2d.cs, src/OpenCvSharp/Modules/core/Struct/Rect2f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec2d.cs:143 — `a.Item0 != b.Item0 || a.Item1 != b.Item1` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec2d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec2f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec3d.cs:154 — `a.Item0 != b.Item0 || a.Item1 != b.Item1 || a.Item2 != b.Item2` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec3f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:172 — `a.Item0 != b.Item0 || a.Item1 != b.Item1 || a.Item2 != b.Item2 || a.Item3 != b.Item3` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec4f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec2d.cs:136 — `a.Item0 == b.Item0 && a.Item1 == b.Item1` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec2d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec2f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec3d.cs:147 — `a.Item0 == b.Item0 && a.Item1 == b.Item1 && a.Item2 == b.Item2` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec3d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec3f.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/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs:165 — `a.Item0 == b.Item0 && a.Item1 == b.Item1 && a.Item2 == b.Item2 && a.Item3 == b.Item3` appears character-identically in 2 files — src/OpenCvSharp/Modules/core/Struct/Vec/Vec4d.cs, src/OpenCvSharp/Modules/core/Struct/Vec/Vec4f.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/OpenCvSharp/Modules/dpm/DpmDetector.cs:85 — `image.Type() != MatType.CV_8UC1 && image.Type() != MatType.CV_8UC3` appears character-identically in 2 files — src/OpenCvSharp/Modules/dpm/DpmDetector.cs, src/OpenCvSharp/Modules/rapid/CvRapid.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/OpenCvSharp/Modules/optflow/GPCForest5.cs:71 — `imagesFromArray.Length != imagesToArray.Length || imagesFromArray.Length != gtArray.Length` appears character-identically in 2 files — src/OpenCvSharp/Modules/optflow/GPCForest5.cs, src/OpenCvSharp/Modules/optflow/GPCTrainingSamples.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/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:125 — `src.PixelWidth != dst.Width || src.PixelHeight != dst.Height` appears character-identically in 2 files — src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs, src/OpenCvSharp.WpfExtensions/WriteableBitmapConverter.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.
P10 · Library API & versioning · Implementation type on the public API · ×5
  • Implementation type on the public API src/OpenCvSharp/Internal/PInvoke/ExceptionHandler.cs:11 — 14 public types in `OpenCvSharp.Internal` are marked as implementation by their own namespace, folder or name: `ExceptionHandler` (src/OpenCvSharp/Internal/PInvoke/ExceptionHandler.cs:11, `Internal`), `ExceptionStatus` (src/OpenCvSharp/Internal/PInvoke/ExceptionStatus.cs:6, `Internal`), `CvGPCTrainingParams` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_optflow_gpc.cs:17, `Internal`), `CvGPCMatchingParams` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/NativeMethods_optflow_gpc.cs:31, `Internal`), `NativeMethods` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/bioinspired/NativeMethods_bioinspired.cs:10, `Internal`), `FacemarkLBFParamsData` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/face/FacemarkParamsData.cs:12, `Internal`), `FacemarkAAMParamsData` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/face/FacemarkParamsData.cs:33, `Internal`), `CvColoredKinFuParams` (src/OpenCvSharp/Internal/PInvoke/NativeMethods/rgbd/NativeMethods_rgbd_colored_kinfu.cs:18, `Internal`), and 6 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API src/OpenCvSharp/Internal/Util/ArrayAddress2.cs:10 — 4 public types in `OpenCvSharp.Internal.Util` are marked as implementation by their own namespace, folder or name: `ArrayAddress2` (src/OpenCvSharp/Internal/Util/ArrayAddress2.cs:10, `Internal`), `MatTypeMap` (src/OpenCvSharp/Internal/Util/MatTypeMap.cs:10, `Internal`), `ReadOnlyArray2D` (src/OpenCvSharp/Internal/Util/ReadOnlyArray2D.cs:7, `Internal`), `SaturateCast` (src/OpenCvSharp/Internal/Util/SaturateCast.cs:4, `Internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API src/OpenCvSharp/Internal/Vectors/IStdVector.cs:6 — 15 public types in `OpenCvSharp.Internal.Vectors` are marked as implementation by their own namespace, folder or name: `IStdVector` (src/OpenCvSharp/Internal/Vectors/IStdVector.cs:6, `Internal`), `StdVector` (src/OpenCvSharp/Internal/Vectors/StdVector.cs:18, `Internal`), `VectorOfDTreesNode` (src/OpenCvSharp/Internal/Vectors/VectorOfDTreesNode.cs:7, `Internal`), `VectorOfImageFeatures` (src/OpenCvSharp/Internal/Vectors/VectorOfImageFeatures.cs:7, `Internal`), `VectorOfKeyLine` (src/OpenCvSharp/Internal/Vectors/VectorOfKeyLine.cs:7, `Internal`), `VectorOfMat` (src/OpenCvSharp/Internal/Vectors/VectorOfMat.cs:5, `Internal`), `VectorOfString` (src/OpenCvSharp/Internal/Vectors/VectorOfString.cs:7, `Internal`), `VectorOfVectorByte` (src/OpenCvSharp/Internal/Vectors/VectorOfVectorByte.cs:7, `Internal`), and 7 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API src/OpenCvSharp/Modules/dnn_superres/DnnSuperResImpl.cs:21 — 1 public type in `OpenCvSharp.DnnSuperres` is marked as implementation by its own namespace, folder or name: `DnnSuperResImpl` (src/OpenCvSharp/Modules/dnn_superres/DnnSuperResImpl.cs:21, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
  • Implementation type on the public API src/OpenCvSharp/Modules/stitching/AffineBasedEstimator.cs:9 — 42 public types in `OpenCvSharp.Detail` are marked as implementation by their own namespace, folder or name: `AffineBasedEstimator` (src/OpenCvSharp/Modules/stitching/AffineBasedEstimator.cs:9, `Detail`), `AffineBestOf2NearestMatcher` (src/OpenCvSharp/Modules/stitching/AffineBestOf2NearestMatcher.cs:13, `Detail`), `BestOf2NearestMatcher` (src/OpenCvSharp/Modules/stitching/BestOf2NearestMatcher.cs:9, `Detail`), `BestOf2NearestRangeMatcher` (src/OpenCvSharp/Modules/stitching/BestOf2NearestRangeMatcher.cs:13, `Detail`), `BlenderType` (src/OpenCvSharp/Modules/stitching/Blender.cs:8, `Detail`), `Blender` (src/OpenCvSharp/Modules/stitching/Blender.cs:20, `Detail`), `BlocksChannelsCompensator` (src/OpenCvSharp/Modules/stitching/BlocksChannelsCompensator.cs:9, `Detail`), `BlocksCompensator` (src/OpenCvSharp/Modules/stitching/BlocksCompensator.cs:10, `Detail`), and 34 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
X7 · Silent fallback defaults · Silent fallback default in catch · ×5
  • Silent fallback default in catch src/OpenCvSharp/Fundamentals/OpenCvSafeHandle.cs:79 — `RunPostReleaseAction` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/OpenCvSharp/Modules/face/Facemark/FacemarkFaceDetector.cs:78 — `Invoke` swallows every exception into `return -1;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/OpenCvSharp/Modules/face/Facemark/FacemarkFaceDetector.cs:92 — `Trampoline` swallows every exception into `return -1;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/OpenCvSharp/Modules/geometry/SACSegmentation.cs:333 — `ModelConstraintTrampoline` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/OpenCvSharp/Modules/videoio/StreamReaderBridge.cs:55 — `ReadTrampoline` swallows every exception into `return -1;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
D31 · IaC & Container Security · Low IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
P10 · Library API & versioning · Public type used only inside its own library · ×4
  • Public type used only inside its own library src/OpenCvSharp/Modules/superres/BroxOpticalFlow.cs:10 — `OpenCvSharp.BroxOpticalFlow` (src/OpenCvSharp/Modules/superres/BroxOpticalFlow.cs:10) is public, and the library's own code uses it, but no other project in this repository uses it (read: `OpenCvSharp.AvaloniaExtensions`, `OpenCvSharp.GdipExtensions`, `OpenCvSharp.Tests`, `OpenCvSharp.Tests.Avalonia`, `OpenCvSharp.Tests.NativeAot`, `OpenCvSharp.Tests.Windows`, `OpenCvSharp.WpfExtensions`) 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/OpenCvSharp/Modules/superres/DualTVL1OpticalFlow.cs:9 — `OpenCvSharp.DualTVL1OpticalFlow` (src/OpenCvSharp/Modules/superres/DualTVL1OpticalFlow.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `OpenCvSharp.AvaloniaExtensions`, `OpenCvSharp.GdipExtensions`, `OpenCvSharp.Tests`, `OpenCvSharp.Tests.Avalonia`, `OpenCvSharp.Tests.NativeAot`, `OpenCvSharp.Tests.Windows`, `OpenCvSharp.WpfExtensions`) 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/OpenCvSharp/Modules/superres/PyrLKOpticalFlow.cs:9 — `OpenCvSharp.PyrLKOpticalFlow` (src/OpenCvSharp/Modules/superres/PyrLKOpticalFlow.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `OpenCvSharp.AvaloniaExtensions`, `OpenCvSharp.GdipExtensions`, `OpenCvSharp.Tests`, `OpenCvSharp.Tests.Avalonia`, `OpenCvSharp.Tests.NativeAot`, `OpenCvSharp.Tests.Windows`, `OpenCvSharp.WpfExtensions`) 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/OpenCvSharp/Modules/superres/SuperResFarnebackOpticalFlow.cs:11 — `OpenCvSharp.SuperResFarnebackOpticalFlow` (src/OpenCvSharp/Modules/superres/SuperResFarnebackOpticalFlow.cs:11) is public, and the library's own code uses it, but no other project in this repository uses it (read: `OpenCvSharp.AvaloniaExtensions`, `OpenCvSharp.GdipExtensions`, `OpenCvSharp.Tests`, `OpenCvSharp.Tests.Avalonia`, `OpenCvSharp.Tests.NativeAot`, `OpenCvSharp.Tests.Windows`, `OpenCvSharp.WpfExtensions`) 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.
IC1 · Incompleteness & stubs · Disabled test · ×2
  • Disabled test test/OpenCvSharp.Tests/core/MatTest.cs:1256 — A test is skipped ("heavy") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
  • Disabled test test/OpenCvSharp.Tests/highgui/TrackbarTest.cs:10 — A test is skipped ("GUI Test") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found src/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj:36 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `src/OpenCvSharp.WpfExtensions/OpenCvSharp.WpfExtensions.csproj` makes this repository a deployable product (line 36).
D21 · Naming Consistency · `CreateDefaultLINE` spells `LINE` where 53 names in the project spell it `Line` · ×1
  • `CreateDefaultLINE` spells `LINE` where 53 names in the project spell it `Line` src/OpenCvSharp/Modules/rgbd/LinemodDetector.cs:43 — 53 of 54 names in project OpenCvSharp spell the token `Line` (53 of 54; unit: names in project OpenCvSharp containing `Line`). Peers: Cv2.GetCpuFeaturesLine (src/OpenCvSharp/Cv2/Cv2_core.cs:2668); Cv2.FitLine (src/OpenCvSharp/Cv2/Cv2_geometry.cs:3343); Cv2.FitLine (src/OpenCvSharp/Cv2/Cv2_geometry.cs:3367); Cv2.FitLine (src/OpenCvSharp/Cv2/Cv2_geometry.cs:3392); Cv2.FitLine (src/OpenCvSharp/Cv2/Cv2_geometry.cs:3417). Rename to `CreateDefaultLine`. [rule N6]
D21 · Naming Consistency · `WeChatQRCode` spells `QR` where 19 names in the project spell it `Qr` · ×1
  • `WeChatQRCode` spells `QR` where 19 names in the project spell it `Qr` src/OpenCvSharp/Modules/wechat_qrcode/WeChatQRCode.cs:12 — 19 of 20 names in project OpenCvSharp spell the token `Qr` (19 of 20; unit: names in project OpenCvSharp containing `Qr`). Peers: NativeMethods.objdetect_QRCodeDetector_decode(straightQrCode) (src/OpenCvSharp/Internal/PInvoke/NativeMethods/objdetect/NativeMethods_objdetect_QRCodeDetector.cs:28); NativeMethods.objdetect_QRCodeDetector_detectAndDecode(straightQrCode) (src/OpenCvSharp/Internal/PInvoke/NativeMethods/objdetect/NativeMethods_objdetect_QRCodeDetector.cs:32); NativeMethods.objdetect_QRCodeDetector_decodeMulti(straightQrCode) (src/OpenCvSharp/Internal/PInvoke/NativeMethods/objdetect/NativeMethods_objdetect_QRCodeDetector.cs:40); NativeMethods.objdetect_QRCodeDetectorAruco_decode(straightQrCode) (src/OpenCvSharp/Internal/PInvoke/NativeMethods/objdetect/NativeMethods_objdetect_QRCodeDetectorAruco.cs:44); NativeMethods.objdetect_QRCodeDetectorAruco_detectAndDecode(straightQrCode) (src/OpenCvSharp/Internal/PInvoke/NativeMethods/objdetect/NativeMethods_objdetect_QRCodeDetectorAruco.cs:48). Rename to `WeChatQrCode`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion src/OpenCvSharp/OpenCvSharp.csproj:1 — `OpenCvSharp` overshoots its size bounds (109380 LoC, 842 public types across 36 namespaces). 1 of 27 project(s) overshoot their size bounds, lowering Project Cohesion to 9.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D27 · Navigability · Scattered collaborators · ×1
  • Scattered collaborators — 93 % of calls cross a namespace and only 59 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • 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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 5/9 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.
Minor — 74 finding(s)
D10 · Test Quality · Skipped (documented) · ×71
  • Skipped (documented): BlobFromImageWithParamsMatchesBlobFromImage test/OpenCvSharp.Tests/dnn/BlobAndNmsTest.cs:14 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): BlobFromImageWithParamsLetterbox test/OpenCvSharp.Tests/dnn/BlobAndNmsTest.cs:52 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ImagesFromBlobRoundTrip test/OpenCvSharp.Tests/dnn/BlobAndNmsTest.cs:72 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): NMSBoxesBatched test/OpenCvSharp.Tests/dnn/BlobAndNmsTest.cs:99 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): SoftNMSBoxes test/OpenCvSharp.Tests/dnn/BlobAndNmsTest.cs:118 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ReadNetFromTFLiteInvalidBufferThrows test/OpenCvSharp.Tests/dnn/BlobAndNmsTest.cs:136 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): TracingModeRoundTrip test/OpenCvSharp.Tests/dnn/DnnTokenizerTracingTest.cs:16 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ProfilingModeRoundTrip test/OpenCvSharp.Tests/dnn/DnnTokenizerTracingTest.cs:28 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): FinalizeNetIsWired test/OpenCvSharp.Tests/dnn/DnnTokenizerTracingTest.cs:40 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): RegisterOutputIsWired test/OpenCvSharp.Tests/dnn/DnnTokenizerTracingTest.cs:51 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ReadNetFromONNXUnicodePath test/OpenCvSharp.Tests/dnn/DnnUnicodePathTest.cs:17 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ReadNetUnicodePath test/OpenCvSharp.Tests/dnn/DnnUnicodePathTest.cs:39 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): DetectionModelUnicodePath test/OpenCvSharp.Tests/dnn/DnnUnicodePathTest.cs:62 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ReadNetFromOnnxWithOpenCvEngine test/OpenCvSharp.Tests/dnn/EngineSelectionTest.cs:49 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ClassificationModelRecognizesMnistDigit test/OpenCvSharp.Tests/dnn/ModelTest.cs:25 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ModelPredictReturnsProbabilities test/OpenCvSharp.Tests/dnn/ModelTest.cs:42 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ModelFromNetSharesBaseSetters test/OpenCvSharp.Tests/dnn/ModelTest.cs:69 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): ClassificationModelSoftmaxToggle test/OpenCvSharp.Tests/dnn/ModelTest.cs:85 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): DetectionModelLifecycle test/OpenCvSharp.Tests/dnn/ModelTest.cs:97 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): SegmentationModelLifecycle test/OpenCvSharp.Tests/dnn/ModelTest.cs:117 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): KeypointsModelLifecycle test/OpenCvSharp.Tests/dnn/ModelTest.cs:139 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): GetModelFormatReturnsOnnx test/OpenCvSharp.Tests/dnn/NetIntrospectionTest.cs:19 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): GetLayerTypesAndCount test/OpenCvSharp.Tests/dnn/NetIntrospectionTest.cs:27 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): GetParamAndSetParamAreWired test/OpenCvSharp.Tests/dnn/NetIntrospectionTest.cs:45 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • Skipped (documented): SetInputShapeRejectsUnknownInput test/OpenCvSharp.Tests/dnn/NetIntrospectionTest.cs:58 — Skipped with a documented reason — a deferral, not lazy debt: Only runs on Windows or Linux
  • + 46 more in this group — see findings.md.
D24 · Comment Value · doc comments repeat the names · ×3
  • doc comments repeat the names src/OpenCvSharp/Cv2/Cv2_core.cs:44 — 99 of 7014 documented parameters and 139 of 7442 summaries in `OpenCvSharp` only repeat the member or parameter name (e.g. "The border type" for `borderType`). 1882 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names test/OpenCvSharp.Tests/dnn/ModelDownloader.cs:8 — 0 of 3 documented parameters and 0 of 28 summaries in `OpenCvSharp.Tests` only repeat the member or parameter name (e.g. "" for `uri`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/OpenCvSharp.WpfExtensions/BitmapSourceConverter.cs:30 — 0 of 27 documented parameters and 0 of 18 summaries in `OpenCvSharp.WpfExtensions` only repeat the member or parameter name (e.g. "" for `horizontalResolution`). 10 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-7932e0f750b9486fa81aee977411261c/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-7932e0f750b9486fa81aee977411261c/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-7932e0f750b9486fa81aee977411261c/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=204" --report-format json --report-path /tmp/watchdog-gitleaks-7932e0f750b9486fa81aee977411261c/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7932e0f750b9486fa81aee977411261c/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .154artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-01dbbcaac69143238bf34b66d33bca6f0artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .15artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—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. semgrep could not parse 4 file(s) — `src/OpenCvSharp/Modules/line_descriptors/LSDParam.cs`, `src/OpenCvSharp/Modules/video/DenseOpticalFlow.cs`, `src/OpenCvSharp/Modules/video/SparseOpticalFlow.cs`, `src/OpenCvSharp/Modules/videoio/StreamReaderStreamAdapter.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-01dbbcaac69143238bf34b66d33bca6f0artifacts/raw/osv-scanner.json

Run 01a1e69f-c756-7cdc-84ac-b3a1e2833e44 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md