Public report of mono/SkiaSharp, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 04:20 UTC · Survey ID cd_b3feb0b393ee4f459381627068da8987
mono/SkiaSharp
Measured 17 November 2026, 04:18 UTC, at code version 3ec9acf
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 80,479 lines of product code in 259 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Accessibility, 36.0
Findings by how serious they are
142 critical632 serious223 minor
5 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 04:18 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 ▸
74of 74 dimensions measured by tools.
981of 997 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
74dimensions across 7 lenses, read from 80,479 lines of product code in 259 projects.
mono/SkiaSharp falls short of our standard for production, in part because it has controls that only work with a mouse. It scores 47.6 out of 100 and is rated Weak, and 118 of its 142 critical findings are security problems.
Accessibility, at 36.0, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 8.0 points. Fixing focus, motion and contrast comes next, worth about 7.0 points. Raising Accessibility to 70 would lift the score to about 57.3.
Sixty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen passwords or keys in the code's history and one in the code are open to anyone who can read the repository, and twelve pipeline steps run downloads nobody checks. Pinning each tool to an exact version, replacing each exposed password or key and checking each download against a checksum would close these risks. Correcting the flagged pipeline settings would fix the nine weaknesses in the build pipeline's configuration, and the 12 unsafe settings in infrastructure or container files need changing to safe values. The seven sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 80,479 lines, about €130,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 36.0 to 70, the lowest score rated Strong, the score would rise from 47.6 to about 57.3.
Code composition: what the lines of code are
Business logic 11%Supporting code 26%Tests 32%Generated by tools 30%
Rebuild cost: about €130,000 · Estimate
Cost to rebuild
€41,000 to €210,000, for 688 to 2,197 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 80,479 lines of product code
Comment lines
The estimate prices 59,190 lines. Comment lines count towards the size of 80,479 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 8.0 points · Medium effort · Keyboard semantics
2
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 3.2 points · Medium effort · Page structure
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 Accessibility, at 36.0 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 8.0 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 105,751 lines over the last 90 days, which is about 428,879 lines a year. At that pace, the extra work comes to an estimated 21.4 to 143 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
50 modules, with 29 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 10 more are left out to keep it readable.
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.
SkiaSharp uses SkiaSharp.Internals, so a change to SkiaSharp.Internals can break SkiaSharp, while a change to SkiaSharp can't break SkiaSharp.Internals.
Position
Below the diagonal: SkiaSharp uses a module listed above it, which is the healthy direction.
scripts.infra.docs.release_notes uses scripts.infra.docs.release_notes.update_github_summaries, so a change to scripts.infra.docs.release_notes.update_github_summaries can break scripts.infra.docs.release_notes, while a change to scripts.infra.docs.release_notes can't break scripts.infra.docs.release_notes.update_github_summaries.
Position
Below the diagonal: scripts.infra.docs.release_notes uses a module listed above it, which is the healthy direction.
SkiaSharp.HarfBuzz uses HarfBuzzSharp, so a change to HarfBuzzSharp can break SkiaSharp.HarfBuzz, while a change to SkiaSharp.HarfBuzz can't break HarfBuzzSharp.
Position
Below the diagonal: SkiaSharp.HarfBuzz uses a module listed above it, which is the healthy direction.
SkiaSharp.Resources uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Resources, while a change to SkiaSharp.Resources can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Resources uses a module listed above it, which is the healthy direction.
SkiaSharp.SceneGraph uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.SceneGraph, while a change to SkiaSharp.SceneGraph can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.SceneGraph uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Android uses (global), so a change to (global) can break SkiaSharp.Views.Android, while a change to SkiaSharp.Views.Android can't break (global).
Position
Below the diagonal: SkiaSharp.Views.Android uses a module listed above it, which is the healthy direction.
39 pairs of types, where a type in SkiaSharp.Views.Android uses a type in SkiaSharp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SkiaSharp.Views.Android uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Android, while a change to SkiaSharp.Views.Android can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Android uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Blazor.Internal uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Blazor.Internal, while a change to SkiaSharp.Views.Blazor.Internal can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Blazor.Internal uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in SkiaSharp.Views.Desktop uses a type in SkiaSharp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SkiaSharp.Views.Desktop uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Desktop, while a change to SkiaSharp.Views.Desktop can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Desktop uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Maui uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Maui, while a change to SkiaSharp.Views.Maui can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Maui uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Windows uses (global), so a change to (global) can break SkiaSharp.Views.Windows, while a change to SkiaSharp.Views.Windows can't break (global).
Position
Below the diagonal: SkiaSharp.Views.Windows uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Windows uses SkiaSharp.Views.GlesInterop, so a change to SkiaSharp.Views.GlesInterop can break SkiaSharp.Views.Windows, while a change to SkiaSharp.Views.Windows can't break SkiaSharp.Views.GlesInterop.
Position
Below the diagonal: SkiaSharp.Views.Windows uses a module listed above it, which is the healthy direction.
31 pairs of types, where a type in SkiaSharp.Views.Windows uses a type in SkiaSharp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SkiaSharp.Views.Windows uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Windows, while a change to SkiaSharp.Views.Windows can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Windows uses a module listed above it, which is the healthy direction.
SkiaSharp.Skottie uses SkiaSharp.Resources, so a change to SkiaSharp.Resources can break SkiaSharp.Skottie, while a change to SkiaSharp.Skottie can't break SkiaSharp.Resources.
Position
Below the diagonal: SkiaSharp.Skottie uses a module listed above it, which is the healthy direction.
SkiaSharp.Skottie uses SkiaSharp.SceneGraph, so a change to SkiaSharp.SceneGraph can break SkiaSharp.Skottie, while a change to SkiaSharp.Skottie can't break SkiaSharp.SceneGraph.
Position
Below the diagonal: SkiaSharp.Skottie uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Blazor uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Blazor, while a change to SkiaSharp.Views.Blazor can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Blazor uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Blazor uses SkiaSharp.Views.Blazor.Internal, so a change to SkiaSharp.Views.Blazor.Internal can break SkiaSharp.Views.Blazor, while a change to SkiaSharp.Views.Blazor can't break SkiaSharp.Views.Blazor.Internal.
Position
Below the diagonal: SkiaSharp.Views.Blazor uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Gtk uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Gtk, while a change to SkiaSharp.Views.Gtk can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Gtk uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Gtk uses SkiaSharp.Views.Desktop, so a change to SkiaSharp.Views.Desktop can break SkiaSharp.Views.Gtk, while a change to SkiaSharp.Views.Gtk can't break SkiaSharp.Views.Desktop.
Position
Below the diagonal: SkiaSharp.Views.Gtk uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Maui.Controls uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Maui.Controls, while a change to SkiaSharp.Views.Maui.Controls can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Maui.Controls uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Maui.Controls uses SkiaSharp.Views.Maui, so a change to SkiaSharp.Views.Maui can break SkiaSharp.Views.Maui.Controls, while a change to SkiaSharp.Views.Maui.Controls can't break SkiaSharp.Views.Maui.
Position
Below the diagonal: SkiaSharp.Views.Maui.Controls uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Maui.Handlers uses SkiaSharp.Views.Android, so a change to SkiaSharp.Views.Android can break SkiaSharp.Views.Maui.Handlers, while a change to SkiaSharp.Views.Maui.Handlers can't break SkiaSharp.Views.Android.
Position
Below the diagonal: SkiaSharp.Views.Maui.Handlers uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Maui.Handlers uses SkiaSharp.Views.Maui, so a change to SkiaSharp.Views.Maui can break SkiaSharp.Views.Maui.Handlers, while a change to SkiaSharp.Views.Maui.Handlers can't break SkiaSharp.Views.Maui.
Position
Below the diagonal: SkiaSharp.Views.Maui.Handlers uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Maui.Platform uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.Maui.Platform, while a change to SkiaSharp.Views.Maui.Platform can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.Maui.Platform uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.Maui.Platform uses SkiaSharp.Views.Maui, so a change to SkiaSharp.Views.Maui can break SkiaSharp.Views.Maui.Platform, while a change to SkiaSharp.Views.Maui.Platform can't break SkiaSharp.Views.Maui.
Position
Below the diagonal: SkiaSharp.Views.Maui.Platform uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.WPF uses SkiaSharp, so a change to SkiaSharp can break SkiaSharp.Views.WPF, while a change to SkiaSharp.Views.WPF can't break SkiaSharp.
Position
Below the diagonal: SkiaSharp.Views.WPF uses a module listed above it, which is the healthy direction.
SkiaSharp.Views.WPF uses SkiaSharp.Views.Desktop, so a change to SkiaSharp.Views.Desktop can break SkiaSharp.Views.WPF, while a change to SkiaSharp.Views.WPF can't break SkiaSharp.Views.Desktop.
Position
Below the diagonal: SkiaSharp.Views.WPF uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
100
High / Critical
A02:2025 — Security Misconfiguration
33
High / Critical
A07:2025 — Authentication Failures
16
High / Critical
A03:2025 — Software Supply Chain Failures
7
Medium
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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 — 142
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 — 632
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 — 223
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
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 74 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 — 74 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 981 of 997 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: the test projects could not be restored because pkgs.dev.azure.com could not be reached (NU1301: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/skiasharp/nuget/v3/index.json. [tests/SkiaSharp.Tests.Integration.slnx] The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'." [tests/SkiaSharp.Tests.Integra…), so no test was built or run on this run. This is OURS — the scan's network path to the registry — and a TRANSIENT condition, NOT a statement about this repository's tests; coverage is excluded from the score rather than counted as a near-zero, and a re-run with the registry reachable measures it.
D10 Test 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. The 1,457 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 15 test source file(s) (.py) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
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. The NuGet registry this repository's packages resolve from could not be reached on this run, so no outdated, vulnerable or deprecated package could be read. The tool said: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json.. This is OUR side and an ENVIRONMENT fault — the collector exists and ran — so the remedy is the scan's network path to pkgs.dev.azure.com, and a re-run with it reachable measures this repository.
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 (110 contributor(s) across 4003 commit(s) sampled, automation and bot accounts excluded). One of them holds 87% of the history; the other 109 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 'binding/SkiaSharp/SkiaSharp.csproj' with message: Project does not contain 'Compile' target.
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 build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
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. A scan loads every live solution in the repository into one workspace. Every score, lens, and finding here reflects the projects of `samples/Gallery/SkiaSharpSample.Mac.slnx`, `samples/Gallery/SkiaSharpSample.slnx`, `source/SkiaSharpSource.slnx`, `benchmarks/SkiaSharp.Benchmarks.slnx`, `samples/Basic/UnoPlatform/SkiaSharpSample.slnx`, `samples/Basic/Maui/SkiaSharpSample.Windows.slnx`, `samples/Basic/iOS/SkiaSharpSample.Mac.slnx`, `samples/Basic/macOS/SkiaSharpSample.Mac.slnx`, `samples/Basic/Android/SkiaSharpSample.Mac.slnx`, `samples/Basic/MacCatalyst/SkiaSharpSample.Mac.slnx`, `samples/Basic/tvOS/SkiaSharpSample.Mac.slnx`, `samples/Basic/Tizen/SkiaSharpSample.slnx`, `samples/Basic/WindowsForms/SkiaSharpSample.Windows.slnx`, `samples/Basic/WinUI/SkiaSharpSample.Windows.slnx`, `samples/Basic/BlazorWebAssembly/SkiaSharpSample.slnx`, `samples/Basic/WPF/SkiaSharpSample.Windows.slnx`, `samples/Basic/Gtk4/SkiaSharpSample.slnx`, `samples/Basic/Gtk3/SkiaSharpSample.slnx`, `samples/Basic/Web/SkiaSharpSample.slnx`, `samples/Basic/BrowserWebAssembly/SkiaSharpSample.slnx`, `samples/Basic/Console/SkiaSharpSample.slnx`, `utils/Utils.slnx`, `samples/Basic/DockerConsole/SkiaSharpSample.slnx`, `samples/Basic/DockerWebApi/SkiaSharpSample.slnx`, `native/winui/SkiaSharp.Views.WinUI.Native/SkiaSharp.Views.WinUI.Native.slnx`; 1 further solution(s) found in this tree (`native/windows/libHarfBuzzSharp/libHarfBuzzSharp.slnx`) could not be added to it — their project list could not be read, or none of their projects opened — so their code is not represented in the headline. (This is a count of the solutions discovery found and could not show to be covered by the analyzed ones — not a claim about how many solution files the repository contains.) If one of them is an archived or vendored tree, declaring it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — excludes it from discovery the same way generated code is. You can widen what we reach: if one of these solutions is live code, check that it opens on its own (`dotnet build <solution>`); if it is archived or vendored, declare it so.
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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
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 (70,420 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"]`.
D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D30 Dependency Vulnerabilities — 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. Pkgs.dev.azure.com could not be reached (NU1301: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.). 1 of 3 declared ecosystem(s) (npm) 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.
D30 Dependency Vulnerabilities — 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. Osv-scanner exited 1 with no findings — dependency CVEs were not measured. 1 of 3 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
D31 IaC & Container Security — 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. Tests/Dockerfile.linux.dockerignore carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 21 of 22 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
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. `binding/Binding.Shared/DelegateProxies.shared.cs`, `binding/Binding.Shared/HashCode.cs`, `binding/Binding.Shared/LibraryLoader.cs`, `binding/Binding.Shared/PlatformConfiguration.cs`, `source/SkiaSharp.Views/SkiaSharp.Views.Shared/SKPaintGLSurfaceEventArgs.cs`, … (+15 more) 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.
D43 Malicious Dependencies — 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. Osv-scanner exited 1 with no findings — dependency CVEs were not measured. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
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 build step could not reach the network from our sandbox (a registry or download request was refused). This is a limit of our sandbox, not of your repository. (rule: network). The renderer reported: docker build failed (exit 1) — 9 | >>> dotnet publish SkiaSharpSample/ -c Release -r $RID -o /app/out 10 | -------------------- ERROR: failed to solve: process "/bin/sh -c if [ \"$TARGETARCH\" = \"arm64\" ]; then RID=linux-arm64; else RID=linux-x64; fi && dotnet publish SkiaSharpSample/ -c Release -r $RID -o /app/out" did not complete successfully: exit code: 1; likely cause (our sandbox): a build step could not reach the network from our sandbox (a registry or download request was refused). This is a limit of our sandbox, not of your repository; 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 (samples/Basic/DockerWebApi/linux.Dockerfile). docker build failed (exit 1) — 9 | >>> dotnet publish SkiaSharpSample/ -c Release -r $RID -o /app/out 10 | -------------------- ERROR: failed to solve: process "/bin/sh -c if [ \"$TARGETARCH\" = \"arm64\" ]; then RID=linux-arm64; else RID=linux-x64; fi && dotnet publish SkiaSharpSample/ -c Release -r $RID -o /app/out" did not complete successfully: exit code: 1; likely cause (our sandbox): a build step could not reach the network from our sandbox (a registry or download request was refused). This is a limit of our sandbox, not of your repository; runtime evidence skipped.
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.
SC1 Supply-chain 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. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for binding/SkiaSharp/SkiaSharp.csproj, binding/HarfBuzzSharp/HarfBuzzSharp.csproj, binding/SkiaSharp.Skottie/SkiaSharp.Skottie.csproj, binding/SkiaSharp.SceneGraph/SkiaSharp.SceneGraph.csproj, binding/SkiaSharp.Resources/SkiaSharp.Resources.csproj and 62 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Repo exclusion declarations: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
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.
32 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was run_review.main at 68. A further 11 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 SkiaExtensions.GetBytesPerPixel at 31 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: binding/SkiaSharp/Definitions.cs (SkiaExtensions.GetBytesPerPixel at 31), binding/SkiaSharp/EnumMappings.cs (SkiaExtensions.ToNative at 31), binding/SkiaSharp/GRDefinitions.cs (SkiaExtensions.ToGlSizedFormat at 31), binding/SkiaSharp/SKRuntimeEffect.cs (SKRuntimeEffectUniforms.ValidateTypes at 27), utils/SkiaSharpGenerator/Cookies/CookieDetector.cs (CookieDetector.GetTypeSignature at 23). 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.
+ 27 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 32 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with run_review.main (cyclomatic 68), render-security-audit-md.render_md (cyclomatic 61), validate-skia-review.main (cyclomatic 57). — 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 32 together lifts Cyclomatic Complexity from 6.4 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.
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.
+ 43 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with ci-status.render_console (cognitive 175), render-security-audit-md.render_md (cognitive 153). — 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 2 together lifts Cognitive Complexity from 5.4 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.2 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 22 TooManyMethods finding(s) in God Classes — start with SKCanvas.cs, SKPaint.cs, SKFont.cs. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 7 FileTooLong finding(s) in God Classes — start with GLTextureView.cs, SKCanvas.cs, SKPaint.cs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 2 MethodTooLong finding(s) in God Classes — start with GLTextureView.cs, Generator.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.
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.
125 duplicated block group(s) detected. 7.0 % of the production lines (4,932 of 70,420) are in a reported copy. A further 180 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 111 of the 305 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (7 corresponding lines) · ×10binding/HarfBuzzSharp/DelegateProxies.font.cs:143
Edited copy of a member (8 corresponding lines) · ×10binding/HarfBuzzSharp/DelegateProxies.font.cs:152
Edited copy of a member (9 corresponding lines) · ×10binding/SkiaSharp/SKRuntimeEffect.cs:145
+ 101 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SKXamlCanvas.cs (2), SKDrawingArea.cs, SKGLSurfaceView.cs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with DrawingViewController.cs (3), Generator.cs, Tag.cs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 10 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with DelegateProxies.font.cs, DelegateProxies.unicode.cs, SKGLViewHandler.Android.cs. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.4 / 10Stronggated by 14 serious findings✓ 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.
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Unstable project HarfBuzzSharp finding(s) in Coupling — start with HarfBuzzSharp.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project SkiaSharp.Resources finding(s) in Coupling — start with SkiaSharp.Resources.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project SkiaSharp.SceneGraph finding(s) in Coupling — start with SkiaSharp.SceneGraph.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.
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.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with SKGLView.cs, FilterRailView.xaml.cs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.8 / 10Stronggated by 18 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.
3 skipped (3 with a documented reason), 18 zero-assertion, 1 whose failure is swallowed by a catch-all, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1457 tests. Measured on the C# suite only — at least 15 test source file(s) (.py) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: ReleaseBitmapPixelsWithNullDelegate · ×17tests/Tests/SkiaSharp/SKBitmapTest.cs:320
Test cannot fail: ExceptionsThrownInTheConstructorFailGracefullytests/Tests/SkiaSharp/SKObjectTest.cs:183
Resolve the 17 No assertions finding(s) in Test Quality — start with SKCanvasTest.cs (5), SKShaderTest.cs (4), SKBitmapTest.cs. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 1 Test cannot fail finding(s) in Test Quality — start with SKObjectTest.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
1 of 319 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 60 direct `PackageReference`(s), and 196 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.
Banned license: Fizzler
What to do
Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with release-notes-data.py, Generator.cs, update_versions.py. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
166 deducted debt markers + unmeasured dead symbols across 70420 LoC in the .NET projects (0.7/KLoC) → score 8.7. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 NoWarnInCsproj finding(s) in Explicit Debt — start with SkiaSharpSample.csproj (2), SkiaSharp.NuGet.props (2), SkiaSharp.Benchmarks.Tracking.Source.csproj. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 5 EmptyCatchBlock finding(s) in Explicit Debt — start with BaseTool.cs (2), LibraryLoader.cs, GpuPage.cs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with SKRegion.cs, REDACTED, Privacy.cshtml.cs. — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
259 projects, 2179 source files, 70420 hand-written lines of code (70420 production / 0 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), plus 39529 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 240 inter-project edges (build status unknown — did not finish). Measured across 25 solutions loaded as one workspace: `samples/Gallery/SkiaSharpSample.Mac.slnx`, `samples/Gallery/SkiaSharpSample.slnx`, `source/SkiaSharpSource.slnx`, `benchmarks/SkiaSharp.Benchmarks.slnx`, `samples/Basic/UnoPlatform/SkiaSharpSample.slnx`, `samples/Basic/Maui/SkiaSharpSample.Windows.slnx`, `samples/Basic/iOS/SkiaSharpSample.Mac.slnx`, `samples/Basic/macOS/SkiaSharpSample.Mac.slnx`, `samples/Basic/Android/SkiaSharpSample.Mac.slnx`, `samples/Basic/MacCatalyst/SkiaSharpSample.Mac.slnx`, `samples/Basic/tvOS/SkiaSharpSample.Mac.slnx`, `samples/Basic/Tizen/SkiaSharpSample.slnx`, `samples/Basic/WindowsForms/SkiaSharpSample.Windows.slnx`, `samples/Basic/WinUI/SkiaSharpSample.Windows.slnx`, `samples/Basic/BlazorWebAssembly/SkiaSharpSample.slnx`, `samples/Basic/WPF/SkiaSharpSample.Windows.slnx`, `samples/Basic/Gtk4/SkiaSharpSample.slnx`, `samples/Basic/Gtk3/SkiaSharpSample.slnx`, `samples/Basic/Web/SkiaSharpSample.slnx`, `samples/Basic/BrowserWebAssembly/SkiaSharpSample.slnx`, `samples/Basic/Console/SkiaSharpSample.slnx`, `utils/Utils.slnx`, `samples/Basic/DockerConsole/SkiaSharpSample.slnx`, `samples/Basic/DockerWebApi/SkiaSharpSample.slnx`, `native/winui/SkiaSharp.Views.WinUI.Native/SkiaSharp.Views.WinUI.Native.slnx`.
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.
2 of 2 documentation facets pass in full. 89 document(s) read across 49 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
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.
No ADRs foundutils/SkiaSharpGenerator/SkiaSharpGenerator.csproj:4
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with SkiaSharpGenerator.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.
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.
1 naming inconsistencies among 19 declarations measured against a convention their peers follow.
`OpenGL` spells `GL` where 18 names in the project spell it `Gl`binding/SkiaSharp/EnumMappings.cs:15
What to do
Resolve the 1 `OpenGL` spells `GL` where 18 names in the project spell it `Gl` finding(s) in Naming Consistency — start with EnumMappings.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.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×12binding/HarfBuzzSharp/DelegateProxies.font.cs:8
What to do
Resolve the 35 redundant comment finding(s) in Comment Value — start with SKColorSpace.cs (3), SKTypeface.cs (3), Util.cs (3). — One of this dimension's main actionable groups (35 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
79 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
14 finding(s): 0 critical, 14 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 13 REDACTED finding(s) in Secrets (history) — start with REDACTED (7), REDACTED (6). — One of this dimension's main actionable groups (13 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
103 finding(s): 0 critical, 94 high, 9 medium, 0 low. 60 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 33 file(s) — `.agents/skills/native-dependency-update/scripts/setup.sh` (line 13), `.github/scripts/skia-sync-detect.sh` (line 159, line 160, line 161, …), `binding/Binding.Shared/DelegateProxies.shared.cs` (line 11), `binding/Binding.Shared/HashCode.cs` (line 13), `binding/Binding.Shared/LibraryLoader.cs` (line 16), … (+28 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 2 of those file(s) — `samples/Gallery/Maui/Controls/GalleryItems.cs`, `utils/SkiaSharpGenerator/Generate/DocumentationStore.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 12 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
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
No action in Static Analysis (SAST) — all 60 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (60 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 3 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. nuget,osv was not scanned (nuget: pkgs.dev.azure.com could not be reached (NU1301: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.); osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured), so this is not the whole dependency surface and the result is reported at reduced confidence.
Resolve the 21 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (21). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 12 High IaC finding(s) in IaC & Container Security — start with REDACTED (12). — One of this dimension's main actionable groups (12 issue-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
4 of 192 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is binding/HarfBuzzSharp/FontFunctions.cs. Counted over 192 of the 262 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with SKGLLayer.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured), so this is not the whole dependency surface and the result is reported at reduced confidence.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 90 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.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels6.1 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — .agents/skills/skill-creator/eval-viewer/viewer.html:604
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×5) — .agents/skills/ci-status/scripts/viewer.html:2, .agents/skills/issue-triage/scripts/viewer.html:2, .agents/skills/security-audit/scripts/viewer.html:2, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — .agents/skills/ci-status/scripts/viewer.html:75, .agents/skills/issue-triage/scripts/viewer.html:65
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — .agents/skills/ci-status/scripts/viewer.html:74, .agents/skills/ci-status/scripts/viewer.html:102, .agents/skills/ci-status/scripts/viewer.html:139
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.pill-stale` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/ci-status/scripts/viewer.html:30
`.pill-skipped` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/ci-status/scripts/viewer.html:31
`.cat-chain_blockage` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/ci-status/scripts/viewer.html:37
`.cat-unknown` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/ci-status/scripts/viewer.html:38
`.diff-chevron` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .agents/skills/review-skia-update/scripts/viewer.html:222
`.st-false-positive` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/security-audit/scripts/viewer.html:20
`.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/assets/eval_review.html:17
`.btn-export` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/assets/eval_review.html:19
`.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .agents/skills/skill-creator/eval-viewer/viewer.html:275
`.section-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/eval-viewer/viewer.html:83
`.output-file-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/eval-viewer/viewer.html:136
`.output-file-content .download-link` sets color: #d97757 on background-color: #faf9f5 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/eval-viewer/viewer.html:197
`.prev-feedback` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/eval-viewer/viewer.html:221
`.grade-pass` sets color: #788c5d on background-color: #eef2e8 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/eval-viewer/viewer.html:302
`.grade-fail` sets color: #c44 on background-color: #fceaea — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/eval-viewer/viewer.html:303
`.done-btn.ready` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .agents/skills/skill-creator/eval-viewer/viewer.html:467
`.cat-item.active` sets color: #6366f1 on background-color: #eef2ff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — samples/Gallery/Blazor/Components/FilterRail.razor.css:82
`.api-tag.active` sets color: white on background-color: #6366f1 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — samples/Gallery/Blazor/Components/TagPill.razor.css:22
`.api-tag.tag-method.active` sets color: white on background-color: #d97706 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — samples/Gallery/Blazor/Components/TagPill.razor.css:44
`[data-theme="dark"] .api-tag.tag-method.active` sets color: white on background-color: #d97706 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — samples/Gallery/Blazor/Components/TagPill.razor.css:81
`.rail-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — samples/Gallery/Blazor/Components/FilterRail.razor.css:24
`.mobile-filter-fab` moves (`transition: box-shadow 150ms ease, transform 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — samples/Gallery/Blazor/Pages/Home.razor.css:226
`.drawer-panel` moves (`animation: slideUp 200ms cubic-bezier(0.16, 1, 0.3, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — samples/Gallery/Blazor/Pages/Home.razor.css:269
`.sample-sidebar` moves (`transition: width 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — samples/Gallery/Blazor/Pages/SamplePage.razor.css:41
`.rail-chevron` moves (`transition: transform 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — samples/Gallery/Blazor/Components/FilterRail.razor.css:57
`.sample-card` moves (`transition: transform 160ms ease, box-shadow 160ms ease, border-color 160ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — samples/Gallery/Blazor/Components/SampleCard.razor.css:18
`.card-arrow` moves (`transition: opacity 150ms ease, transform 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — samples/Gallery/Blazor/Components/SampleCard.razor.css:138
`.color-swatch` moves (`transition: transform 0.2s, box-shadow 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/Drawing.razor.css:56
`.nav-link::after` moves (`transition: transform 0.15s cubic-bezier(0.2, 0.6, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — documentation/site/style.css:196
`.platform-pill` moves (`transition: transform 0.15s, box-shadow 0.15s, border-color 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — documentation/site/style.css:738
`.feature` moves (`transition: transform 0.15s, box-shadow 0.15s, border-color 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — documentation/site/style.css:842
`.wf-card` moves (`transition: transform 0.15s, box-shadow 0.15s, border-color 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — documentation/site/ai/ai.css:347
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`DpiWatcherInterop` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (callbackReference; e.g. `callbackReference` at line 89). — source/SkiaSharp.Views/SkiaSharp.Views.Blazor/Internal/DpiWatcherInterop.cs:12
`SampleManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (cachedCutoff; e.g. `cachedCutoff` at line 134). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — samples/Gallery/Shared/SampleManager.cs:20
`Fonts` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (defaultTypeface; e.g. `defaultTypeface` at line 43). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — samples/Gallery/Shared/SampleMedia.cs:33
`PlatformConfiguration` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (linuxFlavor; e.g. `linuxFlavor` at line 89). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — binding/Binding.Shared/PlatformConfiguration.cs:14
`Linux` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (UseSystemLibrary2; e.g. `UseSystemLibrary2` at line 220). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — binding/Binding.Shared/LibraryLoader.cs:204
`HandleDictionary` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (instances, stackTraces; e.g. `instances` at line 182). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — binding/SkiaSharp/HandleDictionary.cs:14
`SkiaSharpVersion` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (nativeMinimum, nativeVersion; e.g. `nativeMinimum` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — binding/SkiaSharp/SkiaSharpVersion.cs:10
`DpiWatcherInterop` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (instance; e.g. `instance` at line 42). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — source/SkiaSharp.Views/SkiaSharp.Views.Blazor/Internal/DpiWatcherInterop.cs:12
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
`SkiaSharp.Views.Maui.Core` is a Domain project but references `SkiaSharp.Views.WinUI`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/SkiaSharp.Views.Maui.Core.csproj:24
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation7.5 / 10Strong✓ 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.
`SkiaSharp.Vulkan.Tests` (production) references the test project `SkiaSharp.Tests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — tests/SkiaSharp.Vulkan.Tests/SkiaSharp.Vulkan.Tests.csproj:49
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
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. (×3) — source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Ref.cs:11, source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Ref.cs:11, source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKSwapChainPanel.cs:59
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
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.
`CreatePlatformView` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Ref.cs:11, source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Ref.cs:11
`DrawInBackground` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKSwapChainPanel.cs:59
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×3) — source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:140, source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:143, source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:230
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the 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.
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.
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.
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.
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.
documentation/dev/building.md names .NET 9, but the projects target .NET 0, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/dev/building.md:227
documentation/dev/building.md names .NET 11, but the projects target .NET 0, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — documentation/dev/building.md:333
What to do
Reconcile the README with reality: documentation/dev/building.md names .NET 9, but the projects target .NET 0, 10; documentation/dev/building.md names .NET 11, but the projects target .NET 0, 10.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning9.0 / 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.
`SkiaSharp.Views.Android.Resource` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/Resource.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net10.0-android36.0)`, `SkiaSharpSample`, `SkiaSharpSample`) 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. — source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/Resource.cs:5
`SkiaSharp.Views.Android.Resource` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/Resource.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net9.0-android35.0)`) 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. — source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/Resource.cs:5
`SkiaSharp.Views.Android.SKGLSurfaceViewRenderer` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net10.0-android36.0)`, `SkiaSharpSample`, `SkiaSharpSample`) 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. — source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:12
`SkiaSharp.Views.Android.SKGLSurfaceViewRenderer` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net9.0-android35.0)`) 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. — source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:12
`SkiaSharp.Views.Android.SKGLTextureViewRenderer` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net10.0-android36.0)`, `SkiaSharpSample`, `SkiaSharpSample`) 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. — source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:12
`SkiaSharp.Views.Android.SKGLTextureViewRenderer` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net9.0-android35.0)`) 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. — source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:12
What to do
Make `SkiaSharp.Views.Android.Resource` 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 `SkiaSharp.Views.Android.Resource` 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 `SkiaSharp.Views.Android.SKGLSurfaceViewRenderer` 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 `SkiaSharp.Views.Android.SKGLSurfaceViewRenderer` 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 `SkiaSharp.Views.Android.SKGLTextureViewRenderer` 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 `SkiaSharp.Views.Android.SKGLTextureViewRenderer` 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.
Do you agree with this assessment?
P2 · Observability6.3 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 8/18 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 18, 10 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
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.
`benchmarks/SkiaSharp.Benchmarks.Tracking.Source/SkiaSharp.Benchmarks.Tracking.Source.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — benchmarks/SkiaSharp.Benchmarks.Tracking.Source/SkiaSharp.Benchmarks.Tracking.Source.csproj:36
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. (×2) — samples/Basic/BlazorWebAssembly/SkiaSharpSample/Program.cs:11, samples/Gallery/Blazor/Program.cs:11
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. — utils/SkiaSharpGenerator/Cookies/CookieDetector.cs:194
What to do
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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.
`fetch_release_file` is async and calls subprocess.run — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — eng/common/cross/install-debs.py:113
5 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×4) — source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:294, utils/SkiaSharpGenerator/Cookies/CookieCommand.cs:64, utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:79, …
`Task.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:322
What to do
Python: await the async equivalent (asyncio.sleep, an async HTTP client such as httpx.AsyncClient or aiohttp, asyncio.create_subprocess_exec), or move the blocking call off the loop with `await asyncio.to_thread(...)`; never call asyncio.run inside a coroutine — await the coroutine.
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself — a page handed to a consumer runs in that consumer's origin.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 4 such include(s) across the repository's markup. — .agents/skills/issue-triage/scripts/viewer.html:112
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Do you agree with this assessment?
X1 · Async correctness4.3 / 10Weak✓ Tool-verified
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×5) — samples/Gallery/Maui/Controls/GalleryHeader.xaml.cs:77, samples/Gallery/Maui/Controls/GallerySampleCard.xaml.cs:9, samples/Gallery/Maui/GalleryPage.xaml.cs:119, …
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×5) — source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:294, source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:322, utils/SkiaSharpGenerator/Cookies/CookieCommand.cs:64, …
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
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.
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.
`SKGLView` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `context` itself (line 28), which makes that instance its own. But `context` is named in none of the methods the disposal search covered: `Dispose` (line 223) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`context?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:28
`SKGLView` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `glInterface` itself (line 29), which makes that instance its own. But `glInterface` is named in none of the methods the disposal search covered: `Dispose` (line 223) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`glInterface?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:29
`SKGLView` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `renderTarget` itself (line 30), which makes that instance its own. But `renderTarget` is named in none of the methods the disposal search covered: `Dispose` (line 223) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`renderTarget?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:30
`SKGLView` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `surface` itself (line 32), which makes that instance its own. But `surface` is named in none of the methods the disposal search covered: `Dispose` (line 223) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`surface?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:32
`renderTarget` is a `GRBackendRenderTarget` this type creates itself, and here (line 115) a new instance is written over it — but `GetRenderTarget` itself reads through `renderTarget` before replacing it, so it expects an instance to be there, and nothing earlier in `GetRenderTarget` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`renderTarget?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKSwapChainPanel.cs:115
`renderTarget` is a `GRBackendRenderTarget` this type creates itself, and here (line 156) a new instance is written over it — but `Render` itself reads through `renderTarget` before replacing it, so it expects an instance to be there, and nothing earlier in `Render` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`renderTarget?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — source/SkiaSharp.Views/SkiaSharp.Views.Gtk4/SKGLArea.cs:156
`bitmap` is a `Bitmap` this type creates itself, and here (line 151) a new instance is written over it — but `CreateBitmap` itself reads through `bitmap` before replacing it, so it expects an instance to be there, and nothing earlier in `CreateBitmap` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`bitmap?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKControl.cs:151
`builder` is a `SKPathBuilder`, which implements `IDisposable`, and it is created here (line 136). Every use of it in `CreateStar` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var builder = …;`), which releases it at the end of the scope on every path including a throw. — benchmarks/SkiaSharp.Benchmarks/Benchmarks/SurfaceCanvasBenchmark.cs:136
`process` is a `Process`, which implements `IDisposable`, and it is created here (line 84). Every use of it in `ParseSkiaHeaders` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var process = …;`), which releases it at the end of the scope on every path including a throw. — utils/SkiaSharpGenerator/BaseTool.cs:84
`process` is a `Process`, which implements `IDisposable`, and it is created here (line 121). Every use of it in `ParseSkiaHeaders` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var process = …;`), which releases it at the end of the scope on every path including a throw. — utils/SkiaSharpGenerator/BaseTool.cs:121
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 5/21 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×15) — samples/Gallery/Maui/Controls/GalleryHeader.xaml.cs:77, samples/Gallery/Maui/GalleryPage.xaml.cs:138, samples/Gallery/Maui/GalleryPage.xaml.cs:163, …
No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. — samples/Gallery/Shared/CanvasSampleBase.cs:36
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.5 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`e.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — samples/Basic/BrowserWebAssembly/SkiaSharpSample/wwwroot/main.js:25
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
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. (×4) — source/SkiaSharp.Views/SkiaSharp.Views.Blazor/Internal/SKHtmlCanvasInterop.cs:149, samples/Basic/Tizen/SkiaSharpSample/GpuPage.cs:114, utils/SkiaSharpGenerator/BaseTool.cs:103, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
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.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
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.
This method contradicts itself about `errorString`: line 34 writes `errorString?.ToString`, which says `errorString` can be null, but line 33 then dereferences it directly as `errorString.Handle` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `errorString` truly cannot be null here, the `?.` is misleading. Settle it one way — test `errorString` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — binding/SkiaSharp/SKRuntimeEffect.cs:33
This method contradicts itself about `errorString`: line 50 writes `errorString?.ToString`, which says `errorString` can be null, but line 49 then dereferences it directly as `errorString.Handle` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `errorString` truly cannot be null here, the `?.` is misleading. Settle it one way — test `errorString` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — binding/SkiaSharp/SKRuntimeEffect.cs:49
This method contradicts itself about `errorString`: line 66 writes `errorString?.ToString`, which says `errorString` can be null, but line 65 then dereferences it directly as `errorString.Handle` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `errorString` truly cannot be null here, the `?.` is misleading. Settle it one way — test `errorString` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — binding/SkiaSharp/SKRuntimeEffect.cs:65
This method contradicts itself about `objects`: line 84 writes `objects?.Length`, which says `objects` can be null, but line 86 then dereferences it directly with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `objects` truly cannot be null here, the `?.` is misleading. Settle it one way — test `objects` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — binding/SkiaSharp/Util.cs:86
25/68 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~0.4 `!` suppressions per 1k syntax nodes — 87 suppression(s) across the 225971 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 31 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 16 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 — 40 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
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) — 9 | >>> dotnet publish SkiaSharpSample/ -c Release -r $RID -o /app/out 10 | -------------------- ERROR: failed to solve: process "/bin/sh -c if [ \"$TARGETARCH\" = \"arm64\" ]; then RID=linux-arm64; else RID=linux-x64; fi && dotnet publish SkiaSharpSample/ -c Release -r $RID -o /app/out" did not complete successfully: exit code: 1; likely cause (our sandbox): a build step could not reach the network from our sandbox (a registry or download request was refused). This is a limit of our sandbox, not of your repository; 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 — pkgs.dev.azure.com could not be reached
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) — 20 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 — pkgs.dev.azure.com could not be reached
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
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
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.
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
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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X8 JS interop contract — 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.
NoWarnInCsproj benchmarks/SkiaSharp.Benchmarks.Tracking.Source/SkiaSharp.Benchmarks.Tracking.Source.csproj:25— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj tests/SkiaSharp.Tests.Samples.Analyzers/SkiaSharp.Tests.Samples.Analyzers.csproj:10— RS2008 — 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 source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SkiaSharp.Views.Uno.WinUI.csproj:9— CA1416 — 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 samples/Basic/WPF/SkiaSharpSample/SkiaSharpSample.csproj:7— WPF0001 — 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 samples/Basic/WindowsForms/SkiaSharpSample/SkiaSharpSample.csproj:7— WFO5001 — 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 source/SkiaSharp.NuGet.props:23— NU5125 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
NoWarnInCsproj source/SkiaSharp.NuGet.props:23— NU5048 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
EmptyCatchBlock binding/Binding.Shared/LibraryLoader.cs:81— 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 samples/Basic/Tizen/SkiaSharpSample/GpuPage.cs:114— 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 source/SkiaSharp.Views/SkiaSharp.Views.Blazor/Internal/SKHtmlCanvasInterop.cs:149— 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 utils/SkiaSharpGenerator/BaseTool.cs:103— 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 utils/SkiaSharpGenerator/BaseTool.cs:144— 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.
WriteOnlyPrivateField binding/SkiaSharp/SKRegion.cs:500— private SKRectI clip — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:15— private ILogger<ErrorModel> _logger — 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 samples/Basic/Web/SkiaSharpSample/Pages/Privacy.cshtml.cs:8— private ILogger<PrivacyModel> _logger — 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 utils/SkiaSharpGenerator/Verify/Verifier.cs:13— private CppCompilation sourceCompilation — 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.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×3
Click handler on a non-interactive <div> .agents/skills/ci-status/scripts/viewer.html:74— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> .agents/skills/ci-status/scripts/viewer.html:102— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> .agents/skills/ci-status/scripts/viewer.html:139— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label .agents/skills/skill-creator/eval-viewer/viewer.html:604— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
Dependency-rule violation: SkiaSharp.Views.Maui.Core (Domain) → SkiaSharp.Views.WinUI (Web) source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/SkiaSharp.Views.Maui.Core.csproj:24— `SkiaSharp.Views.Maui.Core` is a Domain project but references `SkiaSharp.Views.WinUI`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
AX8 · Test isolation· Production project references a test project · ×1
Production project references a test project: SkiaSharp.Vulkan.Tests → SkiaSharp.Tests tests/SkiaSharp.Vulkan.Tests/SkiaSharp.Vulkan.Tests.csproj:49— `SkiaSharp.Vulkan.Tests` (production) references the test project `SkiaSharp.Tests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Banned license: Fizzler — `Fizzler` 1.3.1 resolves to SPDX id LGPL-3.0-or-later, and this run's banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an `OR` is a choice and is charged only when every branch is banned, an `AND` binds every operand, and a `WITH` exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison — which is how variants like `-only` and `-or-later` are caught while `LGPL-2.0-only` is not read as `GPL-2.0`, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. ★ This arm reads the resolved package list and knows nothing about dependency SCOPE — it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. ★ DEPTH: this repository's MSBuild projects declare 60 direct `PackageReference`(s), and 196 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. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
FileScopedPragmaDisable source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1— #pragma warning disable CS0618 — 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.
TodoComment binding/HarfBuzzSharp/Blob.cs:143— // TODO: check to see if we can avoid the second copy (the ToArray) — 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 binding/SkiaSharp/SKBitmap.cs:9— // TODO: keep in mind SKBitmap may be going away (according to Google) — 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 binding/SkiaSharp/SKBitmap.cs:10— // TODO: `ComputeIsOpaque` may be useful — 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 binding/SkiaSharp/SKBitmap.cs:11— // TODO: `GenerationID` may be useful — 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 binding/SkiaSharp/SKBitmap.cs:12— // TODO: `GetAddr` and `GetPixel` are confusing — 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 binding/SkiaSharp/SKBitmap.cs:243— // TODO: optimize as this does more work that we really want — 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 binding/SkiaSharp/SKCanvas.cs:7— // TODO: carefully consider the `PeekPixels`, `ReadPixels` — 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 binding/SkiaSharp/SKCodec.cs:9— // TODO: `Create(...)` should have overloads that accept a SKPngChunkReader — 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 binding/SkiaSharp/SKCodec.cs:10— // TODO: missing the `QueryYuv8` and `GetYuv8Planes` members — 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 binding/SkiaSharp/SKFont.cs:1586— // TODO: deal with multiple contours? — 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 binding/SkiaSharp/SKTextBlob.cs:582— // TODO: deal with multiple contours? — 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 binding/SkiaSharp/SKFont.cs:1607— // 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 binding/SkiaSharp/SKFontManager.cs:377— // TODO: work around for https://bugs.chromium.org/p/skia/issues/detail?id=6196
TodoComment binding/SkiaSharp/SKImage.cs:10— // TODO: `MakeCrossContextFromEncoded` — 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 binding/SkiaSharp/SKImage.cs:11— // TODO: `MakeFromYUVTexturesCopy` and `MakeFromNV12TexturesCopy` — 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 binding/SkiaSharp/SKImage.cs:12— // TODO: `FromPicture` with bit depth and color space — 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 binding/SkiaSharp/SKImage.cs:13— // TODO: `GetTextureHandle` — 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 binding/SkiaSharp/SKImage.cs:14— // TODO: `MakeColorSpace` — 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 binding/SkiaSharp/SKMaskFilter.cs:8— // TODO: `getFormat` — 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 binding/SkiaSharp/SKMaskFilter.cs:9— // TODO: `computeFastBounds` — 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 binding/SkiaSharp/SKMatrix44.cs:386— // TODO: create a vector type — 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 binding/SkiaSharp/SKTextBlob.cs:588— // TODO: clip glyphs on both ends of paths — 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 source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/GTKExtensions.cs:117— // TODO: maybe keep the same color types where we can, instead of just going to the platform default — 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 source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/GTKExtensions.cs:170— // TODO: maybe keep the same color types where we can, instead of just going to the platform default — 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 source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/GTKExtensions.cs:187— // TODO: maybe keep the same color types where we can, instead of just going to the platform default — 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.
+ 18 more in this group — see findings.md.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×40
NuGet dependencies are not locked benchmarks/SkiaSharp.Benchmarks.Tracking.Source/SkiaSharp.Benchmarks.Tracking.Source.csproj:36— benchmarks/SkiaSharp.Benchmarks.Tracking.Source/SkiaSharp.Benchmarks.Tracking.Source.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 benchmarks/SkiaSharp.Benchmarks.Tracking/SkiaSharp.Benchmarks.Tracking.csproj:44— benchmarks/SkiaSharp.Benchmarks.Tracking/SkiaSharp.Benchmarks.Tracking.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 benchmarks/SkiaSharp.Benchmarks/SkiaSharp.Benchmarks.csproj:14— benchmarks/SkiaSharp.Benchmarks/SkiaSharp.Benchmarks.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 binding/Directory.Build.targets:4— binding/Directory.Build.targets 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 eng/common/internal/Tools.csproj:12— eng/common/internal/Tools.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 native/winui/SkiaSharp.Views.WinUI.Native/SkiaSharp.Views.WinUI.Native.Projection/SkiaSharp.Views.WinUI.Native.Projection.csproj:19— native/winui/SkiaSharp.Views.WinUI.Native/SkiaSharp.Views.WinUI.Native.Projection/SkiaSharp.Views.WinUI.Native.Projection.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 native/winui/SkiaSharp.Views.WinUI.Native/SkiaSharp.Views.WinUI.Native/packages.config:3— native/winui/SkiaSharp.Views.WinUI.Native/SkiaSharp.Views.WinUI.Native/packages.config 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 samples/Basic/Android/SkiaSharpSample/SkiaSharpSample.csproj:10— samples/Basic/Android/SkiaSharpSample/SkiaSharpSample.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 samples/Basic/BlazorWebAssembly/SkiaSharpSample/SkiaSharpSample.csproj:16— samples/Basic/BlazorWebAssembly/SkiaSharpSample/SkiaSharpSample.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 samples/Basic/DockerConsole/SkiaSharpSample/SkiaSharpSample.csproj:10— samples/Basic/DockerConsole/SkiaSharpSample/SkiaSharpSample.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 samples/Basic/DockerWebApi/SkiaSharpSample/SkiaSharpSample.csproj:9— samples/Basic/DockerWebApi/SkiaSharpSample/SkiaSharpSample.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 samples/Basic/Gtk3/SkiaSharpSample/SkiaSharpSample.csproj:9— samples/Basic/Gtk3/SkiaSharpSample/SkiaSharpSample.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 samples/Basic/Gtk4/SkiaSharpSample/SkiaSharpSample.csproj:9— samples/Basic/Gtk4/SkiaSharpSample/SkiaSharpSample.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 samples/Basic/Maui/SkiaSharpSample/SkiaSharpSample.csproj:41— samples/Basic/Maui/SkiaSharpSample/SkiaSharpSample.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 samples/Basic/WinUI/SkiaSharpSample/SkiaSharpSample.csproj:16— samples/Basic/WinUI/SkiaSharpSample/SkiaSharpSample.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 samples/Gallery/Blazor/SkiaSharpSample.Blazor.csproj:18— samples/Gallery/Blazor/SkiaSharpSample.Blazor.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 samples/Gallery/Maui/SkiaSharpSample.Maui.csproj:35— samples/Gallery/Maui/SkiaSharpSample.Maui.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 samples/Gallery/Shared/SkiaSharpSample.Shared.csproj:16— samples/Gallery/Shared/SkiaSharpSample.Shared.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 samples/Gallery/Uno/SkiaSharpSample.Uno.csproj:65— samples/Gallery/Uno/SkiaSharpSample.Uno.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 samples/SkiaFiddle/SkiaFiddle.csproj:54— samples/SkiaFiddle/SkiaFiddle.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 source/SkiaSharp.Direct3D/SkiaSharp.Direct3D.Vortice/SkiaSharp.Direct3D.Vortice.csproj:15— source/SkiaSharp.Direct3D/SkiaSharp.Direct3D.Vortice/SkiaSharp.Direct3D.Vortice.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 source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Controls/SkiaSharp.Views.Maui.Controls.csproj:17— source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Controls/SkiaSharp.Views.Maui.Controls.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 source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/SkiaSharp.Views.Maui.Core.csproj:19— source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/SkiaSharp.Views.Maui.Core.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 source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SkiaSharp.Views.Uno.WinUI.csproj:22— source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SkiaSharp.Views.Uno.WinUI.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 source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SkiaSharp.Views.Blazor.csproj:31— source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SkiaSharp.Views.Blazor.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.
DeadPreprocessorBranch binding/Binding.Shared/PlatformConfiguration.cs:92— #if __IOS__ || __TVOS__ || __MACOS__ || __MACCATALYST__ || __ANDROID__ — 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.
DeadPreprocessorBranch binding/HarfBuzzSharp/HarfBuzzApi.cs:9— #if __IOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.Resources/ResourcesApi.cs:9— #if __IOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.SceneGraph/SceneGraphApi.cs:9— #if __IOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.Skottie/SkottieApi.cs:9— #if __IOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/SkiaApi.cs:44— #if __IOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/HarfBuzzSharp/Platform/Android/Resource.cs:1— #if __ANDROID__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.Resources/Platform/Android/Resource.cs:1— #if __ANDROID__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.SceneGraph/Platform/Android/Resource.cs:1— #if __ANDROID__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.Skottie/Platform/Android/Resource.cs:1— #if __ANDROID__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/Platform/Android/Resource.cs:1— #if __ANDROID__ — 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.
DeadPreprocessorBranch binding/HarfBuzzSharp/Properties/HarfBuzzSharpAssemblyInfo.cs:29— #if __IOS__ || __TVOS__ || __MACOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.Resources/Properties/SkiaSharpResourcesAssemblyInfo.cs:29— #if __IOS__ || __TVOS__ || __MACOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.SceneGraph/Properties/SkiaSharpSceneGraphAssemblyInfo.cs:28— #if __IOS__ || __TVOS__ || __MACOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp.Skottie/Properties/SkiaSharpSkottieAssemblyInfo.cs:29— #if __IOS__ || __TVOS__ || __MACOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/Properties/SkiaSharpAssemblyInfo.cs:57— #if __IOS__ || __TVOS__ || __MACOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/GRBackendRenderTarget.cs:75— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/GRDefinitions.cs:138— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/GRDefinitions.cs:144— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/GRMtlBackendContext.cs:4— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/GRMtlBackendContext.cs:42— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/GRMtlBackendContext.cs:48— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/Gpu/Graphite/SKGraphiteMtlBackendContext.cs:4— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/Gpu/Graphite/SKGraphiteMtlBackendContext.cs:36— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
DeadPreprocessorBranch binding/SkiaSharp/Gpu/Graphite/SKGraphiteMtlBackendContext.cs:49— #if __IOS__ || __MACOS__ || __TVOS__ — 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.
TooManyMethods: SKCanvas binding/SkiaSharp/SKCanvas.cs— TooManyMethods — 694 significant lines (blank, comment-only and punctuation-only lines excluded), 145 methods. The bar is 30 methods; this is 115 over it, 4.83× 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: SKPaint binding/SkiaSharp/SKPaint.cs— TooManyMethods — 687 significant lines (blank, comment-only and punctuation-only lines excluded), 133 methods. The bar is 30 methods; this is 103 over it, 4.43× 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: SKFont binding/SkiaSharp/SKFont.cs— TooManyMethods — 617 significant lines (blank, comment-only and punctuation-only lines excluded), 113 methods. The bar is 30 methods; this is 83 over it, 3.77× 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: SKImageFilter binding/SkiaSharp/SKImageFilter.cs— TooManyMethods — 316 significant lines (blank, comment-only and punctuation-only lines excluded), 112 methods. The bar is 30 methods; this is 82 over it, 3.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: SKImage binding/SkiaSharp/SKImage.cs— TooManyMethods — 480 significant lines (blank, comment-only and punctuation-only lines excluded), 105 methods. The bar is 30 methods; this is 75 over it, 3.50× 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: SKBitmap binding/SkiaSharp/SKBitmap.cs— TooManyMethods — 459 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× 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: SKPath binding/SkiaSharp/SKPath.cs— TooManyMethods — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SKSurface binding/SkiaSharp/SKSurface.cs— TooManyMethods — 269 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. 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: SKShader binding/SkiaSharp/SKShader.cs— TooManyMethods — 293 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. 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: Buffer binding/HarfBuzzSharp/Buffer.cs— TooManyMethods — 306 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 30 methods; this is 22 over it, 1.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: SKPathBuilder binding/SkiaSharp/SKPathBuilder.cs— TooManyMethods — 186 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: Font binding/HarfBuzzSharp/Font.cs— TooManyMethods — 275 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: SKTypeface binding/SkiaSharp/SKTypeface.cs— TooManyMethods — 296 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: SKPixmap binding/SkiaSharp/SKPixmap.cs— TooManyMethods — 249 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: SKMatrix44 binding/SkiaSharp/SKMatrix44.cs— TooManyMethods — 289 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 30 methods; this is 14 over it, 1.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: DelegateProxies binding/Binding.Shared/DelegateProxies.shared.cs— TooManyMethods — 287 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods, declared across 4 files: Binding.Shared/DelegateProxies.shared.cs (17), HarfBuzzSharp/DelegateProxies.font.cs (12), HarfBuzzSharp/DelegateProxies.unicode.cs (6), HarfBuzzSharp/DelegateProxies.cs (3). The bar is 30 methods; this is 8 over it, 1.27× 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: DelegateProxies binding/SkiaSharp/DelegateProxies.cs— TooManyMethods — 163 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods, declared across 5 files: SkiaSharp/DelegateProxies.cs (13), SkiaSharp/DelegateProxies.stream.cs (13), SkiaSharp/DelegateProxies.drawable.cs (5), SkiaSharp/DelegateProxies.wstream.cs (4), +1 more file(s). The bar is 30 methods; this is 7 over it, 1.23× 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: SKMatrix binding/SkiaSharp/SKMatrix.cs— TooManyMethods — 263 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: SKRegion binding/SkiaSharp/SKRegion.cs— TooManyMethods — 169 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: SKData binding/SkiaSharp/SKData.cs— TooManyMethods — 168 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: SKTextBlob binding/SkiaSharp/SKTextBlob.cs— TooManyMethods — 154 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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: GRContext binding/SkiaSharp/GRContext.cs— TooManyMethods — 134 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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.
No assertions: ReleaseBitmapPixelsWithNullDelegate tests/Tests/SkiaSharp/SKBitmapTest.cs:320— 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: CanDrawPatch tests/Tests/SkiaSharp/SKCanvasTest.cs:192— 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: CanDrawText tests/Tests/SkiaSharp/SKCanvasTest.cs:225— 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: CanDrawEmptyText tests/Tests/SkiaSharp/SKCanvasTest.cs:238— 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: CanvasCanClipRoundRect tests/Tests/SkiaSharp/SKCanvasTest.cs:250— 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: CanvasCanDrawRoundRect tests/Tests/SkiaSharp/SKCanvasTest.cs:259— 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: CanInstantiateDrawable tests/Tests/SkiaSharp/SKDrawableTest.cs:7— 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: RotationIsCorrectLayoutWithOriginTopLeft tests/Tests/SkiaSharp/SKMatrix44Tests.cs:345— 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: Clone tests/Tests/SkiaSharp/SKPaintTest.cs:206— 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: PathWithPendingBuilderMutationsSurvivesFinalization tests/Tests/SkiaSharp/SKPathTest.cs:729— 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: CanBeginRecording tests/Tests/SkiaSharp/SKPictureRecorderTest.cs:15— 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: CanDrawWithCreateLinearGradientShader tests/Tests/SkiaSharp/SKShaderTest.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: CanDrawWithCreateLinearGradientShaderColorF tests/Tests/SkiaSharp/SKShaderTest.cs:28— 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: CanDrawWithCreateSweepGradientShader tests/Tests/SkiaSharp/SKShaderTest.cs:112— 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: CanDrawWithCreatePictureShader tests/Tests/SkiaSharp/SKShaderTest.cs:150— 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: ShouldAppendBuffer tests/Tests/HarfBuzzSharp/HBBufferTest.cs:232— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: TableCallbackReturningNullOrTruncatedBlobDoesNotCrash tests/Tests/HarfBuzzSharp/HBFaceTest.cs:675— 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.
X2 · Cancellation propagation· Async method without CancellationToken · ×15
Async method without CancellationToken: BackClicked samples/Gallery/Maui/Controls/GalleryHeader.xaml.cs:77— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OpenSampleAsync samples/Gallery/Maui/GalleryPage.xaml.cs:138— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReturnToGalleryAsync samples/Gallery/Maui/GalleryPage.xaml.cs:163— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GoBackAsync samples/Gallery/Maui/SampleDetailPage.xaml.cs:87— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExportAsync samples/Gallery/Maui/SampleDetailPage.xaml.cs:565— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitAsync samples/Gallery/Shared/SampleBase.cs:42— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnInit samples/Gallery/Shared/Samples/GifPlayerSample.cs:55— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnInit samples/Gallery/Shared/Samples/LottiePlayerSample.cs:56— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnInit samples/Gallery/Shared/Samples/ShaderCrossFadeSample.cs:116— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnInit samples/Gallery/Shared/Samples/ShaderPlaygroundSample.cs:174— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadConfigAsync utils/SkiaSharpGenerator/BaseTool.cs:277— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DetectAsync utils/SkiaSharpGenerator/Cookies/CookieDetector.cs:37— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DownloadLatestCodeAsync utils/SkiaSharpGenerator/Cookies/CookieDetector.cs:192— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GenerateAsync utils/SkiaSharpGenerator/Generate/Generator.cs:23— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: VerifyAsync utils/SkiaSharpGenerator/Verify/Verifier.cs:20— No CancellationToken parameter — this work can't be stopped early once started.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×13
Animation without a prefers-reduced-motion guard .agents/skills/review-skia-update/scripts/viewer.html:222— `.diff-chevron` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard .agents/skills/skill-creator/eval-viewer/viewer.html:275— `.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard samples/Gallery/Blazor/Pages/Home.razor.css:226— `.mobile-filter-fab` moves (`transition: box-shadow 150ms ease, transform 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard samples/Gallery/Blazor/Pages/Home.razor.css:269— `.drawer-panel` moves (`animation: slideUp 200ms cubic-bezier(0.16, 1, 0.3, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard samples/Gallery/Blazor/Pages/SamplePage.razor.css:41— `.sample-sidebar` moves (`transition: width 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard samples/Gallery/Blazor/Components/FilterRail.razor.css:57— `.rail-chevron` moves (`transition: transform 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard samples/Gallery/Blazor/Components/SampleCard.razor.css:18— `.sample-card` moves (`transition: transform 160ms ease, box-shadow 160ms ease, border-color 160ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard samples/Gallery/Blazor/Components/SampleCard.razor.css:138— `.card-arrow` moves (`transition: opacity 150ms ease, transform 150ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/Drawing.razor.css:56— `.color-swatch` moves (`transition: transform 0.2s, box-shadow 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard documentation/site/style.css:196— `.nav-link::after` moves (`transition: transform 0.15s cubic-bezier(0.2, 0.6, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard documentation/site/style.css:738— `.platform-pill` moves (`transition: transform 0.15s, box-shadow 0.15s, border-color 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard documentation/site/style.css:842— `.feature` moves (`transition: transform 0.15s, box-shadow 0.15s, border-color 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard documentation/site/ai/ai.css:347— `.wf-card` moves (`transition: transform 0.15s, box-shadow 0.15s, border-color 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Duplicated block (6 lines × 2) source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs:157— source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs:157-162 | source/SkiaSharp.Views/SkiaSharp.Views.Gtk4/SKDrawingArea.cs:173-178 — 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 `source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs:157` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:288— source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:288-293 | source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.cs:310-315 — 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 `source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:288` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceView.cs:36— source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceView.cs:36-41 | source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureView.cs:37-42 — 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 (6 lines × 2) source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:162— source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:162-167 | source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.cs:167-172 — 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. 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 (6 lines × 2) .agents/skills/ci-status/scripts/ci-status.py:662— .agents/skills/ci-status/scripts/ci-status.py:662-667 | .agents/skills/ci-status/scripts/ci-status.py:668-673 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) .agents/skills/review-skia-update/scripts/check_source.py:66— .agents/skills/review-skia-update/scripts/check_source.py:66-71 | .agents/skills/review-skia-update/scripts/check_source.py:74-79 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) .agents/skills/review-skia-update/scripts/regenerate_bindings.py:69— .agents/skills/review-skia-update/scripts/regenerate_bindings.py:69-74 | .agents/skills/update-skia/scripts/regenerate_bindings.py:71-76 — before extracting anything, compare `.agents/skills/review-skia-update/scripts/regenerate_bindings.py` and `.agents/skills/update-skia/scripts/regenerate_bindings.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) samples/Gallery/Shared/Samples/VectorArtSample.cs:111— samples/Gallery/Shared/Samples/VectorArtSample.cs:111-116 | samples/Gallery/Shared/Samples/VectorArtSample.cs:148-153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Gallery/Shared/Samples/VectorArtSample.cs:111` 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.
Duplicated block (6 lines × 2) samples/Gallery/Shared/Samples/VertexMeshSample.cs:151— samples/Gallery/Shared/Samples/VertexMeshSample.cs:151-156 | samples/Gallery/Shared/Samples/VertexMeshSample.cs:160-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (6 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:87— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:87-92 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:87-92 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 187 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (6 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/SceneDelegate.cs:12— samples/Basic/MacCatalyst/SkiaSharpSample/SceneDelegate.cs:12-17 | samples/Basic/iOS/SkiaSharpSample/SceneDelegate.cs:12-17 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/SceneDelegate.cs` and `samples/Basic/iOS/SkiaSharpSample/SceneDelegate.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (6 lines × 2) scripts/infra/caching/repo-deps.py:84— scripts/infra/caching/repo-deps.py:84-89 | scripts/infra/caching/repo-deps.py:128-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) utils/SkiaSharpGenerator/Generate/Generator.cs:186— utils/SkiaSharpGenerator/Generate/Generator.cs:186-192 | utils/SkiaSharpGenerator/Generate/Generator.cs:699-705 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) binding/HarfBuzzSharp/Tag.cs:91— binding/HarfBuzzSharp/Tag.cs:91-97 | binding/SkiaSharp/SKFourByteTag.cs:88-94 — 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 `binding/HarfBuzzSharp/Tag.cs:91` 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) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:144— source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:144-150 | source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:153-159 — before extracting anything, compare `source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs` and `source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (7 lines × 2) .agents/skills/review-skia-update/scripts/run_review.py:271— .agents/skills/review-skia-update/scripts/run_review.py:271-277 | .agents/skills/review-skia-update/scripts/run_review.py:408-414 — both copies are in the same file, so extract the 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 `.agents/skills/review-skia-update/scripts/run_review.py:271` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) .agents/skills/sample-scout/scripts/render-sample-scout.py:161— .agents/skills/sample-scout/scripts/render-sample-scout.py:161-167 | .agents/skills/skia-analyst/scripts/render-skia-analyst.py:166-172 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `.agents/skills/skia-analyst/scripts/render-skia-analyst.py:173` calls `sum`, `get` and `.agents/skills/sample-scout/scripts/render-sample-scout.py:168` 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 (7 lines × 2) samples/Gallery/Blazor/Pages/SamplePage.razor:203— samples/Gallery/Blazor/Pages/SamplePage.razor:203-209 | samples/Gallery/Blazor/Pages/SamplePage.razor:219-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Gallery/Blazor/Pages/SamplePage.razor:203` 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 `e` to `SKPaintSurfaceEventArgs` in one and `SKPaintGLSurfaceEventArgs` 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) samples/Basic/Gtk4/SkiaSharpSample/GpuPage.cs:163— samples/Basic/Gtk4/SkiaSharpSample/GpuPage.cs:163-169 | samples/Basic/Tizen/SkiaSharpSample/GpuPage.cs:161-167 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:129— samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:129-135 | samples/Basic/WindowsForms/SkiaSharpSample/GpuPage.cs:104-110 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:197— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:197-203 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:197-203 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (7 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:146— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:146-152 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:146-152 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (7 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:186— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:186-192 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:186-192 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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· Edited copy of a member (7 corresponding lines) · ×10
Edited copy of a member (7 corresponding lines) binding/HarfBuzzSharp/DelegateProxies.font.cs:143— binding/HarfBuzzSharp/DelegateProxies.font.cs:143-149 | binding/HarfBuzzSharp/DelegateProxies.font.cs:169-175 — 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) binding/HarfBuzzSharp/DelegateProxies.unicode.cs:82— binding/HarfBuzzSharp/DelegateProxies.unicode.cs:82-88 | binding/HarfBuzzSharp/DelegateProxies.unicode.cs:91-99 — 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) source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Android.cs:96— source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Android.cs:96-105 | source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Android.cs:66-72 — 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) source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:162— source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:162-168 | source/SkiaSharp.Views/SkiaSharp.Views.WPF/WPFExtensions.cs:133-139 — 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) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceView.cs:35— source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceView.cs:35-41 | source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureView.cs:36-42 — 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) scripts/infra/caching/repo-deps.py:71— scripts/infra/caching/repo-deps.py:71-79 | scripts/infra/caching/repo-deps.py:83-89 — 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) samples/Gallery/Shared/Samples/VertexMeshSample.cs:150— samples/Gallery/Shared/Samples/VertexMeshSample.cs:150-156 | samples/Gallery/Shared/Samples/VertexMeshSample.cs:159-165 — 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) scripts/infra/docs/release-notes-data.py:647— scripts/infra/docs/release-notes-data.py:647-653 | scripts/infra/docs/release-notes-data.py:763-769 — 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) samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:157— samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:157-165 | samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:168-174 — 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) samples/Basic/iOS/SkiaSharpSample/SceneDelegate.cs:11— samples/Basic/iOS/SkiaSharpSample/SceneDelegate.cs:11-17 | samples/Basic/MacCatalyst/SkiaSharpSample/SceneDelegate.cs:11-17 — 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×10
Edited copy of a member (8 corresponding lines) binding/HarfBuzzSharp/DelegateProxies.font.cs:152— binding/HarfBuzzSharp/DelegateProxies.font.cs:152-159 | binding/HarfBuzzSharp/DelegateProxies.font.cs:207-216 — 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) binding/HarfBuzzSharp/DelegateProxies.cs:23— binding/HarfBuzzSharp/DelegateProxies.cs:23-30 | binding/SkiaSharp/DelegateProxies.cs:154-161 — 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) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:143— source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:143-150 | source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:152-159 — 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) .agents/skills/ci-status/scripts/render-ci-status-md.py:16— .agents/skills/ci-status/scripts/render-ci-status-md.py:16-23 | .agents/skills/security-audit/scripts/render-security-audit-md.py:16-23 — 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) samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:196— samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:196-203 | samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:196-203 — 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) samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:97— samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:97-104 | samples/Basic/tvOS/SkiaSharpSample/GpuGLViewController.cs:80-90 — 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) samples/Gallery/Shared/Samples/ColorFontSample.cs:51— samples/Gallery/Shared/Samples/ColorFontSample.cs:51-58 | samples/Gallery/Shared/Samples/VariableFontSample.cs:51-59 — 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) samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:44— samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:44-51 | samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:51-59 — 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) samples/Gallery/Blazor/Pages/SamplePage.razor:295— samples/Gallery/Blazor/Pages/SamplePage.razor:295-307 | samples/Gallery/Maui/SampleDetailPage.xaml.cs:373-380 — 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) samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:185— samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:185-192 | samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:185-192 — 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.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×10
Edited copy of a member (9 corresponding lines) binding/SkiaSharp/SKRuntimeEffect.cs:145— binding/SkiaSharp/SKRuntimeEffect.cs:145-153 | binding/SkiaSharp/SKRuntimeEffect.cs:156-164 — 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) binding/SkiaSharp/SKPaint.cs:1303— binding/SkiaSharp/SKPaint.cs:1303-1312 | binding/SkiaSharp/SKWebpEncoder.cs:39-47 — 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) source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:217— source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:217-225 | source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:234-242 — 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) source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Android.cs:89— source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Android.cs:89-97 | source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Android.cs:131-139 — 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) source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKGLControl.cs:234— source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKGLControl.cs:234-245 | source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:229-237 — 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) scripts/infra/perf/sizes/render_md.py:159— scripts/infra/perf/sizes/render_md.py:159-167 | scripts/infra/perf/sizes/render_md.py:172-180 — 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) samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:95— samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:95-103 | samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:95-103 — 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) samples/Gallery/Shared/Samples/ImageDecoderSample.cs:309— samples/Gallery/Shared/Samples/ImageDecoderSample.cs:309-317 | samples/Gallery/Shared/Samples/OverdrawVisualizationSample.cs:158-166 — 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) samples/Gallery/Shared/Samples/TextLabSample.cs:66— samples/Gallery/Shared/Samples/TextLabSample.cs:66-78 | samples/Gallery/Shared/Samples/WorldTextSample.cs:67-75 — 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) samples/Basic/tvOS/SkiaSharpSample/GpuGLViewController.cs:123— samples/Basic/tvOS/SkiaSharpSample/GpuGLViewController.cs:123-133 | samples/Basic/tvOS/SkiaSharpSample/GpuMetalViewController.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.
Duplicated block (8 lines × 2) source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:218— source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:218-225 | source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:235-242 — 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 (8 lines × 2) binding/SkiaSharp/SKColor.cs:293— binding/SkiaSharp/SKColor.cs:293-300 | binding/SkiaSharp/SKColor.cs:303-310 — both copies are in the same file, so extract the 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 `binding/SkiaSharp/SKColor.cs:293` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `binding/SkiaSharp/SKColor.cs:310` calls `TryParseByte` and `binding/SkiaSharp/SKColor.cs:300` 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 (8 lines × 2) binding/SkiaSharp/SKBitmap.cs:1011— binding/SkiaSharp/SKBitmap.cs:1011-1018 | binding/SkiaSharp/SKSurface.cs:1048-1055 — 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 `binding/SkiaSharp/SKBitmap.cs:1011` 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.
Duplicated block (8 lines × 2) binding/SkiaSharp/SKBitmap.cs:1011— binding/SkiaSharp/SKBitmap.cs:1011-1018 | binding/SkiaSharp/SKSurface.cs:1048-1055 — 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 `binding/SkiaSharp/SKBitmap.cs:1011` 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.
Duplicated block (8 lines × 2) source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Android.cs:90— source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Android.cs:90-97 | source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Android.cs:132-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (8 lines × 2) .agents/skills/ci-status/scripts/ci-status.py:348— .agents/skills/ci-status/scripts/ci-status.py:348-355 | .agents/skills/ci-status/scripts/ci-status.py:532-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) .agents/skills/review-skia-update/scripts/regenerate_bindings.py:46— .agents/skills/review-skia-update/scripts/regenerate_bindings.py:46-53 | .agents/skills/update-skia/scripts/regenerate_bindings.py:48-55 — before extracting anything, compare `.agents/skills/review-skia-update/scripts/regenerate_bindings.py` and `.agents/skills/update-skia/scripts/regenerate_bindings.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (8 lines × 2) samples/Gallery/Shared/Samples/VectorArtSample.cs:96— samples/Gallery/Shared/Samples/VectorArtSample.cs:96-103 | samples/Gallery/Shared/Samples/VectorArtSample.cs:119-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Gallery/Shared/Samples/VectorArtSample.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) samples/Gallery/Shared/Samples/VectorArtSample.cs:122— samples/Gallery/Shared/Samples/VectorArtSample.cs:122-129 | samples/Gallery/Shared/Samples/VectorArtSample.cs:134-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:96— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:96-103 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:96-103 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
AX2 · Stateful singletons· Process-global static state · ×7
Process-global static state: SampleManager samples/Gallery/Shared/SampleManager.cs:20— `SampleManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (cachedCutoff; e.g. `cachedCutoff` at line 134). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Fonts samples/Gallery/Shared/SampleMedia.cs:33— `Fonts` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (defaultTypeface; e.g. `defaultTypeface` at line 43). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: PlatformConfiguration binding/Binding.Shared/PlatformConfiguration.cs:14— `PlatformConfiguration` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (linuxFlavor; e.g. `linuxFlavor` at line 89). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Linux binding/Binding.Shared/LibraryLoader.cs:204— `Linux` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (UseSystemLibrary2; e.g. `UseSystemLibrary2` at line 220). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: HandleDictionary binding/SkiaSharp/HandleDictionary.cs:14— `HandleDictionary` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (instances, stackTraces; e.g. `instances` at line 182). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: SkiaSharpVersion binding/SkiaSharp/SkiaSharpVersion.cs:10— `SkiaSharpVersion` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (nativeMinimum, nativeVersion; e.g. `nativeMinimum` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: DpiWatcherInterop source/SkiaSharp.Views/SkiaSharp.Views.Blazor/Internal/DpiWatcherInterop.cs:12— `DpiWatcherInterop` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (instance; e.g. `instance` at line 42). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
FileTooLong: Android/GLTextureView.cs source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs— FileTooLong — 787 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 287 over it, 1.57× 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: SkiaSharp/SKCanvas.cs binding/SkiaSharp/SKCanvas.cs— FileTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 225 over it, 1.45× 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: SkiaSharp/SKPaint.cs binding/SkiaSharp/SKPaint.cs— FileTooLong — 711 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 211 over it, 1.42× 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: SkiaSharp/SKFont.cs binding/SkiaSharp/SKFont.cs— FileTooLong — 634 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 134 over it, 1.27× 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: scripts/ci-status.py .agents/skills/ci-status/scripts/ci-status.py— FileTooLong — 563 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 63 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: scripts/update_versions.py .agents/skills/update-skia/scripts/update_versions.py— FileTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 34 over it, 1.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: SkiaSharp/SKPath.cs binding/SkiaSharp/SKPath.cs— FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 26 over it, 1.05× 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.
Sync-over-async blocking eng/common/cross/install-debs.py:113— `fetch_release_file` is async and calls subprocess.run — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
Sync-over-async blocking — 5 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:294— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:322— `Task.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking utils/SkiaSharpGenerator/Cookies/CookieCommand.cs:64— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:79— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking utils/SkiaSharpGenerator/Verify/VerifyCommand.cs:61— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Low contrast colour pair in CSS (4.4:1) .agents/skills/ci-status/scripts/viewer.html:30— `.pill-stale` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) .agents/skills/ci-status/scripts/viewer.html:31— `.pill-skipped` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) .agents/skills/ci-status/scripts/viewer.html:37— `.cat-chain_blockage` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) .agents/skills/ci-status/scripts/viewer.html:38— `.cat-unknown` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) .agents/skills/security-audit/scripts/viewer.html:20— `.st-false-positive` sets color: #6b7280 on background-color: #f3f4f6 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) samples/Gallery/Blazor/Components/TagPill.razor.css:22— `.api-tag.active` sets color: white on background-color: #6366f1 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×6
Edited copy of a member (6 corresponding lines) source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:111— source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:111-116 | source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:118-123 — 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) samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:143— samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:143-148 | samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs:140-145 — 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) samples/Gallery/Shared/Samples/FillPathSample.cs:138— samples/Gallery/Shared/Samples/FillPathSample.cs:138-144 | samples/Gallery/Shared/Samples/PathEffectsSamplerSample.cs:178-183 — 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) samples/Basic/WinUI/SkiaSharpSample/GpuPage.xaml.cs:153— samples/Basic/WinUI/SkiaSharpSample/GpuPage.xaml.cs:153-159 | samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:166-171 — 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) samples/Gallery/Shared/Samples/TextToPathSample.cs:170— samples/Gallery/Shared/Samples/TextToPathSample.cs:170-175 | samples/Gallery/Shared/Samples/VariableFontSample.cs:146-151 — 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) scripts/infra/perf/_common.py:118— scripts/infra/perf/_common.py:118-123 | scripts/infra/perf/sizes/track.py:180-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.
Duplicated block (5 lines × 2) binding/SkiaSharp/SKColor.cs:273— binding/SkiaSharp/SKColor.cs:273-277 | binding/SkiaSharp/SKColor.cs:287-291 — both copies are in the same file, so extract the 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 `binding/SkiaSharp/SKColor.cs:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) utils/SkiaSharpGenerator/BaseTool.cs:294— utils/SkiaSharpGenerator/BaseTool.cs:294-298 | utils/SkiaSharpGenerator/Generate/Generator.cs:576-580 — 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 `utils/SkiaSharpGenerator/BaseTool.cs:294` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) .agents/skills/review-skia-update/scripts/run_review.py:104— .agents/skills/review-skia-update/scripts/run_review.py:104-108 | .agents/skills/review-skia-update/scripts/run_review.py:114-118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) .agents/skills/review-skia-update/scripts/check_deps.py:29— .agents/skills/review-skia-update/scripts/check_deps.py:29-33 | .agents/skills/update-skia/scripts/update_versions.py:88-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `variables` to `dict` in one and `dict[str, object]` 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 (5 lines × 2) samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:144— samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:144-148 | samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs:141-145 — before extracting anything, compare `samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs` and `samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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. 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 (5 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:96— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:96-100 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:96-100 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 187 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
AC3 · Page structure· Page without a main landmark · ×5
Page without a main landmark .agents/skills/ci-status/scripts/viewer.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .agents/skills/issue-triage/scripts/viewer.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .agents/skills/security-audit/scripts/viewer.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .agents/skills/skill-creator/assets/eval_review.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .agents/skills/skill-creator/eval-viewer/viewer.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×5
Edited copy of a member (18 corresponding lines) binding/SkiaSharp/SKImage.cs:380— binding/SkiaSharp/SKImage.cs:380-397 | binding/SkiaSharp/SKSurface.cs:775-792 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:264— source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:264-281 | source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.cs:286-303 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:50— source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:50-67 | source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.cs:53-72 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) samples/Basic/tvOS/SkiaSharpSample/GpuGLViewController.cs:102— samples/Basic/tvOS/SkiaSharpSample/GpuGLViewController.cs:102-120 | samples/Basic/tvOS/SkiaSharpSample/GpuMetalViewController.cs:94-111 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:62— samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:62-79 | samples/Basic/WPF/SkiaSharpSample/DrawingPage.xaml.cs:84-101 — These two members are one piece of code written twice and then edited apart: 18 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.
async void method: BackClicked samples/Gallery/Maui/Controls/GalleryHeader.xaml.cs:77— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: CardTapped samples/Gallery/Maui/Controls/GallerySampleCard.xaml.cs:9— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnGallerySelectionChanged samples/Gallery/Maui/GalleryPage.xaml.cs:119— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OpenClicked samples/Gallery/Maui/SampleDetailPage.xaml.cs:66— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShareClicked samples/Gallery/Maui/SampleDetailPage.xaml.cs:67— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
Sync-over-async (deadlock risk) source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:294— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:322— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) utils/SkiaSharpGenerator/Cookies/CookieCommand.cs:64— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:79— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) utils/SkiaSharpGenerator/Verify/VerifyCommand.cs:61— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Duplicated block (9 lines × 2) binding/SkiaSharp/SKMatrix44.cs:195— binding/SkiaSharp/SKMatrix44.cs:195-203 | binding/SkiaSharp/SKMatrix44.cs:211-219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (9 lines × 2) .agents/skills/review-skia-update/scripts/regenerate_bindings.py:57— .agents/skills/review-skia-update/scripts/regenerate_bindings.py:57-65 | .agents/skills/update-skia/scripts/regenerate_bindings.py:59-67 — before extracting anything, compare `.agents/skills/review-skia-update/scripts/regenerate_bindings.py` and `.agents/skills/update-skia/scripts/regenerate_bindings.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:134— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:134-142 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:134-142 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (9 lines × 2) samples/Gallery/Shared/Samples/WideGamutP3Sample.cs:225— samples/Gallery/Shared/Samples/WideGamutP3Sample.cs:225-233 | samples/Gallery/Shared/Samples/WideGamutP3Sample.cs:237-245 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) .agents/skills/review-skia-update/scripts/regenerate_bindings.py:175— .agents/skills/review-skia-update/scripts/regenerate_bindings.py:175-187 | .agents/skills/update-skia/scripts/regenerate_bindings.py:177-189 — before extracting anything, compare `.agents/skills/review-skia-update/scripts/regenerate_bindings.py` and `.agents/skills/update-skia/scripts/regenerate_bindings.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (13 lines × 2) samples/Gallery/Shared/Samples/ColorFontSample.cs:70— samples/Gallery/Shared/Samples/ColorFontSample.cs:70-82 | samples/Gallery/Shared/Samples/VariableFontSample.cs:75-87 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) samples/Basic/tvOS/SkiaSharpSample/GpuGLViewController.cs:106— samples/Basic/tvOS/SkiaSharpSample/GpuGLViewController.cs:106-118 | samples/Basic/tvOS/SkiaSharpSample/GpuMetalViewController.cs:97-109 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:127— samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:127-139 | samples/Basic/WinUI/SkiaSharpSample/GpuPage.xaml.cs:117-129 — 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.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×4
Owned disposable field is never released source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:28— `SKGLView` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `context` itself (line 28), which makes that instance its own. But `context` is named in none of the methods the disposal search covered: `Dispose` (line 223) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`context?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:29— `SKGLView` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `glInterface` itself (line 29), which makes that instance its own. But `glInterface` is named in none of the methods the disposal search covered: `Dispose` (line 223) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`glInterface?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:30— `SKGLView` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `renderTarget` itself (line 30), which makes that instance its own. But `renderTarget` is named in none of the methods the disposal search covered: `Dispose` (line 223) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`renderTarget?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:32— `SKGLView` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `surface` itself (line 32), which makes that instance its own. But `surface` is named in none of the methods the disposal search covered: `Dispose` (line 223) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`surface?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Swallowed exception (empty catch) source/SkiaSharp.Views/SkiaSharp.Views.Blazor/Internal/SKHtmlCanvasInterop.cs:149— 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) samples/Basic/Tizen/SkiaSharpSample/GpuPage.cs:114— 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) utils/SkiaSharpGenerator/BaseTool.cs:103— 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) utils/SkiaSharpGenerator/BaseTool.cs:144— 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.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×4
Symbol treated as nullable, then dereferenced unguarded binding/SkiaSharp/SKRuntimeEffect.cs:33— This method contradicts itself about `errorString`: line 34 writes `errorString?.ToString`, which says `errorString` can be null, but line 33 then dereferences it directly as `errorString.Handle` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `errorString` truly cannot be null here, the `?.` is misleading. Settle it one way — test `errorString` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded binding/SkiaSharp/SKRuntimeEffect.cs:49— This method contradicts itself about `errorString`: line 50 writes `errorString?.ToString`, which says `errorString` can be null, but line 49 then dereferences it directly as `errorString.Handle` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `errorString` truly cannot be null here, the `?.` is misleading. Settle it one way — test `errorString` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded binding/SkiaSharp/SKRuntimeEffect.cs:65— This method contradicts itself about `errorString`: line 66 writes `errorString?.ToString`, which says `errorString` can be null, but line 65 then dereferences it directly as `errorString.Handle` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `errorString` truly cannot be null here, the `?.` is misleading. Settle it one way — test `errorString` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded binding/SkiaSharp/Util.cs:86— This method contradicts itself about `objects`: line 84 writes `objects?.Length`, which says `objects` can be null, but line 86 then dereferences it directly with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `objects` truly cannot be null here, the `?.` is misleading. Settle it one way — test `objects` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Low contrast colour pair in CSS (2.1:1) .agents/skills/skill-creator/eval-viewer/viewer.html:83— `.section-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.1:1) .agents/skills/skill-creator/eval-viewer/viewer.html:136— `.output-file-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.1:1) .agents/skills/skill-creator/eval-viewer/viewer.html:221— `.prev-feedback` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.2:1) .agents/skills/skill-creator/eval-viewer/viewer.html:302— `.grade-pass` sets color: #788c5d on background-color: #eef2e8 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.2:1) samples/Gallery/Blazor/Components/TagPill.razor.css:44— `.api-tag.tag-method.active` sets color: white on background-color: #d97706 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.2:1) samples/Gallery/Blazor/Components/TagPill.razor.css:81— `[data-theme="dark"] .api-tag.tag-method.active` sets color: white on background-color: #d97706 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Hotspot: scripts/infra/docs/release-notes-data.py scripts/infra/docs/release-notes-data.py:2173— scripts/infra/docs/release-notes-data.py changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in release-notes-data.build_data_json at line 2173. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 04:05:50 +02:00' --until='2026-11-17 04:05:50 +02:00' --full-history --no-merges -- scripts/infra/docs/release-notes-data.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: utils/SkiaSharpGenerator/Generate/Generator.cs utils/SkiaSharpGenerator/Generate/Generator.cs:539— utils/SkiaSharpGenerator/Generate/Generator.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in Generator.WriteFunctions at line 539. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 04:05:50 +02:00' --until='2026-11-17 04:05:50 +02:00' --full-history --no-merges -- utils/SkiaSharpGenerator/Generate/Generator.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: .agents/skills/update-skia/scripts/update_versions.py .agents/skills/update-skia/scripts/update_versions.py:409— .agents/skills/update-skia/scripts/update_versions.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in update_versions.update_versions at line 409. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 04:05:50 +02:00' --until='2026-11-17 04:05:50 +02:00' --full-history --no-merges -- .agents/skills/update-skia/scripts/update_versions.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) .agents/skills/review-skia-update/scripts/check_deps.py:26— .agents/skills/review-skia-update/scripts/check_deps.py:26-45 | .agents/skills/update-skia/scripts/update_versions.py:87-101 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) binding/HarfBuzzSharp/Tag.cs:56— binding/HarfBuzzSharp/Tag.cs:56-70 | binding/SkiaSharp/SKFourByteTag.cs:63-77 — 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) samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:103— samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:103-117 | samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs:102-119 — 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 (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) binding/SkiaSharp.Skottie/Animation.cs:122— binding/SkiaSharp.Skottie/Animation.cs:122-133 | binding/SkiaSharp.Skottie/AnimationBuilder.cs:92-106 — 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) binding/SkiaSharp/SKFont.cs:1013— binding/SkiaSharp/SKFont.cs:1013-1024 | binding/SkiaSharp/SKFont.cs:1211-1222 — 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) binding/SkiaSharp/SKFont.cs:880— binding/SkiaSharp/SKFont.cs:880-891 | binding/SkiaSharp/SKFont.cs:1027-1038 — 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 copies of one member (3 members, 8+ corresponding lines) · ×3
Edited copies of one member (3 members, 8+ corresponding lines) binding/SkiaSharp/SKBitmap.cs:969— binding/SkiaSharp/SKBitmap.cs:969-979 | binding/SkiaSharp/SKData.cs:317-324 | binding/SkiaSharp/SKImage.cs:266-278 — 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) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:145— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:145-152 | samples/Basic/WPF/SkiaSharpSample/DrawingPage.xaml.cs:232-242 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:145-152 — 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) samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:187— samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:187-194 | samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:177-185 | samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.cs:162-169 — 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) · ×3
Edited copy of a member (10 corresponding lines) binding/SkiaSharp/SKColor.cs:110— binding/SkiaSharp/SKColor.cs:110-119 | binding/SkiaSharp/SKColor.cs:129-138 — 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) source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:97— source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:97-106 | source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:104-113 — 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) binding/SkiaSharp/SKBitmap.cs:1009— binding/SkiaSharp/SKBitmap.cs:1009-1018 | binding/SkiaSharp/SKSurface.cs:1046-1055 — 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.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) binding/SkiaSharp/MathTypes.cs:70— binding/SkiaSharp/MathTypes.cs:70-74 | binding/SkiaSharp/MathTypes.cs:308-312 — 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) .agents/skills/ci-status/scripts/render-ci-status-md.py:38— .agents/skills/ci-status/scripts/render-ci-status-md.py:38-42 | .agents/skills/security-audit/scripts/render-security-audit-md.py:53-60 — 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) binding/SkiaSharp/SKPixmap.cs:431— binding/SkiaSharp/SKPixmap.cs:431-435 | binding/SkiaSharp/SKWebpEncoder.cs:70-76 — 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 (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:204— source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:204-214 | source/SkiaSharp.Views/SkiaSharp.Views.WPF/WPFExtensions.cs:173-183 — 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) source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:187— source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:187-197 | source/SkiaSharp.Views/SkiaSharp.Views.WPF/WPFExtensions.cs:156-166 — 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) samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:83— samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:83-94 | samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs:83-93 — 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.
Duplicated block (15 lines × 2) binding/SkiaSharp/GRVkBackendContext.cs:97— binding/SkiaSharp/GRVkBackendContext.cs:97-111 | binding/SkiaSharp/Gpu/Graphite/SKGraphiteVkBackendContext.cs:73-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) samples/Gallery/Shared/Samples/CanvasTransformsSample.cs:89— samples/Gallery/Shared/Samples/CanvasTransformsSample.cs:89-103 | samples/Gallery/Shared/Samples/ThreeDSample.cs:125-139 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:120— samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:120-134 | samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs:119-133 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs` and `samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 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. 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 (10 lines × 2) binding/SkiaSharp/SKColorF.cs:220— binding/SkiaSharp/SKColorF.cs:220-229 | binding/SkiaSharp/SKColorF.cs:271-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) binding/SkiaSharp/SKTextBlob.cs:106— binding/SkiaSharp/SKTextBlob.cs:106-115 | binding/SkiaSharp/SKTextBlob.cs:240-249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) .agents/skills/review-skia-update/scripts/check_companion.py:26— .agents/skills/review-skia-update/scripts/check_companion.py:26-35 | .agents/skills/review-skia-update/scripts/check_source.py:40-49 — 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. 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 (12 lines × 2) binding/SkiaSharp/SKImage.cs:1188— binding/SkiaSharp/SKImage.cs:1188-1199 | binding/SkiaSharp/SKSurface.cs:1109-1120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) utils/SkiaSharpGenerator/Generate/Generator.cs:158— utils/SkiaSharpGenerator/Generate/Generator.cs:158-169 | utils/SkiaSharpGenerator/Generate/Generator.cs:670-681 — both copies are in the same file, so extract the 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 `utils/SkiaSharpGenerator/Generate/Generator.cs:158` 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) .agents/skills/review-skia-update/scripts/regenerate_bindings.py:106— .agents/skills/review-skia-update/scripts/regenerate_bindings.py:106-117 | .agents/skills/update-skia/scripts/regenerate_bindings.py:108-119 — before extracting anything, compare `.agents/skills/review-skia-update/scripts/regenerate_bindings.py` and `.agents/skills/update-skia/scripts/regenerate_bindings.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) source/SkiaSharp.Vulkan/SkiaSharp.Vulkan.SharpVk/GRSharpVkBackendContext.cs:42— source/SkiaSharp.Vulkan/SkiaSharp.Vulkan.SharpVk/GRSharpVkBackendContext.cs:42-52 | source/SkiaSharp.Vulkan/SkiaSharp.Vulkan.Silk.NET/GRSilkNetBackendContext.cs:75-85 — 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. 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 (11 lines × 2) samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:107— samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:107-117 | samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs:109-119 — before extracting anything, compare `samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs` and `samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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 `samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:107` 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.
Duplicated block (11 lines × 2) samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:138— samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:138-148 | samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs:137-147 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs` and `samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 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. 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.
Unfinished stub — throws NotImplementedException source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Ref.cs:11— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Ref.cs:11— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKSwapChainPanel.cs:59— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Ref.cs:11— `CreatePlatformView` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Ref.cs:11— `CreatePlatformView` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKSwapChainPanel.cs:59— `DrawInBackground` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Outbound HTTP without resilience samples/Basic/BlazorWebAssembly/SkiaSharpSample/Program.cs:11— `new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Outbound HTTP without resilience samples/Gallery/Blazor/Program.cs:11— `new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
Outbound HTTP without resilience utils/SkiaSharpGenerator/Cookies/CookieDetector.cs:194— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
X18 · Disposal-pattern correctness· Owned disposable field overwritten without releasing the previous instance · ×3
Owned disposable field overwritten without releasing the previous instance source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKSwapChainPanel.cs:115— `renderTarget` is a `GRBackendRenderTarget` this type creates itself, and here (line 115) a new instance is written over it — but `GetRenderTarget` itself reads through `renderTarget` before replacing it, so it expects an instance to be there, and nothing earlier in `GetRenderTarget` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`renderTarget?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
Owned disposable field overwritten without releasing the previous instance source/SkiaSharp.Views/SkiaSharp.Views.Gtk4/SKGLArea.cs:156— `renderTarget` is a `GRBackendRenderTarget` this type creates itself, and here (line 156) a new instance is written over it — but `Render` itself reads through `renderTarget` before replacing it, so it expects an instance to be there, and nothing earlier in `Render` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`renderTarget?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
Owned disposable field overwritten without releasing the previous instance source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKControl.cs:151— `bitmap` is a `Bitmap` this type creates itself, and here (line 151) a new instance is written over it — but `CreateBitmap` itself reads through `bitmap` before replacing it, so it expects an instance to be there, and nothing earlier in `CreateBitmap` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`bitmap?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×3
Disposable created and abandoned in the method that made it benchmarks/SkiaSharp.Benchmarks/Benchmarks/SurfaceCanvasBenchmark.cs:136— `builder` is a `SKPathBuilder`, which implements `IDisposable`, and it is created here (line 136). Every use of it in `CreateStar` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var builder = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it utils/SkiaSharpGenerator/BaseTool.cs:84— `process` is a `Process`, which implements `IDisposable`, and it is created here (line 84). Every use of it in `ParseSkiaHeaders` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var process = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it utils/SkiaSharpGenerator/BaseTool.cs:121— `process` is a `Process`, which implements `IDisposable`, and it is created here (line 121). Every use of it in `ParseSkiaHeaders` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var process = …;`), which releases it at the end of the scope on every path including a throw.
AC3 · Page structure· Heading level jumps from h4 to h6 · ×2
Heading level jumps from h4 to h6 .agents/skills/ci-status/scripts/viewer.html:75— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h4 to h6 .agents/skills/issue-triage/scripts/viewer.html:65— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Low contrast colour pair in CSS (3.1:1) .agents/skills/skill-creator/assets/eval_review.html:19— `.btn-export` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.1:1) .agents/skills/skill-creator/eval-viewer/viewer.html:467— `.done-btn.ready` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) .agents/skills/skill-creator/eval-viewer/viewer.html:303— `.grade-fail` sets color: #c44 on background-color: #fceaea — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) samples/Gallery/Blazor/Components/FilterRail.razor.css:82— `.cat-item.active` sets color: #6366f1 on background-color: #eef2ff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
BarePragmaDisable samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:183— #pragma warning disable CA1422 — 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 samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:183— #pragma warning disable CA1422 — 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.
MethodTooLong: GLThread.GuardedRun source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1051— MethodTooLong — GuardedRun runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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: Generator.WriteStruct utils/SkiaSharpGenerator/Generate/Generator.cs:240— MethodTooLong — WriteStruct runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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.
Change coupling: SKGLLayer.cs ↔ SKGLView.cs source/SkiaSharp.Views/SkiaSharp.Views/Platform/iOS/SKGLLayer.cs:1— `source/SkiaSharp.Views/SkiaSharp.Views/Platform/iOS/SKGLLayer.cs` and `source/SkiaSharp.Views/SkiaSharp.Views/Platform/iOS/SKGLView.cs` change together 81% of the time (13 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `4af3a500` Use pointer-based GLES interop signatures (#5155); `457e9b0e` Author view remarks as Markdown (#5091); `73bfe559` Re-work views to avoid incorrect disposal (#1180) (at that commit the files were still `source/SkiaSharp.Views/SkiaSharp.Views.AppleiOS/SKGLLayer.cs` and `source/SkiaSharp.Views/SkiaSharp.Views.AppleiOS/SKGLView.cs`) — run `git show` on any of them.
Change coupling: SKGLLayer.cs ↔ SKGLView.cs source/SkiaSharp.Views/SkiaSharp.Views/Platform/iOS/SKGLLayer.cs:1— `source/SkiaSharp.Views/SkiaSharp.Views/Platform/iOS/SKGLLayer.cs` and `source/SkiaSharp.Views/SkiaSharp.Views/Platform/macOS/SKGLView.cs` change together 64% of the time (9 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `4af3a500` Use pointer-based GLES interop signatures (#5155); `73bfe559` Re-work views to avoid incorrect disposal (#1180) (at that commit the files were still `source/SkiaSharp.Views/SkiaSharp.Views.AppleiOS/SKGLLayer.cs` and `source/SkiaSharp.Views/SkiaSharp.Views.Mac/SKGLView.cs`); `ea9dd88f` Fix issues with buffer samples #1087 (#1098) (at that commit the files were still `source/SkiaSharp.Views/SkiaSharp.Views.AppleiOS/SKGLLayer.cs` and `source/SkiaSharp.Views/SkiaSharp.Views.Mac/SKGLView.cs`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) binding/SkiaSharp/SKImage.cs:1187— binding/SkiaSharp/SKImage.cs:1187-1202 | binding/SkiaSharp/SKSurface.cs:1108-1123 — 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) binding/HarfBuzzSharp/Buffer.cs:229— binding/HarfBuzzSharp/Buffer.cs:229-247 | binding/HarfBuzzSharp/Buffer.cs:370-385 — 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 copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs:151— source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs:151-171 | source/SkiaSharp.Views/SkiaSharp.Views.Gtk4/SKDrawingArea.cs:170-191 — 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.
Edited copy of a member (21 corresponding lines) samples/Gallery/Shared/Samples/CanvasTransformsSample.cs:125— samples/Gallery/Shared/Samples/CanvasTransformsSample.cs:125-147 | samples/Gallery/Shared/Samples/ThreeDSample.cs:173-193 — 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 (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) binding/HarfBuzzSharp/Font.cs:368— binding/HarfBuzzSharp/Font.cs:368-385 | binding/HarfBuzzSharp/Font.cs:521-533 — 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) scripts/infra/perf/_common.py:45— scripts/infra/perf/_common.py:45-57 | scripts/infra/perf/sizes/track.py:80-95 — 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 (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) binding/SkiaSharp/SKShader.cs:608— binding/SkiaSharp/SKShader.cs:608-621 | binding/SkiaSharp/SKShader.cs:634-647 — 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) samples/Gallery/Blazor/Pages/SamplePage.razor:196— samples/Gallery/Blazor/Pages/SamplePage.razor:196-209 | samples/Gallery/Blazor/Pages/SamplePage.razor:212-225 — 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 copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1402— source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1402-1424 | source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1427-1448 — 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) samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:118— samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:118-139 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:110-131 — 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 copies of one member (3 members, 7+ corresponding lines) · ×2
Edited copies of one member (3 members, 7+ corresponding lines) .agents/skills/review-skia-update/scripts/run_review.py:92— .agents/skills/review-skia-update/scripts/run_review.py:92-100 | .agents/skills/review-skia-update/scripts/run_review.py:104-110 | .agents/skills/review-skia-update/scripts/run_review.py:114-120 — 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) source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:161— source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:161-167 | source/SkiaSharp.Views/SkiaSharp.Views.WinUI/AngleSwapChainPanel.cs:174-181 | source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.cs:166-172 — 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 copy of a member (3 corresponding lines) · ×2
Edited copy of a member (3 corresponding lines) source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:58— source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:58-60 | source/SkiaSharp.Views/SkiaSharp.Views.WPF/WPFExtensions.cs:39-41 — These two members are one piece of code written twice and then edited apart: 3 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 (3 corresponding lines) scripts/infra/docs/release-notes-data.py:1190— scripts/infra/docs/release-notes-data.py:1190-1192 | scripts/infra/docs/release_notes/common.py:43-46 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (26 lines × 2) source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/SKPaintGLSurfaceEventArgs.cs:68— source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/SKPaintGLSurfaceEventArgs.cs:68-93 | source/SkiaSharp.Views/SkiaSharp.Views.Shared/SKPaintGLSurfaceEventArgs.cs:161-204 — 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 (26 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:156— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:156-181 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:156-181 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (22 lines × 2) binding/SkiaSharp/SKColorF.cs:241— binding/SkiaSharp/SKColorF.cs:241-262 | binding/SkiaSharp/SKColorF.cs:289-310 — both copies are in the same file, so extract the 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 `binding/SkiaSharp/SKColorF.cs:241` 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.
Duplicated block (22 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:12— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:12-33 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:12-33 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:36— utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:36-53 | utils/SkiaSharpGenerator/Verify/VerifyCommand.cs:32-49 — 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 `utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:36` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:55` calls `IsNullOrEmpty`, `Combine`, `GetCurrentDirectory` and `utils/SkiaSharpGenerator/Verify/VerifyCommand.cs:51` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) binding/SkiaSharp/SKMatrix.cs:40— binding/SkiaSharp/SKMatrix.cs:40-57 | binding/SkiaSharp/SKMatrix.cs:103-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:160— source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:160-175 | source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs:204-219 — 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 (16 lines × 2) .agents/skills/review-skia-update/scripts/regenerate_bindings.py:87— .agents/skills/review-skia-update/scripts/regenerate_bindings.py:87-102 | .agents/skills/update-skia/scripts/regenerate_bindings.py:89-104 — before extracting anything, compare `.agents/skills/review-skia-update/scripts/regenerate_bindings.py` and `.agents/skills/update-skia/scripts/regenerate_bindings.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) utils/SkiaSharpGenerator/Generate/Generator.cs:168— utils/SkiaSharpGenerator/Generate/Generator.cs:168-172 | utils/SkiaSharpGenerator/Generate/Generator.cs:225-229 | utils/SkiaSharpGenerator/Generate/Generator.cs:426-430 — 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 `utils/SkiaSharpGenerator/Generate/Generator.cs:168` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) samples/Gallery/Shared/Samples/BlurImageFilterSample.cs:49— samples/Gallery/Shared/Samples/BlurImageFilterSample.cs:49-53 | samples/Gallery/Shared/Samples/ImageFilterCropSample.cs:83-87 | samples/Gallery/Shared/Samples/PhotoLabSample.cs:49-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 all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) .agents/skills/sample-scout/scripts/render-sample-scout.py:52— .agents/skills/sample-scout/scripts/render-sample-scout.py:52-70 | .agents/skills/skia-analyst/scripts/render-skia-analyst.py:67-85 — 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 (19 lines × 2) samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:98— samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:98-116 | samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs:97-115 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs` and `samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 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. 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 (8 lines × 3) .agents/skills/ci-status/scripts/render-ci-status.py:32— .agents/skills/ci-status/scripts/render-ci-status.py:32-40 | .agents/skills/issue-triage/scripts/render-triage-report.py:152-159 | .agents/skills/security-audit/scripts/render-security-audit.py:32-40 — before extracting anything, compare `.agents/skills/ci-status/scripts/render-ci-status.py` and `.agents/skills/issue-triage/scripts/render-triage-report.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `.agents/skills/issue-triage/scripts/render-triage-report.py:151` calls `with_suffix` and `.agents/skills/ci-status/scripts/render-ci-status.py:31` 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 × 3) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:135— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:135-142 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:143-150 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:135-142 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:123— samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:123-156 | samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:130-172 | samples/Basic/Gtk4/SkiaSharpSample/DrawingPage.cs:218-260 | samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:105-131 | samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:112-154 | samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.cs:101-143 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:134— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:134-142 | samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:145-152 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:142-150 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:153-160 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:134-142 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:145-152 — 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 copy of a member (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) samples/Gallery/Shared/Samples/ColorFontSample.cs:61— samples/Gallery/Shared/Samples/ColorFontSample.cs:61-94 | samples/Gallery/Shared/Samples/VariableFontSample.cs:62-99 — These two members are one piece of code written twice and then edited apart: 34 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 (34 corresponding lines) scripts/infra/docs/release-notes-data.py:658— scripts/infra/docs/release-notes-data.py:658-691 | scripts/infra/docs/release-notes-data.py:774-810 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 2) samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:140— samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:140-153 | samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:115-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:140` calls `Scale` and `samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:115` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) samples/Basic/Tizen/SkiaSharpSample/DrawingPage.cs:170— samples/Basic/Tizen/SkiaSharpSample/DrawingPage.cs:170-183 | samples/Basic/WPF/SkiaSharpSample/DrawingPage.xaml.cs:120-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 3) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:146— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:146-152 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:154-160 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:146-152 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (7 lines × 3) samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:129— samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:129-135 | samples/Basic/WinUI/SkiaSharpSample/GpuPage.xaml.cs:119-125 | samples/Basic/WindowsForms/SkiaSharpSample/GpuPage.cs:104-110 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5 lines × 6) samples/Gallery/Shared/Samples/VectorArtSample.cs:99— samples/Gallery/Shared/Samples/VectorArtSample.cs:99-103 | samples/Gallery/Shared/Samples/VectorArtSample.cs:105-109 | samples/Gallery/Shared/Samples/VectorArtSample.cs:122-126 | samples/Gallery/Shared/Samples/VectorArtSample.cs:127-131 | samples/Gallery/Shared/Samples/VectorArtSample.cs:134-138 | samples/Gallery/Shared/Samples/VectorArtSample.cs:139-143 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/Gallery/Shared/Samples/VectorArtSample.cs:132` calls `LineTo` and `samples/Gallery/Shared/Samples/VectorArtSample.cs:127` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 6) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:135— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:135-139 | samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:146-150 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:143-147 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:154-158 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:135-139 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:146-150 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:135` 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.
Low cohesion: SKGLView (LCOM4 5) source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Controls/SKGLView.cs:13— SKGLView's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FilterRailView (LCOM4 4) samples/Gallery/Maui/Controls/FilterRailView.xaml.cs:5— FilterRailView's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low contrast colour pair in CSS (2.9:1) .agents/skills/skill-creator/assets/eval_review.html:17— `.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.0:1) .agents/skills/skill-creator/eval-viewer/viewer.html:197— `.output-file-content .download-link` sets color: #d97757 on background-color: #faf9f5 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement samples/Gallery/Blazor/Components/FilterRail.razor.css:24— `.rail-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Stateful shared instance: DpiWatcherInterop source/SkiaSharp.Views/SkiaSharp.Views.Blazor/Internal/DpiWatcherInterop.cs:12— `DpiWatcherInterop` keeps one instance of itself in the static `instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (callbackReference; e.g. `callbackReference` at line 89).
run_review.main (cyclomatic 68) .agents/skills/review-skia-update/scripts/run_review.py:134— run_review.main has cyclomatic complexity 68 (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.
render-security-audit-md.render_md (cyclomatic 61) .agents/skills/security-audit/scripts/render-security-audit-md.py:63— render-security-audit-md.render_md has cyclomatic complexity 61 (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.
validate-skia-review.main (cyclomatic 57) .agents/skills/review-skia-update/scripts/validate-skia-review.py:14— validate-skia-review.main has cyclomatic complexity 57 (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.
render-ci-status-md.render (cyclomatic 46) .agents/skills/ci-status/scripts/render-ci-status-md.py:83— render-ci-status-md.render has cyclomatic complexity 46 (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.
GLThread.GuardedRun (cyclomatic 44) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1051— GLThread.GuardedRun has cyclomatic complexity 44 (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.
ci-status.render_console (cyclomatic 39) .agents/skills/ci-status/scripts/ci-status.py:625— ci-status.render_console has cyclomatic complexity 39 (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.
SKColorParseStrategyBenchmark.Parse (cyclomatic 33) benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseStrategyBenchmark.cs:199— SKColorParseStrategyBenchmark.Parse has cyclomatic complexity 33 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. Note what this body is, though: it carries an aggressive-inlining request, so its author has asked in the source for this body to be inlined into every caller. Each part pulled out of it becomes a call the runtime has to decide to inline again, against a size budget — so the split can quietly turn one inlined body into several real calls, on the path the marker exists to protect. The measurement stands — a hot path is not a licence to be unreadable — but the move that pays here is to lift the COLD parts out first (argument validation, fallback and error paths, one-off setup) and leave the kernel whole. Where the kernel itself has to be divided, ask for the extracted parts to be inlined as well, and measure the result rather than assuming the division is free.
query-cg-alerts.main (cyclomatic 33) .agents/skills/security-audit/scripts/query-cg-alerts.py:226— query-cg-alerts.main has cyclomatic complexity 33 (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.
check_source.get_diff_of_diffs (cyclomatic 31) .agents/skills/review-skia-update/scripts/check_source.py:52— check_source.get_diff_of_diffs has cyclomatic complexity 31 (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.
update_versions.reconcile_dependency_metadata (cyclomatic 31) .agents/skills/update-skia/scripts/update_versions.py:166— update_versions.reconcile_dependency_metadata has cyclomatic complexity 31 (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.
query-milestone-schedule.build_support_alerts (cyclomatic 29) .agents/skills/security-audit/scripts/query-milestone-schedule.py:269— query-milestone-schedule.build_support_alerts has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
render-sample-scout.main (cyclomatic 28) .agents/skills/sample-scout/scripts/render-sample-scout.py:51— render-sample-scout.main has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
render-skia-analyst.main (cyclomatic 28) .agents/skills/skia-analyst/scripts/render-skia-analyst.py:66— render-skia-analyst.main has cyclomatic complexity 28 (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.
update_versions.update_versions (cyclomatic 27) .agents/skills/update-skia/scripts/update_versions.py:409— update_versions.update_versions has cyclomatic complexity 27 (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.
SKColorParseSpanBenchmark.ParseStringIndex (cyclomatic 26) benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseSpanBenchmark.cs:99— SKColorParseSpanBenchmark.ParseStringIndex has cyclomatic complexity 26 (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.
Generator.WriteStruct (cyclomatic 26) utils/SkiaSharpGenerator/Generate/Generator.cs:240— Generator.WriteStruct has cyclomatic complexity 26 (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.
check_companion.run_check (cyclomatic 25) .agents/skills/review-skia-update/scripts/check_companion.py:55— check_companion.run_check has cyclomatic complexity 25 (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.
Generator.WriteFunctions (cyclomatic 22) utils/SkiaSharpGenerator/Generate/Generator.cs:539— Generator.WriteFunctions has cyclomatic complexity 22 (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.
SKMatrix44.this[].set (cyclomatic 21) binding/SkiaSharp/SKMatrix44.cs:581— SKMatrix44.this[].set has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: SKMatrix44.this[].get (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
query-milestone-schedule.main (cyclomatic 21) .agents/skills/security-audit/scripts/query-milestone-schedule.py:373— query-milestone-schedule.main 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.
SKColorParseSpanBenchmark.ParseSpanTrim (cyclomatic 20) benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseSpanBenchmark.cs:139— SKColorParseSpanBenchmark.ParseSpanTrim has cyclomatic complexity 20 (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.
BaseTool.ParseSkiaHeaders (cyclomatic 20) utils/SkiaSharpGenerator/BaseTool.cs:47— BaseTool.ParseSkiaHeaders has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
check_deps.run_check (cyclomatic 20) .agents/skills/review-skia-update/scripts/check_deps.py:110— check_deps.run_check 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.
SKColor.TryParse (cyclomatic 19) binding/SkiaSharp/SKColor.cs:259— SKColor.TryParse has cyclomatic complexity 19 (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.
DocumentationStore.GetDocKey (cyclomatic 19) utils/SkiaSharpGenerator/Generate/DocumentationStore.cs:86— DocumentationStore.GetDocKey has cyclomatic complexity 19 (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 is NOT this file's highest cyclomatic complexity: DocumentationStore.GetOperatorMetadataName (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
LibraryLoader.LoadLocalLibrary (cyclomatic 18) binding/Binding.Shared/LibraryLoader.cs:34— LibraryLoader.LoadLocalLibrary has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (GetLibraryPath, CheckLibraryPath). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SKFont.GetTextPathOnPath (cyclomatic 18) binding/SkiaSharp/SKFont.cs:1563— SKFont.GetTextPathOnPath has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 2 function items inside it that branch. 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.
SKColorParseStrategyBenchmark.ParseAccum (cyclomatic 18) benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseStrategyBenchmark.cs:366— SKColorParseStrategyBenchmark.ParseAccum has cyclomatic complexity 18 (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. This is NOT this file's highest cyclomatic complexity: GiantSwitch.TryNibble (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Utils.GetPreambleSize (cyclomatic 17) binding/SkiaSharp/Util.cs:14— Utils.GetPreambleSize has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
query-chrome-releases.fetch_all_posts (cyclomatic 17) .agents/skills/security-audit/scripts/query-chrome-releases.py:151— query-chrome-releases.fetch_all_posts has cyclomatic complexity 17 (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.
SKPixmap.GetPixelSpan (cyclomatic 16) binding/SkiaSharp/SKPixmap.cs:243— SKPixmap.GetPixelSpan has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ci-status.collect_data (cyclomatic 16) .agents/skills/ci-status/scripts/ci-status.py:497— ci-status.collect_data has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Test cannot fail: ExceptionsThrownInTheConstructorFailGracefully tests/Tests/SkiaSharp/SKObjectTest.cs:183— This test's act runs inside `catch (Exception)` at line 191 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. Adding an assertion inside that region does not fix it: the assertion throws, and the same catch swallows it exactly like the exception it replaced. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
ci-status.render_console (cognitive 175) .agents/skills/ci-status/scripts/ci-status.py:625— ci-status.render_console has cognitive complexity 175 (threshold 15). Drivers by points: if/else 24 (87 pts), loops 16 (61 pts), ternaries 5 (26 pts), boolean chains 1 (nesting depth added 129). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
render-security-audit-md.render_md (cognitive 153) .agents/skills/security-audit/scripts/render-security-audit-md.py:63— render-security-audit-md.render_md has cognitive complexity 153 (threshold 15). Drivers by points: if/else 36 (89 pts), ternaries 8 (30 pts), loops 10 (26 pts), boolean chains 8 (nesting depth added 91). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GLThread.GuardedRun (cognitive 116) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1051— GLThread.GuardedRun has cognitive complexity 116 (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.
render-ci-status-md.render (cognitive 113) .agents/skills/ci-status/scripts/render-ci-status-md.py:83— render-ci-status-md.render has cognitive complexity 113 (threshold 15). Drivers by points: if/else 22 (47 pts), loops 15 (37 pts), ternaries 7 (27 pts), boolean chains 2 (nesting depth added 67). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
validate-skia-review.main (cognitive 93) .agents/skills/review-skia-update/scripts/validate-skia-review.py:14— validate-skia-review.main has cognitive complexity 93 (threshold 15). Drivers by points: if/else 24 (52 pts), loops 15 (25 pts), boolean chains 15, error handling 1 (nesting depth added 38). 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.
query-cg-alerts.main (cognitive 90) .agents/skills/security-audit/scripts/query-cg-alerts.py:226— query-cg-alerts.main has cognitive complexity 90 (threshold 15). Drivers by points: if/else 21 (54 pts), loops 13 (34 pts), ternaries 1 (2 pts) (nesting depth added 55). 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.
run_review.main (cognitive 81) .agents/skills/review-skia-update/scripts/run_review.py:134— run_review.main has cognitive complexity 81 (threshold 15). Drivers by points: if/else 32 (45 pts), boolean chains 21, loops 7 (9 pts), error handling 4, ternaries 2 (nesting depth added 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.
Generator.WriteStruct (cognitive 64) utils/SkiaSharpGenerator/Generate/Generator.cs:240— Generator.WriteStruct has cognitive complexity 64 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
update_versions.reconcile_dependency_metadata (cognitive 56) .agents/skills/update-skia/scripts/update_versions.py:166— update_versions.reconcile_dependency_metadata has cognitive complexity 56 (threshold 15). Drivers by points: if/else 18 (42 pts), ternaries 3 (6 pts), boolean chains 5, loops 3 (nesting depth added 27). 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.
Generator.WriteFunctions (cognitive 53) utils/SkiaSharpGenerator/Generate/Generator.cs:539— Generator.WriteFunctions has cognitive complexity 53 (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.
check_source.get_diff_of_diffs (cognitive 48) .agents/skills/review-skia-update/scripts/check_source.py:52— check_source.get_diff_of_diffs has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (23 pts), loops 11 (21 pts), boolean chains 3, ternaries 1 (nesting depth added 17). 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.
ci-status.collect_data (cognitive 45) .agents/skills/ci-status/scripts/ci-status.py:497— ci-status.collect_data has cognitive complexity 45 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 4 (10 pts), error handling 1 (6 pts), ternaries 2 (6 pts), boolean chains 2 (nesting depth added 30). 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.
query-chrome-releases.fetch_all_posts (cognitive 40) .agents/skills/security-audit/scripts/query-chrome-releases.py:151— query-chrome-releases.fetch_all_posts has cognitive complexity 40 (threshold 15). Drivers by points: if/else 8 (19 pts), ternaries 3 (9 pts), error handling 2 (7 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 23). 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.
BaseTool.ParseSkiaHeaders (cognitive 38) utils/SkiaSharpGenerator/BaseTool.cs:47— BaseTool.ParseSkiaHeaders has cognitive complexity 38 (threshold 15). Of this number, 35 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
query-milestone-schedule.build_support_alerts (cognitive 38) .agents/skills/security-audit/scripts/query-milestone-schedule.py:269— query-milestone-schedule.build_support_alerts has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (23 pts), ternaries 5 (6 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 10). 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.
check_deps._extract_dict (cognitive 37) .agents/skills/review-skia-update/scripts/check_deps.py:48— check_deps._extract_dict has cognitive complexity 37 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 3 (10 pts), ternaries 1 (8 pts), error handling 1 (7 pts), boolean chains 1 (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
check_deps.run_check (cognitive 37) .agents/skills/review-skia-update/scripts/check_deps.py:110— check_deps.run_check has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 4 (10 pts), boolean chains 4, ternaries 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check_companion.run_check (cognitive 36) .agents/skills/review-skia-update/scripts/check_companion.py:55— check_companion.run_check has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 8 (14 pts), boolean chains 3, ternaries 1 (nesting depth added 14). 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.
render-skia-analyst.main (cognitive 35) .agents/skills/skia-analyst/scripts/render-skia-analyst.py:66— render-skia-analyst.main has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (19 pts), ternaries 4 (7 pts), loops 5 (6 pts), boolean chains 2, error handling 1 (nesting depth added 8). 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.
render-sample-scout.main (cognitive 34) .agents/skills/sample-scout/scripts/render-sample-scout.py:51— render-sample-scout.main has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16, loops 5 (10 pts), ternaries 2 (4 pts), boolean chains 3, error handling 1 (nesting depth added 7). 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.
update_versions.update_versions (cognitive 33) .agents/skills/update-skia/scripts/update_versions.py:409— update_versions.update_versions has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 6, loops 2 (3 pts), ternaries 2 (nesting depth added 7). 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.
query-milestone-schedule.main (cognitive 30) .agents/skills/security-audit/scripts/query-milestone-schedule.py:373— query-milestone-schedule.main has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 4, loops 3, ternaries 1 (3 pts) (nesting depth added 8). 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.
query-cg-alerts.parse_cg_log (cognitive 29) .agents/skills/security-audit/scripts/query-cg-alerts.py:158— query-cg-alerts.parse_cg_log has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (21 pts), ternaries 1 (3 pts), boolean chains 2, loops 2, error handling 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
install-debs.parse_package_index (cognitive 28) eng/common/cross/install-debs.py:221— install-debs.parse_package_index has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (21 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
install-debs.resolve_dependencies (cognitive 24) eng/common/cross/install-debs.py:196— install-debs.resolve_dependencies has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 2 (5 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 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.
query-milestone-schedule.build_headsup (cognitive 23) .agents/skills/security-audit/scripts/query-milestone-schedule.py:224— query-milestone-schedule.build_headsup has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3 (9 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenerateCommand.OnInvoke (cognitive 22) utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:61— GenerateCommand.OnInvoke has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
install-debs.install_packages (cognitive 22) eng/common/cross/install-debs.py:259— install-debs.install_packages has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 11). 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.
SampleDetailPage.UpdateLayout (cognitive 21) samples/Gallery/Maui/SampleDetailPage.xaml.cs:402— SampleDetailPage.UpdateLayout has cognitive complexity 21 (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.
query-milestone-schedule.print_summary (cognitive 21) .agents/skills/security-audit/scripts/query-milestone-schedule.py:499— query-milestone-schedule.print_summary has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 3 (7 pts), loops 4 (6 pts), boolean chains 4, if/else 3 (4 pts) (nesting depth added 7). 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.
SKPixmap.GetPixelSpan (cognitive 20) binding/SkiaSharp/SKPixmap.cs:243— SKPixmap.GetPixelSpan has cognitive complexity 20 (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.
SKColorParseSpanBenchmark.ParseStringIndex (cognitive 20) benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseSpanBenchmark.cs:99— SKColorParseSpanBenchmark.ParseStringIndex has cognitive complexity 20 (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.
SKColorParseStrategyBenchmark.Parse (cognitive 20) benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseStrategyBenchmark.cs:199— SKColorParseStrategyBenchmark.Parse has cognitive complexity 20 (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. Note what this body is, though: it carries an aggressive-inlining request, so its author has asked in the source for this body to be inlined into every caller. Each part pulled out of it becomes a call the runtime has to decide to inline again, against a size budget — so the split can quietly turn one inlined body into several real calls, on the path the marker exists to protect. The measurement stands — a hot path is not a licence to be unreadable — but the move that pays here is to lift the COLD parts out first (argument validation, fallback and error paths, one-off setup) and leave the kernel whole. Where the kernel itself has to be divided, ask for the extracted parts to be inlined as well, and measure the result rather than assuming the division is free.
BaseTool.GetType (cognitive 20) utils/SkiaSharpGenerator/BaseTool.cs:372— BaseTool.GetType has cognitive complexity 20 (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.
DocumentationStore.GetDocKey (cognitive 20) utils/SkiaSharpGenerator/Generate/DocumentationStore.cs:86— DocumentationStore.GetDocKey has cognitive complexity 20 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
check_generated_files.run_check (cognitive 20) .agents/skills/review-skia-update/scripts/check_generated_files.py:40— check_generated_files.run_check has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (4 pts), loops 2, boolean chains 1, error handling 1 (nesting depth added 7). 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.
skia-sync-publish-handoff.main (cognitive 20) .github/scripts/skia-sync-publish-handoff.py:61— skia-sync-publish-handoff.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 8). 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.
SampleDetailPage.ExportAsync (cognitive 18) samples/Gallery/Maui/SampleDetailPage.xaml.cs:565— SampleDetailPage.ExportAsync has cognitive complexity 18 (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.
SKColorParseBenchmark.OldTryParse (cognitive 18) REDACTED:42— SKColorParseBenchmark.OldTryParse has cognitive complexity 18 (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.
SKColorParseStrategyBenchmark.OldTryParse (cognitive 18) benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseStrategyBenchmark.cs:420— SKColorParseStrategyBenchmark.OldTryParse has cognitive complexity 18 (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.
query-chrome-releases.main (cognitive 18) .agents/skills/security-audit/scripts/query-chrome-releases.py:342— query-chrome-releases.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 5). 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.
SKFont.GetTextPathOnPath (cognitive 17) binding/SkiaSharp/SKFont.cs:1563— SKFont.GetTextPathOnPath has cognitive complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 2 function items inside it that branch. 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.
Verifier.VerifyImplementations (cognitive 17) utils/SkiaSharpGenerator/Verify/Verifier.cs:40— Verifier.VerifyImplementations has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SampleDetailPage.StartAsync (cognitive 16) samples/Gallery/Maui/SampleDetailPage.xaml.cs:140— SampleDetailPage.StartAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
LibraryLoader.LoadLocalLibrary::GetLibraryPath (cognitive 16) binding/Binding.Shared/LibraryLoader.cs:44— LibraryLoader.LoadLocalLibrary::GetLibraryPath has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (5 pts), error handling 1 (nesting depth added 5). 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.
DrawingPage.ApplySwatchColors (cognitive 16) samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:61— DrawingPage.ApplySwatchColors 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.
BaseTool.CleanName (cognitive 16) utils/SkiaSharpGenerator/BaseTool.cs:436— BaseTool.CleanName 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.
ci-status._enrich_failed_runs (cognitive 16) .agents/skills/ci-status/scripts/ci-status.py:431— ci-status._enrich_failed_runs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassTooLong: Generator utils/SkiaSharpGenerator/Generate/Generator.cs— ClassTooLong — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 82 over it, 1.21× 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) utils/SkiaSharpGenerator/Generate/Generator.cs:152— utils/SkiaSharpGenerator/Generate/Generator.cs:152-182 | utils/SkiaSharpGenerator/Generate/Generator.cs:211-238 | utils/SkiaSharpGenerator/Generate/Generator.cs:413-439 | utils/SkiaSharpGenerator/Generate/Generator.cs:665-695 — 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 copies of one member (3 members, 69+ corresponding lines) · ×1
Edited copies of one member (3 members, 69+ corresponding lines) .agents/skills/ci-status/scripts/render-ci-status.py:19— .agents/skills/ci-status/scripts/render-ci-status.py:19-93 | .agents/skills/review-skia-update/scripts/render-skia-review.py:19-87 | .agents/skills/security-audit/scripts/render-security-audit.py:19-91 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 69 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) binding/SkiaSharp/SKColorF.cs:219— binding/SkiaSharp/SKColorF.cs:219-262 | binding/SkiaSharp/SKColorF.cs:270-310 — These two members are one piece of code written twice and then edited apart: 41 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 (62 corresponding lines) · ×1
Edited copy of a member (62 corresponding lines) source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKGLControl.cs:126— source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKGLControl.cs:126-187 | source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:136-199 — These two members are one piece of code written twice and then edited apart: 62 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 (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) .agents/skills/ci-status/scripts/render-ci-status-md.py:46— .agents/skills/ci-status/scripts/render-ci-status-md.py:46-80 | .agents/skills/security-audit/scripts/render-security-audit-md.py:335-359 — 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 (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:30— utils/SkiaSharpGenerator/Generate/GenerateCommand.cs:30-59 | utils/SkiaSharpGenerator/Verify/VerifyCommand.cs:26-52 — These two members are one piece of code written twice and then edited apart: 27 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) · ×1
Edited copy of a member (23 corresponding lines) .agents/skills/review-skia-update/scripts/check_deps.py:70— .agents/skills/review-skia-update/scripts/check_deps.py:70-103 | .agents/skills/update-skia/scripts/update_versions.py:127-149 — 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, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) .agents/skills/review-skia-update/scripts/check_companion.py:188— .agents/skills/review-skia-update/scripts/check_companion.py:188-205 | .agents/skills/review-skia-update/scripts/check_deps.py:231-247 | .agents/skills/review-skia-update/scripts/check_source.py:282-301 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) utils/SkiaSharpGenerator/Cookies/CookieCommand.cs:58— utils/SkiaSharpGenerator/Cookies/CookieCommand.cs:58-81 | utils/SkiaSharpGenerator/Verify/VerifyCommand.cs:55-78 — These two members are one piece of code written twice and then edited apart: 24 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, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1451— source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1451-1475 | source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1478-1502 | source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:1505-1531 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 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 (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:277— source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:277-280 | source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.cs:299-302 — 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.
Duplicated block (52 lines × 2) source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:56— source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:56-107 | source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:57-108 — before extracting anything, compare `source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs` and `source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:56` 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.
Duplicated block (41–42 lines × 2) source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:157— source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:157-198 | source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKGLControl.cs:145-185 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKGLControl.cs:186` calls `SwapBuffers` and `source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:199` 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 (19–20 lines × 3) source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:169— source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:169-187 | source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKSwapChainPanel.cs:85-104 | source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKGLControl.cs:156-174 — 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 `source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:169` 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 (16–18 lines × 2) binding/SkiaSharp/SKColorSpaceStructs.cs:319— binding/SkiaSharp/SKColorSpaceStructs.cs:319-336 | binding/SkiaSharp/SKColorSpaceStructs.cs:376-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3) utils/SkiaSharpGenerator/Generate/Generator.cs:161— utils/SkiaSharpGenerator/Generate/Generator.cs:161-169 | utils/SkiaSharpGenerator/Generate/Generator.cs:218-226 | utils/SkiaSharpGenerator/Generate/Generator.cs:673-681 — 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 `utils/SkiaSharpGenerator/Generate/Generator.cs:161` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `utils/SkiaSharpGenerator/Generate/Generator.cs:682` calls `WriteLine` and `utils/SkiaSharpGenerator/Generate/Generator.cs:171` 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 (8 lines × 4) utils/SkiaSharpGenerator/Generate/Generator.cs:162— utils/SkiaSharpGenerator/Generate/Generator.cs:162-169 | utils/SkiaSharpGenerator/Generate/Generator.cs:219-226 | utils/SkiaSharpGenerator/Generate/Generator.cs:420-427 | utils/SkiaSharpGenerator/Generate/Generator.cs:674-681 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `utils/SkiaSharpGenerator/Generate/Generator.cs:162` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `utils/SkiaSharpGenerator/Generate/Generator.cs:160` calls `Where`, `IsExcludedSymbol`, `GetDisplayName` and `utils/SkiaSharpGenerator/Generate/Generator.cs:419` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (46 lines × 2) source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/SKPaintGLSurfaceEventArgs.cs:18— source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/SKPaintGLSurfaceEventArgs.cs:18-63 | source/SkiaSharp.Views/SkiaSharp.Views.Shared/SKPaintGLSurfaceEventArgs.cs:55-150 — 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 (51 lines × 2) .agents/skills/review-skia-update/scripts/regenerate_bindings.py:121— .agents/skills/review-skia-update/scripts/regenerate_bindings.py:121-171 | .agents/skills/update-skia/scripts/regenerate_bindings.py:123-173 — before extracting anything, compare `.agents/skills/review-skia-update/scripts/regenerate_bindings.py` and `.agents/skills/update-skia/scripts/regenerate_bindings.py` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29–32 lines × 3) .agents/skills/ci-status/scripts/render-ci-status.py:46— .agents/skills/ci-status/scripts/render-ci-status.py:46-74 | .agents/skills/review-skia-update/scripts/render-skia-review.py:40-71 | .agents/skills/security-audit/scripts/render-security-audit.py:46-74 — before extracting anything, compare `.agents/skills/ci-status/scripts/render-ci-status.py` and `.agents/skills/review-skia-update/scripts/render-skia-review.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `.agents/skills/ci-status/scripts/render-ci-status.py:75` calls `get` and `.agents/skills/security-audit/scripts/render-security-audit.py:75` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16–21 lines × 2) .agents/skills/review-skia-update/scripts/check_companion.py:169— .agents/skills/review-skia-update/scripts/check_companion.py:169-184 | .agents/skills/review-skia-update/scripts/check_source.py:212-232 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15–20 lines × 2) .agents/skills/ci-status/scripts/ci-status.py:131— .agents/skills/ci-status/scripts/ci-status.py:131-145 | .agents/skills/ci-status/scripts/ci-status.py:176-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 3) .agents/skills/ci-status/scripts/render-ci-status.py:24— .agents/skills/ci-status/scripts/render-ci-status.py:24-40 | .agents/skills/review-skia-update/scripts/render-skia-review.py:24-40 | .agents/skills/security-audit/scripts/render-security-audit.py:24-40 — before extracting anything, compare `.agents/skills/ci-status/scripts/render-ci-status.py` and `.agents/skills/review-skia-update/scripts/render-skia-review.py` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 6) .agents/skills/ci-status/scripts/render-ci-status-md.py:46— .agents/skills/ci-status/scripts/render-ci-status-md.py:46-58 | .agents/skills/ci-status/scripts/render-ci-status.py:19-32 | .agents/skills/issue-triage/scripts/render-triage-report.py:139-151 | .agents/skills/review-skia-update/scripts/render-skia-review.py:19-32 | .agents/skills/security-audit/scripts/render-security-audit-md.py:335-347 | .agents/skills/security-audit/scripts/render-security-audit.py:19-32 — before extracting anything, compare `.agents/skills/ci-status/scripts/render-ci-status.py` and `.agents/skills/issue-triage/scripts/render-triage-report.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `.agents/skills/issue-triage/scripts/render-triage-report.py:152` calls `with_suffix` and `.agents/skills/ci-status/scripts/render-ci-status-md.py:60` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–13 lines × 4) .agents/skills/ci-status/scripts/render-ci-status.py:50— .agents/skills/ci-status/scripts/render-ci-status.py:50-61 | .agents/skills/issue-triage/scripts/render-triage-report.py:108-120 | .agents/skills/review-skia-update/scripts/render-skia-review.py:44-56 | .agents/skills/security-audit/scripts/render-security-audit.py:50-61 — before extracting anything, compare `.agents/skills/ci-status/scripts/render-ci-status.py` and `.agents/skills/issue-triage/scripts/render-triage-report.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `.agents/skills/ci-status/scripts/render-ci-status.py:61` calls `replace` and `.agents/skills/issue-triage/scripts/render-triage-report.py:120` 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 (11–13 lines × 2) .agents/skills/review-skia-update/scripts/check_deps.py:83— .agents/skills/review-skia-update/scripts/check_deps.py:83-95 | .agents/skills/update-skia/scripts/update_versions.py:131-141 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (4–6 lines × 3) .agents/skills/review-skia-update/scripts/check_companion.py:193— .agents/skills/review-skia-update/scripts/check_companion.py:193-198 | .agents/skills/review-skia-update/scripts/check_deps.py:234-239 | .agents/skills/review-skia-update/scripts/check_source.py:285-288 — 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 `.agents/skills/review-skia-update/scripts/check_companion.py:193` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `.agents/skills/review-skia-update/scripts/check_source.py:288` calls `add_argument`, `parse_args` and `.agents/skills/review-skia-update/scripts/check_companion.py:198` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication· Members sharing a duplicated core (14 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (14 members, 50+ identical tokens) samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:45— samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:45-83 | samples/Basic/BrowserWebAssembly/SkiaSharpSample/Program.cs:17-60 | samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs:43-78 | samples/Basic/Gtk4/SkiaSharpSample/CpuPage.cs:47-85 | samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:44-67 | samples/Basic/Maui/SkiaSharpSample/CpuPage.xaml.cs:32-70 | samples/Basic/Tizen/SkiaSharpSample/CpuPage.cs:60-92 | samples/Basic/WPF/SkiaSharpSample/CpuPage.xaml.cs:33-71 | REDACTED:43-73 | samples/Basic/WinUI/SkiaSharpSample/CpuPage.xaml.cs:32-70 | samples/Basic/WindowsForms/SkiaSharpSample/CpuPage.cs:33-71 | samples/Basic/iOS/SkiaSharpSample/CpuViewController.cs:44-67 | samples/Basic/macOS/SkiaSharpSample/CpuViewController.cs:48-83 | samples/Basic/tvOS/SkiaSharpSample/CpuViewController.cs:45-87 — These 14 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 14 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 14 times.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) samples/Gallery/Shared/Samples/ColorFontSample.cs:97— samples/Gallery/Shared/Samples/ColorFontSample.cs:97-131 | samples/Gallery/Shared/Samples/VariableFontSample.cs:104-143 — These two members are one piece of code written twice and then edited apart: 35 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) samples/Basic/Maui/SkiaSharpSample/GpuPage.xaml.cs:146— samples/Basic/Maui/SkiaSharpSample/GpuPage.xaml.cs:146-171 | samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:122-141 | samples/Basic/WinUI/SkiaSharpSample/GpuPage.xaml.cs:112-131 — 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 (4 members, 22+ corresponding lines) · ×1
Edited copies of one member (4 members, 22+ corresponding lines) samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/GPU.razor:165— samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/GPU.razor:165-192 | samples/Basic/Maui/SkiaSharpSample/GpuPage.xaml.cs:146-171 | samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:151-172 | samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs:148-169 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) samples/Gallery/Shared/Samples/PathEffectsSamplerSample.cs:186— samples/Gallery/Shared/Samples/PathEffectsSamplerSample.cs:186-205 | samples/Gallery/Shared/Samples/TextOnPathSample.cs:121-141 — 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 (4 members, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) samples/Gallery/Shared/Samples/FillPathSample.cs:154— samples/Gallery/Shared/Samples/FillPathSample.cs:154-175 | samples/Gallery/Shared/Samples/FillPathSample.cs:196-213 | samples/Gallery/Shared/Samples/PathBuilderSample.cs:211-231 | samples/Gallery/Shared/Samples/PathBuilderSample.cs:261-280 — These 4 members are one piece of code written 4 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 4 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) samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:220— samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:220-227 | samples/Basic/Gtk4/SkiaSharpSample/DrawingPage.cs:293-300 | samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:102-109 | samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.cs:84-91 — 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 (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:95— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:95-100 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:95-100 | samples/Basic/tvOS/SkiaSharpSample/GpuMetalViewController.cs:76-83 — 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.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:86— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:86-92 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:90-94 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:86-92 — 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.
Duplicated block (77 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:7— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:7-83 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:7-83 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 187 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:7` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:46— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:46-86 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:46-86 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (36–39 lines × 4) samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs:43— samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs:43-78 | samples/Basic/Gtk4/SkiaSharpSample/CpuPage.cs:47-85 | samples/Basic/WPF/SkiaSharpSample/CpuPage.xaml.cs:33-71 | samples/Basic/WindowsForms/SkiaSharpSample/CpuPage.cs:33-71 — before extracting anything, compare `samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs` and `samples/Basic/Gtk4/SkiaSharpSample/CpuPage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23–38 lines × 5) samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:44— samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:44-66 | samples/Basic/Tizen/SkiaSharpSample/CpuPage.cs:60-87 | samples/Basic/iOS/SkiaSharpSample/CpuViewController.cs:44-66 | samples/Basic/macOS/SkiaSharpSample/CpuViewController.cs:48-82 | samples/Basic/tvOS/SkiaSharpSample/CpuViewController.cs:45-82 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs` and `samples/Basic/Tizen/SkiaSharpSample/CpuPage.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.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. 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, `samples/Basic/tvOS/SkiaSharpSample/CpuViewController.cs:86` calls `DrawText` and `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:67` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (35 lines × 2) samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:46— samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:46-80 | samples/Basic/Maui/SkiaSharpSample/CpuPage.xaml.cs:33-67 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/CpuFragment.cs` and `samples/Basic/Maui/SkiaSharpSample/CpuPage.xaml.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22–34 lines × 6) samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs:46— samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs:46-76 | samples/Basic/Gtk4/SkiaSharpSample/CpuPage.cs:50-83 | samples/Basic/WPF/SkiaSharpSample/CpuPage.xaml.cs:36-69 | REDACTED:47-68 | samples/Basic/WinUI/SkiaSharpSample/CpuPage.xaml.cs:35-68 | samples/Basic/WindowsForms/SkiaSharpSample/CpuPage.cs:36-69 — before extracting anything, compare `samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs` and `samples/Basic/Gtk4/SkiaSharpSample/CpuPage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21–32 lines × 7) samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:45— samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:45-76 | samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:44-64 | samples/Basic/Maui/SkiaSharpSample/CpuPage.xaml.cs:32-63 | samples/Basic/Tizen/SkiaSharpSample/CpuPage.cs:60-84 | samples/Basic/iOS/SkiaSharpSample/CpuViewController.cs:44-64 | samples/Basic/macOS/SkiaSharpSample/CpuViewController.cs:48-76 | samples/Basic/tvOS/SkiaSharpSample/CpuViewController.cs:45-76 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/CpuFragment.cs` and `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (29 lines × 4) samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:144— samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:144-172 | samples/Basic/Gtk4/SkiaSharpSample/DrawingPage.cs:232-260 | samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:126-154 | samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.cs:115-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:144` 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.
Duplicated block (24 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:107— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:107-130 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:107-130 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (23 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:7— samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:7-29 | samples/Basic/iOS/SkiaSharpSample/CpuViewController.cs:7-29 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/CpuViewController.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:7` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–22 lines × 3) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:156— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:156-175 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:156-175 | samples/Basic/macOS/SkiaSharpSample/DrawingViewController.cs:181-202 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:156` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:111— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:111-131 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:111-131 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 187 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (11–21 lines × 8) samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:61— samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:61-81 | samples/Basic/BrowserWebAssembly/SkiaSharpSample/Program.cs:43-53 | samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:55-65 | samples/Basic/Maui/SkiaSharpSample/CpuPage.xaml.cs:48-68 | samples/Basic/Tizen/SkiaSharpSample/CpuPage.cs:73-85 | samples/Basic/iOS/SkiaSharpSample/CpuViewController.cs:55-65 | samples/Basic/macOS/SkiaSharpSample/CpuViewController.cs:63-81 | samples/Basic/tvOS/SkiaSharpSample/CpuViewController.cs:61-81 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/CpuFragment.cs` and `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/BrowserWebAssembly/SkiaSharpSample/Program.cs:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/Basic/tvOS/SkiaSharpSample/CpuViewController.cs:86` calls `DrawText` and `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:67` 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 (18 lines × 3) samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:159— samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:159-176 | samples/Basic/Tizen/SkiaSharpSample/DrawingPage.cs:162-179 | samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:159-176 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–20 lines × 13) samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:50— samples/Basic/Android/SkiaSharpSample/CpuFragment.cs:50-69 | samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs:48-65 | samples/Basic/Gtk4/SkiaSharpSample/CpuPage.cs:52-71 | samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:49-58 | samples/Basic/Maui/SkiaSharpSample/CpuPage.xaml.cs:37-56 | samples/Basic/Tizen/SkiaSharpSample/CpuPage.cs:65-77 | samples/Basic/WPF/SkiaSharpSample/CpuPage.xaml.cs:38-57 | REDACTED:49-60 | samples/Basic/WinUI/SkiaSharpSample/CpuPage.xaml.cs:37-56 | samples/Basic/WindowsForms/SkiaSharpSample/CpuPage.cs:38-57 | samples/Basic/iOS/SkiaSharpSample/CpuViewController.cs:49-58 | samples/Basic/macOS/SkiaSharpSample/CpuViewController.cs:53-70 | samples/Basic/tvOS/SkiaSharpSample/CpuViewController.cs:50-69 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/CpuFragment.cs` and `samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 3) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:113— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:113-131 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:121-139 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:113-131 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:113` 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 `e` to `SKPaintMetalSurfaceEventArgs` in one and `SKPaintGLSurfaceEventArgs` 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 (13–17 lines × 2) samples/Gallery/Shared/Samples/CanvasTransformsSample.cs:165— samples/Gallery/Shared/Samples/CanvasTransformsSample.cs:165-181 | samples/Gallery/Shared/Samples/ThreeDSample.cs:224-236 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12–17 lines × 2) samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/GPU.razor:172— samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/GPU.razor:172-188 | samples/Basic/Maui/SkiaSharpSample/GpuPage.xaml.cs:154-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/GPU.razor:172` 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–16 lines × 9) samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:100— samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:100-110 | samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs:99-109 | samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/GPU.razor:168-183 | samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:116-125 | samples/Basic/Maui/SkiaSharpSample/GpuPage.xaml.cs:150-160 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:124-133 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:116-125 | samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:154-164 | samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs:151-161 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs` and `samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `e` to `SKPaintGLSurfaceEventArgs` in one and `SKPaintMetalSurfaceEventArgs` 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, `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:114` calls `Clear` and `samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:100` 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 (9–14 lines × 13) samples/Basic/BrowserWebAssembly/SkiaSharpSample/Program.cs:45— samples/Basic/BrowserWebAssembly/SkiaSharpSample/Program.cs:45-54 | samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs:65-77 | samples/Basic/Gtk4/SkiaSharpSample/CpuPage.cs:71-84 | samples/Basic/MacCatalyst/SkiaSharpSample/CpuViewController.cs:58-66 | samples/Basic/Maui/SkiaSharpSample/CpuPage.xaml.cs:56-69 | samples/Basic/Tizen/SkiaSharpSample/CpuPage.cs:77-86 | samples/Basic/WPF/SkiaSharpSample/CpuPage.xaml.cs:57-70 | REDACTED:60-69 | samples/Basic/WinUI/SkiaSharpSample/CpuPage.xaml.cs:56-69 | samples/Basic/WindowsForms/SkiaSharpSample/CpuPage.cs:57-70 | samples/Basic/iOS/SkiaSharpSample/CpuViewController.cs:58-66 | samples/Basic/macOS/SkiaSharpSample/CpuViewController.cs:70-82 | samples/Basic/tvOS/SkiaSharpSample/CpuViewController.cs:69-82 — before extracting anything, compare `samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs` and `samples/Basic/Gtk4/SkiaSharpSample/CpuPage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/Tizen/SkiaSharpSample/CpuPage.cs:77` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/Basic/BrowserWebAssembly/SkiaSharpSample/Program.cs:57` calls `Snapshot`, `Encode`, `ToBase64String` and `samples/Basic/Gtk3/SkiaSharpSample/CpuPage.cs:78` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 5) samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:153— samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:153-159 | samples/Basic/Gtk4/SkiaSharpSample/DrawingPage.cs:241-247 | samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:124-130 | samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:135-141 | samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.cs:124-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (12–14 lines × 4) samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:110— samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:110-121 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:118-129 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:110-121 | samples/Basic/tvOS/SkiaSharpSample/GpuGLViewController.cs:102-115 — before extracting anything, compare `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs` and `samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `e` to `SKPaintMetalSurfaceEventArgs` in one and `SKPaintGLSurfaceEventArgs` 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, `samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:114` calls `Export`, `RenderFrame`, `Display` and `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:107` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 6) samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:142— samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:142-153 | samples/Basic/Gtk3/SkiaSharpSample/DrawingPage.cs:146-157 | samples/Basic/Gtk4/SkiaSharpSample/DrawingPage.cs:234-245 | samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:117-128 | samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.cs:128-139 | samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.cs:117-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/Basic/Android/SkiaSharpSample/DrawingFragment.cs:140` calls `Scale` and `samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:115` 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 (7–9 lines × 11) samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:102— samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:102-108 | samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs:101-107 | samples/Basic/BlazorWebAssembly/SkiaSharpSample/Pages/GPU.razor:171-179 | samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:117-123 | samples/Basic/Maui/SkiaSharpSample/GpuPage.xaml.cs:152-158 | samples/Basic/WPF/SkiaSharpSample/GpuPage.xaml.cs:127-133 | samples/Basic/WinUI/SkiaSharpSample/GpuPage.xaml.cs:117-123 | samples/Basic/iOS/SkiaSharpSample/GpuGLViewController.cs:125-131 | samples/Basic/iOS/SkiaSharpSample/GpuMetalViewController.cs:117-123 | samples/Basic/macOS/SkiaSharpSample/GpuGLViewController.cs:156-162 | samples/Basic/macOS/SkiaSharpSample/GpuMetalViewController.cs:153-159 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs` and `samples/Basic/Android/SkiaSharpSample/GpuTextureFragment.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 70 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/Basic/MacCatalyst/SkiaSharpSample/GpuMetalViewController.cs:114` calls `Clear` and `samples/Basic/Android/SkiaSharpSample/GpuSurfaceFragment.cs:100` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 5) samples/Gallery/Shared/Samples/VectorArtSample.cs:98— samples/Gallery/Shared/Samples/VectorArtSample.cs:98-103 | samples/Gallery/Shared/Samples/VectorArtSample.cs:104-109 | samples/Gallery/Shared/Samples/VectorArtSample.cs:121-126 | samples/Gallery/Shared/Samples/VectorArtSample.cs:128-133 | samples/Gallery/Shared/Samples/VectorArtSample.cs:140-145 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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, `samples/Gallery/Shared/Samples/VectorArtSample.cs:126` calls `CubicTo` and `samples/Gallery/Shared/Samples/VectorArtSample.cs:133` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 8) samples/Basic/Android/SkiaSharpSample/FpsCounter.cs:29— samples/Basic/Android/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/BlazorWebAssembly/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/MacCatalyst/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/Maui/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/Tizen/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/iOS/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/macOS/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/tvOS/SkiaSharpSample/FpsCounter.cs:29-49 — before extracting anything, compare `samples/Basic/Android/SkiaSharpSample/FpsCounter.cs` and `samples/Basic/BlazorWebAssembly/SkiaSharpSample/FpsCounter.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (42 lines × 2) samples/Basic/Console/SkiaSharpSample/Program.cs:8— samples/Basic/Console/SkiaSharpSample/Program.cs:8-49 | samples/Basic/DockerConsole/SkiaSharpSample/Program.cs:8-52 — before extracting anything, compare `samples/Basic/Console/SkiaSharpSample/Program.cs` and `samples/Basic/DockerConsole/SkiaSharpSample/Program.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 3) samples/Basic/WPF/SkiaSharpSample/FpsCounter.cs:29— samples/Basic/WPF/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/WinUI/SkiaSharpSample/FpsCounter.cs:29-49 | samples/Basic/WindowsForms/SkiaSharpSample/FpsCounter.cs:29-49 — before extracting anything, compare `samples/Basic/WPF/SkiaSharpSample/FpsCounter.cs` and `samples/Basic/WinUI/SkiaSharpSample/FpsCounter.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19–20 lines × 2) scripts/infra/docs/release-notes-data.py:669— scripts/infra/docs/release-notes-data.py:669-688 | scripts/infra/docs/release-notes-data.py:787-805 — both copies are in the same file, so extract the 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 `scripts/infra/docs/release-notes-data.py:669` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7–8 lines × 2) scripts/infra/caching/repo-deps.py:58— scripts/infra/caching/repo-deps.py:58-65 | scripts/infra/caching/repo-deps.py:72-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Off the main sequence: SkiaSharp(netstandard2.0) binding/SkiaSharp/SkiaSharp.csproj:1— SkiaSharp(netstandard2.0): abstractness 0.11, instability 0.09, distance 0.81 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
Third-party script without Subresource Integrity .agents/skills/issue-triage/scripts/viewer.html:112— `https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 4 such include(s) across the repository's markup.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×1
Untrusted text written into markup unescaped samples/Basic/BrowserWebAssembly/SkiaSharpSample/wwwroot/main.js:25— `e.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
redundant comment binding/Binding.Shared/DelegateProxies.shared.cs:143— "multi-value delegate with user data" repeats the code it sits on: 4 of its 5 words (multi, delegate, user, data) are already in `[MethodImpl (MethodImplOptions.AggressiveInlining)]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKBitmap.cs:112— "TryAllocPixels" repeats the code it sits on: 3 of its 3 words (try, alloc, pixels) are already in `public bool TryAllocPixels (SKImageInfo info)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKBitmap.cs:993— "NotifyPixelsChanged" repeats the code it sits on: 3 of its 3 words (notify, pixels, changed) are already in `public void NotifyPixelsChanged ()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKCanvas.cs:891— 5 comments in this file only repeat the code they sit on (lines 891, 1477, 1581, 1857, 2190), for example "DrawRoundRect". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKColorSpace.cs:115— "CreateSrgbLinear" repeats the code it sits on: 3 of its 3 words (create, srgb, linear) are already in `public static SKColorSpace CreateSrgbLinear () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKColorSpace.cs:204— "GetNumericalTransferFunction" repeats the code it sits on: 4 of its 4 words (get, numerical, transfer, function) are already in `public SKColorSpaceTransferFn GetNumericalTransferFunction () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKColorSpace.cs:238— "ToColorSpaceXyz" repeats the code it sits on: 3 of its 3 words (color, space, xyz) are already in `public bool ToColorSpaceXyz (out SKColorSpaceXyz toXyzD50)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKColorSpaceStructs.cs:490— "ToColorSpaceXyz" repeats the code it sits on: 3 of its 3 words (color, space, xyz) are already in `public bool ToColorSpaceXyz (out SKColorSpaceXyz toXyzD50)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKFont.cs:633— 13 comments in this file only repeat the code they sit on (lines 633, 777, 893, 924, 1040, 1071, 1263, 1310, 1327, 1383, 1441, 1461, 1529), for example "MeasureText (glyphs)". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKImage.cs:1169— "RequestReadPixels" repeats the code it sits on: 3 of its 3 words (request, read, pixels) are already in `public void RequestReadPixels (SKImageInfo info, SKRectI srcRect, Action<SKImageReadPixelsResult> callback) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKImage.cs:1361— "ApplyImageFilter" repeats the code it sits on: 3 of its 3 words (apply, image, filter) are already in `public SKImage ApplyImageFilter (SKImageFilter filter, SKRectI subset, SKRectI clipBounds, out SKRectI outSubset, out SK …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKImageFilter.cs:136— 13 comments in this file only repeat the code they sit on (lines 136, 218, 262, 307, 360, 402, 444, 495, 540, 585, 639, 911, 948), for example "CreateColorFilter". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKMatrix44.cs:157— "CreateRotation*Degrees" repeats the code it sits on: 3 of its 3 words (create, rotation, degrees) are already in `public static SKMatrix44 CreateRotationDegrees (float x, float y, float z, float degrees) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKPMColor.cs:81— "UnPreMultiply" repeats the code it sits on: 3 of its 3 words (un, pre, multiply) are already in `public static SKColor UnPreMultiply (SKPMColor pmcolor)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKPaint.cs:982— 10 comments in this file only repeat the code they sit on (lines 982, 1112, 1314, 1492, 1531, 1570, 1678, 1766, 1783, 1865), for example "GetTextPath". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKPathMeasure.cs:99— "GetPositionAndTangent" repeats the code it sits on: 3 of its 3 words (get, position, tangent) are already in `public bool GetPositionAndTangent (float distance, out SKPoint position, out SKPoint tangent)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKRegion.cs:108— "GetBoundaryPath" repeats the code it sits on: 3 of its 3 words (get, boundary, path) are already in `public SKPath GetBoundaryPath ()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKShader.cs:530— 8 comments in this file only repeat the code they sit on (lines 530, 649, 764, 942, 1069, 1103, 1202, 1219), for example "CreateLinearGradient". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKSurface.cs:220— "GPU BACKEND RENDER TARGET surface" repeats the code it sits on: 4 of its 5 words (backend, render, target, surface) are already in `public static SKSurface Create (GRContext context, GRBackendRenderTarget renderTarget, SKColorType colorType) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKSurface.cs:1090— "RequestReadPixels" repeats the code it sits on: 3 of its 3 words (request, read, pixels) are already in `public void RequestReadPixels (SKImageInfo info, SKRectI srcRect, Action<SKImageReadPixelsResult> callback) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKTextBlob.cs:254— 9 comments in this file only repeat the code they sit on (lines 254, 319, 514, 529, 543, 557, 700, 777, 849), for example "CreateRotationScale". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKTypeface.cs:338— "GetTableSize" repeats the code it sits on: 3 of its 3 words (get, table, size) are already in `public int GetTableSize (UInt32 tag)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKTypeface.cs:351— "GetTableData" repeats the code it sits on: 3 of its 3 words (get, table, data) are already in `public byte[] GetTableData (UInt32 tag)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/SKTypeface.cs:603— "GetKerningPairAdjustments" repeats the code it sits on: 4 of its 4 words (get, kerning, pair, adjustments) are already in `public bool HasGetKerningPairAdjustments {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment binding/SkiaSharp/Util.cs:135— "GetCharacterByteSize" repeats the code it sits on: 4 of its 4 words (get, character, byte, size) are already in `internal static int GetCharacterByteSize (this SKTextEncoding encoding) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate REDACTED:70— `!byte.TryParse(hexSpan.Slice(len - 3, 1), NumberStyles.HexNumber, CultureInfo.InvariantCulture, out var r) || !byte.TryParse(hexSpan.Slice(l…` appears character-identically in 2 files — REDACTED, benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseStrategyBenchmark.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 source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs:173— `!double.IsNaN(value) && !double.IsInfinity(value) && value > 0` appears character-identically in 5 files — source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKCanvasView.razor.cs, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/SKGLView.razor.cs, source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKElement.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 samples/Basic/iOS/SkiaSharpSample/SceneDelegate.cs:12— `AppDelegate.DefaultPage != SamplePage.Cpu && Window?.RootViewController is UITabBarController tabs` appears character-identically in 2 files — samples/Basic/MacCatalyst/SkiaSharpSample/SceneDelegate.cs, samples/Basic/iOS/SkiaSharpSample/SceneDelegate.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 source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Android.cs:90— `VirtualView?.IgnorePixelScaling == true && Context != null` appears character-identically in 2 files — source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Android.cs, source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKGLView/SKGLViewHandler.Android.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 samples/Basic/Console/SkiaSharpSample/Program.cs:9— `args[i] is "--output" or "-o" && i + 1 < args.Length` appears character-identically in 2 files — samples/Basic/Console/SkiaSharpSample/Program.cs, samples/Basic/DockerConsole/SkiaSharpSample/Program.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 source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:291— `bitmap == null && info.Width > 0 && info.Height > 0` appears character-identically in 2 files — source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs, source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.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 source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:288— `bitmap?.PixelWidth != info.Width || bitmap?.PixelHeight != info.Height` appears character-identically in 2 files — source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs, source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.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 samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:46— `currentColor == SKColors.Black && IsDarkMode` appears character-identically in 2 files — samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs, samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.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 samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs:48— `currentColor == SKColors.White && !IsDarkMode` appears character-identically in 2 files — samples/Basic/Maui/SkiaSharpSample/DrawingPage.xaml.cs, samples/Basic/WinUI/SkiaSharpSample/DrawingPage.xaml.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 source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:162— `d is SKXamlCanvas canvas && e.NewValue is Visibility visibility` appears character-identically in 2 files — source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs, source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.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 benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseSpanBenchmark.cs:108— `end > start && char.IsWhiteSpace(hexString[end - 1])` appears character-identically in 2 files — benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseSpanBenchmark.cs, benchmarks/SkiaSharp.Benchmarks/Benchmarks/SKColorParseStrategyBenchmark.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 binding/SkiaSharp/HandleDictionary.cs:158— `handle == IntPtr.Zero || instance == null` appears character-identically in 2 files — binding/SkiaSharp/HandleDictionary.cs, binding/SkiaSharp/SKObject.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 samples/Basic/iOS/SkiaSharpSample/DrawingViewController.cs:60— `i < swatches.Length && i < colorPalette.Length` appears character-identically in 2 files — samples/Basic/MacCatalyst/SkiaSharpSample/DrawingViewController.cs, samples/Basic/iOS/SkiaSharpSample/DrawingViewController.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 source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs:161— `imgInfo.Width != 0 && imgInfo.Height != 0` appears character-identically in 2 files — source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs, source/SkiaSharp.Views/SkiaSharp.Views.Gtk4/SKDrawingArea.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 REDACTED:165— `!ctx && contextAttributes.majorVersion > 1` appears character-identically in 2 files — REDACTED, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/wwwroot/SKHtmlCanvas.ts. 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 REDACTED:181— `GL.currentContext && GL.currentContext.GLctx || GLctx` appears character-identically in 2 files — REDACTED, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/wwwroot/SKHtmlCanvas.ts. 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 REDACTED:15— `element || document.querySelector('[' + elementId + ']')` appears character-identically in 4 files — REDACTED, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/wwwroot/SKHtmlCanvas.ts, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/wwwroot/SizeWatcher.js, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/wwwroot/SizeWatcher.ts. 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 REDACTED:88— `renderLoop !== undefined && this.renderLoopEnabled !== renderLoop` appears character-identically in 2 files — REDACTED, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/wwwroot/SKHtmlCanvas.ts. 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 REDACTED:130— `this.glInfo || !pData || width <= 0 || width <= 0` appears character-identically in 2 files — REDACTED, source/SkiaSharp.Views/SkiaSharp.Views.Blazor/wwwroot/SKHtmlCanvas.ts. 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 samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.cs:191— `key?.GetValue("AppsUseLightTheme") is int i && i == 0` appears character-identically in 2 files — samples/Basic/WPF/SkiaSharpSample/DrawingPage.xaml.cs, samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.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 source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs:157— `pix == null || pix.Width != imgInfo.Width || pix.Height != imgInfo.Height` appears character-identically in 2 files — source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs, source/SkiaSharp.Views/SkiaSharp.Views.Gtk4/SKDrawingArea.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 .agents/skills/review-skia-update/scripts/check_deps.py:33— `isinstance(node, ast.BinOp) and isinstance(node.op, ast.Add)` appears character-identically in 2 files — .agents/skills/review-skia-update/scripts/check_deps.py, .agents/skills/update-skia/scripts/update_versions.py. 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 .agents/skills/review-skia-update/scripts/check_deps.py:29— `isinstance(node.func, ast.Name) and node.func.id == "Var" and len(node.args) == 1` appears character-identically in 2 files — .agents/skills/review-skia-update/scripts/check_deps.py, .agents/skills/update-skia/scripts/update_versions.py. 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 .agents/skills/review-skia-update/scripts/check_deps.py:53— `isinstance(target, ast.Name) and target.id == name` appears character-identically in 2 files — .agents/skills/review-skia-update/scripts/check_deps.py, .agents/skills/update-skia/scripts/update_versions.py. 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 .agents/skills/review-skia-update/scripts/regenerate_bindings.py:73— `line.startswith("+") and not line.startswith("+++") and "internal static" in line` appears character-identically in 2 files — .agents/skills/review-skia-update/scripts/regenerate_bindings.py, .agents/skills/update-skia/scripts/regenerate_bindings.py. 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.
Shell project: HarfBuzzSharp.NativeAssets.macOS(netstandard2.0) binding/HarfBuzzSharp.NativeAssets.macOS/HarfBuzzSharp.NativeAssets.macOS.csproj— `HarfBuzzSharp.NativeAssets.macOS(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.macOS(netstandard2.0) binding/SkiaSharp.NativeAssets.macOS/SkiaSharp.NativeAssets.macOS.csproj— `SkiaSharp.NativeAssets.macOS(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.WebAssembly(netstandard2.0) binding/SkiaSharp.NativeAssets.WebAssembly/SkiaSharp.NativeAssets.WebAssembly.csproj— `SkiaSharp.NativeAssets.WebAssembly(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.Win32(netstandard2.0) binding/SkiaSharp.NativeAssets.Win32/SkiaSharp.NativeAssets.Win32.csproj— `SkiaSharp.NativeAssets.Win32(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.Android(net9.0-android35.0) binding/SkiaSharp.NativeAssets.Android/SkiaSharp.NativeAssets.Android.csproj— `SkiaSharp.NativeAssets.Android(net9.0-android35.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HarfBuzzSharp.NativeAssets.Win32(netstandard2.0) binding/HarfBuzzSharp.NativeAssets.Win32/HarfBuzzSharp.NativeAssets.Win32.csproj— `HarfBuzzSharp.NativeAssets.Win32(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HarfBuzzSharp.NativeAssets.Android(net9.0-android35.0) binding/HarfBuzzSharp.NativeAssets.Android/HarfBuzzSharp.NativeAssets.Android.csproj— `HarfBuzzSharp.NativeAssets.Android(net9.0-android35.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HarfBuzzSharp.NativeAssets.iOS(net9.0-ios18.0) binding/HarfBuzzSharp.NativeAssets.iOS/HarfBuzzSharp.NativeAssets.iOS.csproj— `HarfBuzzSharp.NativeAssets.iOS(net9.0-ios18.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HarfBuzzSharp.NativeAssets.Linux(netstandard2.0) binding/HarfBuzzSharp.NativeAssets.Linux/HarfBuzzSharp.NativeAssets.Linux.csproj— `HarfBuzzSharp.NativeAssets.Linux(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HarfBuzzSharp.NativeAssets.MacCatalyst(net9.0-maccatalyst18.0) binding/HarfBuzzSharp.NativeAssets.MacCatalyst/HarfBuzzSharp.NativeAssets.MacCatalyst.csproj— `HarfBuzzSharp.NativeAssets.MacCatalyst(net9.0-maccatalyst18.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HarfBuzzSharp.NativeAssets.Tizen binding/HarfBuzzSharp.NativeAssets.Tizen/HarfBuzzSharp.NativeAssets.Tizen.csproj— `HarfBuzzSharp.NativeAssets.Tizen` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HarfBuzzSharp.NativeAssets.tvOS(net9.0-tvos18.0) binding/HarfBuzzSharp.NativeAssets.tvOS/HarfBuzzSharp.NativeAssets.tvOS.csproj— `HarfBuzzSharp.NativeAssets.tvOS(net9.0-tvos18.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: HarfBuzzSharp.NativeAssets.WebAssembly(netstandard2.0) binding/HarfBuzzSharp.NativeAssets.WebAssembly/HarfBuzzSharp.NativeAssets.WebAssembly.csproj— `HarfBuzzSharp.NativeAssets.WebAssembly(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.iOS(net9.0-ios18.0) binding/SkiaSharp.NativeAssets.iOS/SkiaSharp.NativeAssets.iOS.csproj— `SkiaSharp.NativeAssets.iOS(net9.0-ios18.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.Linux.NoDependencies(netstandard2.0) binding/SkiaSharp.NativeAssets.Linux.NoDependencies/SkiaSharp.NativeAssets.Linux.NoDependencies.csproj— `SkiaSharp.NativeAssets.Linux.NoDependencies(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.Linux(netstandard2.0) binding/SkiaSharp.NativeAssets.Linux/SkiaSharp.NativeAssets.Linux.csproj— `SkiaSharp.NativeAssets.Linux(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.MacCatalyst(net9.0-maccatalyst18.0) binding/SkiaSharp.NativeAssets.MacCatalyst/SkiaSharp.NativeAssets.MacCatalyst.csproj— `SkiaSharp.NativeAssets.MacCatalyst(net9.0-maccatalyst18.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.NanoServer(netstandard2.0) binding/SkiaSharp.NativeAssets.NanoServer/SkiaSharp.NativeAssets.NanoServer.csproj— `SkiaSharp.NativeAssets.NanoServer(netstandard2.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.Tizen binding/SkiaSharp.NativeAssets.Tizen/SkiaSharp.NativeAssets.Tizen.csproj— `SkiaSharp.NativeAssets.Tizen` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.tvOS(net9.0-tvos18.0) binding/SkiaSharp.NativeAssets.tvOS/SkiaSharp.NativeAssets.tvOS.csproj— `SkiaSharp.NativeAssets.tvOS(net9.0-tvos18.0)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: SkiaSharp.NativeAssets.WinUI binding/SkiaSharp.NativeAssets.WinUI/SkiaSharp.NativeAssets.WinUI.csproj— `SkiaSharp.NativeAssets.WinUI` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Silent fallback default on parse failure .agents/skills/ci-status/scripts/ci-status.py:253— `get_github_workflow_runs` returns `[]` when `(json.JSONDecodeError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure .agents/skills/ci-status/scripts/ci-status.py:409— `get_failed_job_details` returns `[]` when `(json.JSONDecodeError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-data.py:641— `load_author_cache` returns `{}` when `(OSError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-data.py:682— `_graphql_pr_authors` returns `{}` when `(ValueError, KeyError, TypeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-data.py:757— `load_fixed_issues_cache` returns `{}` when `(OSError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-data.py:799— `_graphql_pr_fixed_issues` returns `{}` when `(ValueError, KeyError, TypeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-data.py:874— `load_first_time_contributors_cache` returns `{}` when `(OSError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-data.py:921— `_graphql_earliest_pull_requests` returns `{}` when `(ValueError, KeyError, TypeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-data.py:2472— `_data_json_unchanged` returns `False` when `(ValueError, OSError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-data.py:2495— `_website_content_unchanged` returns `False` when `(ValueError, OSError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure scripts/infra/docs/release-notes-render.py:892— `load_index_json` returns `{}` when `(ValueError, OSError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
P10 · Library API & versioning· Public type used only inside its own library · ×6
Public type used only inside its own library source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/Resource.cs:5— `SkiaSharp.Views.Android.Resource` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/Resource.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net10.0-android36.0)`, `SkiaSharpSample`, `SkiaSharpSample`) 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 source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/Resource.cs:5— `SkiaSharp.Views.Android.Resource` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/Resource.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net9.0-android35.0)`) 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 source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:12— `SkiaSharp.Views.Android.SKGLSurfaceViewRenderer` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net10.0-android36.0)`, `SkiaSharpSample`, `SkiaSharpSample`) 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 source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:12— `SkiaSharp.Views.Android.SKGLSurfaceViewRenderer` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLSurfaceViewRenderer.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net9.0-android35.0)`) 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 source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:12— `SkiaSharp.Views.Android.SKGLTextureViewRenderer` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net10.0-android36.0)`, `SkiaSharpSample`, `SkiaSharpSample`) 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 source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:12— `SkiaSharp.Views.Android.SKGLTextureViewRenderer` (source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/SKGLTextureViewRenderer.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `SkiaSharp.Views.Maui.Core(net9.0-android35.0)`) 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.
Silent fallback default in catch binding/Binding.Shared/PlatformConfiguration.cs:112— `IsGlibcImplementation` swallows `TypeLoadException` 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 binding/SkiaSharp/DelegateProxies.cs:171— `SKGraphiteImageProviderProxyImplementation` swallows every exception into `return IntPtr.Zero;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch samples/Basic/WindowsForms/SkiaSharpSample/DrawingPage.cs:193— `IsDarkMode` 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 samples/Basic/WPF/SkiaSharpSample/DrawingPage.xaml.cs:260— `IsDarkMode` 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 .agents/skills/ci-status/scripts/ci-status.py:142— `get_build_changes` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Orphaned file binding/HarfBuzzSharp/FontFunctions.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file binding/SkiaSharp/PlatformLock.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file binding/SkiaSharp/DelegateProxies.stream.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Commented-out code source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:140— 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 source/SkiaSharp.Views/SkiaSharp.Views.WinUI/UWPExtensions.cs:143— 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 source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:230— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
README/code drift documentation/dev/building.md:227— documentation/dev/building.md names .NET 9, but the projects target .NET 0, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift documentation/dev/building.md:333— documentation/dev/building.md names .NET 11, but the projects target .NET 0, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Thin analysable surface across projects: SkiaSharp.Views.WinUI.Native.Projection native/winui/SkiaSharp.Views.WinUI.Native/SkiaSharp.Views.WinUI.Native.Projection/SkiaSharp.Views.WinUI.Native.Projection.csproj— 1 project(s) carry only a thin slice of real code; `SkiaSharp.Views.WinUI.Native.Projection` has 0 significant line(s). The mean analysable-surface weight is 97 %; this project lowers Solution Shape by about 0.24 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
No ADRs found utils/SkiaSharpGenerator/SkiaSharpGenerator.csproj:4— 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 `utils/SkiaSharpGenerator/SkiaSharpGenerator.csproj` makes this repository a deployable product (line 4).
D21 · Naming Consistency· `OpenGL` spells `GL` where 18 names in the project spell it `Gl` · ×1
`OpenGL` spells `GL` where 18 names in the project spell it `Gl` binding/SkiaSharp/EnumMappings.cs:15— 18 of 19 names in project SkiaSharp spell the token `Gl` (18 of 19; unit: names in project SkiaSharp containing `Gl`). Peers: SkiaSharp.GRGlGetProcedureAddressDelegate (binding/SkiaSharp/DelegateProxies.cs:46); GRBackendRenderTarget.CreateGl (binding/SkiaSharp/GRBackendRenderTarget.cs:107); GRBackendRenderTarget.GetGlFramebufferInfo (binding/SkiaSharp/GRBackendRenderTarget.cs:218); GRBackendRenderTarget.GetGlFramebufferInfo (binding/SkiaSharp/GRBackendRenderTarget.cs:225); GRBackendTexture.CreateGl (binding/SkiaSharp/GRBackendTexture.cs:80). Rename to `OpenGl`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion binding/SkiaSharp/SkiaSharp.csproj:1— `SkiaSharp(netstandard2.0)` overshoots its size bounds (34939 LoC, 155 public types across 2 namespaces). 1 of 72 project(s) overshoot their size bounds, lowering Project Cohesion to 9.7/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
Pass-through layer binding/SkiaSharp/PlatformLock.cs:82— ReadWriteLock: all 6 public methods forward their arguments unchanged to _lock and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _lock directly, or give the layer a job.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 4 of 192 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 192 of the 262 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: binding/HarfBuzzSharp/FontFunctions.cs, source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKGLElement.cs, binding/SkiaSharp/PlatformLock.cs, binding/SkiaSharp/DelegateProxies.stream.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 11 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
Logging is not universal — Only 8/18 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 18, 10 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No dependency-update automation benchmarks/SkiaSharp.Benchmarks.Tracking.Source/SkiaSharp.Benchmarks.Tracking.Source.csproj:36— `benchmarks/SkiaSharp.Benchmarks.Tracking.Source/SkiaSharp.Benchmarks.Tracking.Source.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 5/21 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Nullable reference types not enabled everywhere — 25/68 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.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.4 `!` suppressions per 1k syntax nodes — 87 suppression(s) across the 225971 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
doc comments repeat the names binding/HarfBuzzSharp/DelegateProxies.font.cs:8— 6 of 389 documented parameters and 5 of 520 summaries in `HarfBuzzSharp(netstandard2.0)` only repeat the member or parameter name (e.g. "The font." for `font`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names binding/SkiaSharp/Definitions.cs:443— 67 of 4416 documented parameters and 74 of 2959 summaries in `SkiaSharp(netstandard2.0)` only repeat the member or parameter name (e.g. "Returns the hash code for this instance." for `GetHashCode`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Direct3D/SkiaSharp.Direct3D.Vortice/GRVorticeD3DTextureResourceInfo.cs:36— 0 of 0 documented parameters and 1 of 10 summaries in `SkiaSharp.Direct3D.Vortice` only repeat the member or parameter name (e.g. "Gets or sets the current state of the resource." for `ResourceState`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views/SkiaSharp.Views/Platform/Android/GLTextureView.cs:92— 7 of 132 documented parameters and 9 of 126 summaries in `SkiaSharp.Views(net10.0-android36.0)` only repeat the member or parameter name (e.g. "Gets or sets the current debug flags." for `DebugFlags`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views/SkiaSharp.Views.Gtk3/SKDrawingArea.cs:22— 0 of 20 documented parameters and 1 of 23 summaries in `SkiaSharp.Views.Gtk3(netstandard2.0)` only repeat the member or parameter name (e.g. "Gets the current canvas size." for `CanvasSize`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views/SkiaSharp.Views.Gtk4/SKDrawingArea.cs:26— 0 of 16 documented parameters and 1 of 31 summaries in `SkiaSharp.Views.Gtk4` only repeat the member or parameter name (e.g. "Gets the current canvas size." for `CanvasSize`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Ref.cs:14— 7 of 95 documented parameters and 0 of 122 summaries in `SkiaSharp.Views.Maui.Core(net10.0)` only repeat the member or parameter name (e.g. "The handler instance." for `handler`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views.Maui/SkiaSharp.Views.Maui.Core/Handlers/SKCanvasView/SKCanvasViewHandler.Android.cs:43— 7 of 23 documented parameters and 0 of 14 summaries in `SkiaSharp.Views.Maui.Core(net10.0-android36.0)` only repeat the member or parameter name (e.g. "The handler instance." for `handler`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views.Uno/SkiaSharp.Views.Uno.WinUI/SKXamlCanvas.cs:69— 0 of 19 documented parameters and 1 of 34 summaries in `SkiaSharp.Views.Uno.WinUI(net10.0)` only repeat the member or parameter name (e.g. "Gets the current canvas size." for `CanvasSize`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views/SkiaSharp.Views.WPF/SKElement.cs:34— 0 of 24 documented parameters and 1 of 34 summaries in `SkiaSharp.Views.WPF(net462)` only repeat the member or parameter name (e.g. "Gets the current canvas size." for `CanvasSize`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views/SkiaSharp.Views.WinUI/SKXamlCanvas.cs:74— 0 of 4 documented parameters and 1 of 24 summaries in `SkiaSharp.Views.WinUI` only repeat the member or parameter name (e.g. "Gets the current canvas size." for `CanvasSize`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names source/SkiaSharp.Views/SkiaSharp.Views.WindowsForms/SKControl.cs:25— 0 of 34 documented parameters and 2 of 39 summaries in `SkiaSharp.Views.WindowsForms(net462)` only repeat the member or parameter name (e.g. "Gets the current canvas size." for `CanvasSize`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
Skipped (documented): DownloadedStream tests/Tests/SkiaSharp/SKCodecTest.cs:476— Skipped with a documented reason — a deferral, not lazy debt: This keeps breaking CI for some reason. It also fetches `http://www.gstatic.com/webp/gallery/2.webp` over the network, so re-enabling it makes this suite depend on www.gstatic.com being reachable and unchanged — frequently the untold reason a test like this was switched off in the first place.
Skipped (documented): DataDisposedReturnsInvalidStream tests/Tests/SkiaSharp/SKDataTest.cs:234— Skipped with a documented reason — a deferral, not lazy debt: Doesn't work as it relies on memory being overwritten by an external process.
Skipped (documented): DrawTransparentImageWithHighFilterQualityWithUnpremul tests/Tests/SkiaSharp/SKPaintTest.cs:138— Skipped with a documented reason — a deferral, not lazy debt: Known to fail, see: https://github.com/mono/SkiaSharp/issues/282
Off the main sequence: SkiaSharp.Views.Desktop.Common(netstandard2.0) source/SkiaSharp.Views/SkiaSharp.Views.Desktop.Common/SkiaSharp.Views.Desktop.Common.csproj:1— SkiaSharp.Views.Desktop.Common(netstandard2.0): abstractness 0.00, instability 0.20, distance 0.80 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 20 file(s) — `binding/Binding.Shared/DelegateProxies.shared.cs`, `binding/Binding.Shared/HashCode.cs`, `binding/Binding.Shared/LibraryLoader.cs`, `binding/Binding.Shared/PlatformConfiguration.cs`, `source/SkiaSharp.Views/SkiaSharp.Views.Shared/SKPaintGLSurfaceEventArgs.cs`, … (+15 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e7ba-075e-7457-876f-dafcb672f53c · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 1 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 142 · Warnings: 632 · Recommendations: 207 · Info: 16 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 04:18 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.