Public report — UniGetUI, published 5 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
247findings with an exact file:lineof 283 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
51/97dimensions across the health lenses60119 LoC · 86 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
Devolutions/UniGetUI carries serious risk (49%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.
It is strongest in Architecture (94%) — the structure is clean and changes stay contained.
The area that most needs attention is Security (35%) — exposure to security and compliance incidents is elevated. Readiness (57%) is the next concern — operating, monitoring and recovering the system safely is harder.
Leadership focus, highest impact first: Encrypt sensitive data at rest (ASP.NET Core Data Protection /… (Data Protection); Name the access rules (Access Controls); security response headers (Content-Security-Policy (Web-Security Posture).
For scale: Medium (~60,119 production lines); rebuilding it from scratch would take roughly ~1.2 person-years (~1–3 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (94%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
This codebase represents roughly ~1.2 person-years of build effort (about ~€180,000 to rebuild). Its weakest lens is Security at 35% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.1) — service/app, transaction-script/CRUD, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Name the access rules — give each one a named predicate/policy object your guards consult, so the rule set can be reviewed and unit-tested independently of the call sites that enforce it.
Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~1.2 person-years to rebuild), and its weakest lens is Security at 35%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Security first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture — module dependency matrix
92 modules, 321 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
21
High / Critical
A02:2021 — Cryptographic Failures
5
High / Critical
Roadmap
Begin by encrypting sensitive data at rest and managing keys in a vault, ensuring that any infrastructure-managed encryption is properly delegated. Next, formalize access controls by defining named policies and predicates that can be independently reviewed and tested. Then, harden the web security posture by implementing essential security headers for defense in depth. Finally, address the 21 high-priority static analysis findings and resolve the four secret exposure issues in the repository history.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Name the access rules — give each one a named predicate/policy object your guards consult, so the rule set can be reviewed and unit-tested independently of the call sites that enforce it.
Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 48 of 51 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 51 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, 247 of 283 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
The LLM boundary
LLM-set scores this run (4): D20, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WinGetPkgOperationHelper._getOperationParameters at 48. A further 7 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 Settings.ResolveKey at 113 — they are counted neither in the figure above nor in this dimension's score.
+ 31 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 WinGetPkgOperationHelper._getOperationParameters (cyclomatic 48) finding(s) in Cyclomatic Complexity — start with WinGetPkgOperationHelper.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 MainWindow.OnWindowsWndProc (cyclomatic 39) finding(s) in Cyclomatic Complexity — start with MainWindow.axaml.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Bun.ParseBunOutdatedTable (cyclomatic 34) finding(s) in Cyclomatic Complexity — start with Bun.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 61 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 MainWindow.OnWindowsWndProc (cognitive 78) finding(s) in Cognitive Complexity — start with MainWindow.axaml.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PacmanPkgDetailsHelper.GetDetails_UnSafe (cognitive 50) finding(s) in Cognitive Complexity — start with PacmanPkgDetailsHelper.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 WinGetPkgOperationHelper._getOperationParameters (cognitive 45) finding(s) in Cognitive Complexity — start with WinGetPkgOperationHelper.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.6 / 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 12 TooManyMethods finding(s) in God Classes — start with IpcClient.cs, IpcServer.cs, MainWindow.axaml.cs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 8 FileTooLong finding(s) in God Classes — start with IpcServer.cs, MainWindow.axaml.cs, AvaloniaAutoUpdater.cs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 ClassTooLong finding(s) in God Classes — start with IpcCliCommandRunner.cs, NativeWinGetHelper.cs, AbstractOperation.cs. — One of this dimension's main actionable groups (5 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.0 / 10Strong✓ 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.
Off the main sequence: UniGetUI.Core.Logging(net10.0) · ×11
What to do
Resolve the 5 Layer violation finding(s) in Coupling. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 11 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (11 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
664 test methods: 664 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.2 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
42 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D24 · Comment Value / 10Exemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
1 of 52 projects flagged as possibly oversized/incoherent.
Split UniGetUI.Avalonia
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.8 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
84 % of calls cross a namespace and 8 % 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 to do
Improve Navigability — currently 8.8/10. — 84 % of calls cross a namespace and 8 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: jwt · ×4WebBasedData/screenshot-database-v2.json:2085detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 4 Secret finding(s) in Secrets (history) — start with screenshot-database-v2.json (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: dependabot-missing-cooldown · ×21.github/dependabot.yml:3detected by semgrep finding
What to do
Resolve the 21 High finding(s) in Static Analysis (SAST) — start with build-release.yml (16), codeql.yml (3), dependabot.yml. — One of this dimension's main actionable groups (21 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
2 of 221 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/ExternalLibraries.Clipboard/WindowsClipboard.cs.
Further orphaned files (smaller)
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Secret passed as a command-line argument finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
`IPackage` declares 36 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IPackage.cs:10
`IPackageDetails` declares 19 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IPackageDetails.cs:3
`IPackageManager` declares 23 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IPackageManager.cs:10
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C1 · Data Protection2.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Do you agree with this assessment?
C2 · Access Controls3.3 / 10Weak✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by imperative guard methods that throw on violation) — this is NOT a claim that the code is unprotected. What's missing is a NAMED rule set: the guards encode the access rules inline, so the rules can't be listed, reviewed or tested apart from the call sites that apply them. Recommendation, not a defect.
Only 2 imperative guard call site(s) — too few to demonstrate default-deny across handlers.
What to do
Name the access rules — give each one a named predicate/policy object your guards consult, so the rule set can be reviewed and unit-tested independently of the call sites that enforce it.
Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.
Do you agree with this assessment?
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
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 placeholder string ("Cached installer is invalid; it will be …") is still in shipped code — typical of generated boilerplate that was never filled in. — AvaloniaAutoUpdater.cs:459
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×21) — TelemetryHandler.cs:168, HomebrewPkgDetailsHelper.cs:100, HomebrewPkgDetailsHelper.cs:103, …
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.
`ConfirmAddSource` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — SourceManagerCardViewModel.cs:97
`GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×8) — AptPkgDetailsHelper.cs:119, CargoPkgDetailsHelper.cs:68, DnfPkgDetailsHelper.cs:102, …
`GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×7) — AptPkgDetailsHelper.cs:122, CargoPkgDetailsHelper.cs:73, DnfPkgDetailsHelper.cs:105, …
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 52 of 52 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Only 26/32 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 32, 1 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.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Roslyn scan: Polly resilience markers (Retry, CircuitBreaker, Timeout) on outbound HTTP invocations. Computed per type, deterministic.
The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.
What to do
Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
What to do
Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×19) — CrashReportWindow.axaml.cs:56, SharedPreUiCommandDispatcher.cs:236, SharedPreUiCommandDispatcher.cs:254, …
`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) — BaseLogPage.axaml.cs:46, BaseLogPage.axaml.cs:53, AbstractPackagesPage.axaml.cs:499, …
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.
Only 12/401 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. (×23) — App.axaml.cs:168, PackageRowModel.cs:162, UserAvatarViewModel.cs:138, …
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. (×2) — PackageCollections.cs:253, UserAvatarViewModel.cs:67
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×15) — CrashHandler.cs:119, CrashHandler.cs:214, Program.cs:25, …
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.3 `!` suppressions per 1k syntax nodes — 83 suppression(s) across the 284788 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 46 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
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.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
D11 Test Reliability — Test reliability not included
D19 Documentation Quality — LLM evaluation failed
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this check looks for (4 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
P12 CI test-gate honesty — 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.
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
High: dependabot-missing-cooldown .github/dependabot.yml:3— This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:39— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: run-shell-injection .github/workflows/build-release.yml:44— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:104— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:120— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v6`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:125— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v6`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:133— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-python@<40-character SHA>`. This step references `actions/setup-python@v7`; resolve the SHA it points at today with `gh api repos/actions/setup-python/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:333— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v7`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:381— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:384— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v6`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:389— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v6`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:493— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:665— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v7`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:681— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/download-artifact@<40-character SHA>`. This step references `actions/download-artifact@v8`; resolve the SHA it points at today with `gh api repos/actions/download-artifact/commits/v8 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:789— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:856— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/download-artifact@<40-character SHA>`. This step references `actions/download-artifact@v8`; resolve the SHA it points at today with `gh api repos/actions/download-artifact/commits/v8 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yml:894— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v7`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/codeql.yml:56— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/codeql.yml:60— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: github/codeql-action/init@<40-character SHA>`. This step references `github/codeql-action/init@v4.37.3`; resolve the SHA it points at today with `gh api repos/github/codeql-action/commits/v4.37.3 --jq .sha`. `github/codeql-action/init` is hosted INSIDE the `github/codeql-action` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `github/codeql-action/init` path in `uses:` and query only `github/codeql-action`. Note that `v4.37.3` is an exact release tag rather than a floating major: it is still mutable (a tag can be repointed), but by convention it moves only on a force-push, so pin the floating-major and branch references in this file first.
High: github-actions-mutable-action-tag .github/workflows/codeql.yml:88— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: github/codeql-action/analyze@<40-character SHA>`. This step references `github/codeql-action/analyze@v4.37.3`; resolve the SHA it points at today with `gh api repos/github/codeql-action/commits/v4.37.3 --jq .sha`. `github/codeql-action/analyze` is hosted INSIDE the `github/codeql-action` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `github/codeql-action/analyze` path in `uses:` and query only `github/codeql-action`. Note that `v4.37.3` is an exact release tag rather than a floating major: it is still mutable (a tag can be repointed), but by convention it moves only on a force-push, so pin the floating-major and branch references in this file first.
High: github-actions-mutable-action-tag .github/workflows/translation-validation.yml:36— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
EmptyCatchBlock src/UniGetUI.Avalonia/CrashHandler.cs:119— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/CrashHandler.cs:214— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:150— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:233— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/Program.cs:25— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:147— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:325— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:364— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/ContributorsViewModel.cs:36— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/TranslatorsViewModel.cs:38— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1084— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.Core.Logger/Logger.cs:57— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:465— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs:536— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs:548— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
NoWarnInCsproj src/UniGetUI.Avalonia/UniGetUI.Avalonia.csproj:45— MVVMTK0045 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/UniGetUI.Avalonia/UniGetUI.Avalonia.csproj:45— AVLN3001 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Directory.Build.props:65— EnableGenerateDocumentationFile — 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.
TooManyMethods: IpcClient src/UniGetUI.Interface.IpcApi/IpcClient.cs:0— TooManyMethods — 809 significant lines (blank, comment-only and punctuation-only lines excluded), 98 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IpcServer src/UniGetUI.Interface.IpcApi/IpcServer.cs:0— TooManyMethods — 1093 significant lines (blank, comment-only and punctuation-only lines excluded), 97 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainWindow src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:0— TooManyMethods — 997 significant lines (blank, comment-only and punctuation-only lines excluded), 76 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CoreTools src/UniGetUI.Core.Tools/Tools.cs:0— TooManyMethods — 603 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: PackagesPageViewModel src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:0— TooManyMethods — 567 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractPackagesPage src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:0— TooManyMethods — 443 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AvaloniaAutoUpdater src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:0— TooManyMethods — 870 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: MainWindowViewModel src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs:0— TooManyMethods — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IpcPackageApi src/UniGetUI.Interface.IpcApi/IpcPackageApi.cs:0— TooManyMethods — 395 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Settings src/UniGetUI.Core.Settings/SettingsEngine_Dictionaries.cs:0— TooManyMethods — 571 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods, declared across 6 files: UniGetUI.Core.Settings/SettingsEngine_Dictionaries.cs (9), UniGetUI.Core.Settings/SettingsEngine_Extras.cs (8), UniGetUI.Core.Settings/SettingsEngine_Lists.cs (8), UniGetUI.Core.Settings/SettingsEngine_ImportExport.cs (5), +2 more file(s). The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: WinGet src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs:0— TooManyMethods — 455 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InstallOptionsViewModel src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:0— TooManyMethods — 404 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Off the main sequence: UniGetUI.Core.Logging(net10.0) — UniGetUI.Core.Logging(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 31 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Interface.Enums(net10.0) — UniGetUI.Interface.Enums(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 23 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.PackageEngine.Structs(net10.0) — UniGetUI.PackageEngine.Structs(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 28 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.Data(net10.0) — UniGetUI.Core.Data(net10.0): abstractness 0.00, instability 0.03, distance 0.97 — zone of pain — concrete and depended on by 29 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.Settings(net10.0) — UniGetUI.Core.Settings(net10.0): abstractness 0.00, instability 0.07, distance 0.93 — zone of pain — concrete and depended on by 28 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.LanguageEngine(net10.0) — UniGetUI.Core.LanguageEngine(net10.0): abstractness 0.00, instability 0.16, distance 0.84 — zone of pain — concrete and depended on by 27 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.Tools(net10.0) — UniGetUI.Core.Tools(net10.0): abstractness 0.00, instability 0.19, distance 0.81 — zone of pain — concrete and depended on by 26 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.Classes(net10.0) — UniGetUI.Core.Classes(net10.0): abstractness 0.17, instability 0.03, distance 0.80 — zone of pain — concrete and depended on by 28 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.IconEngine(net10.0) — UniGetUI.Core.IconEngine(net10.0): abstractness 0.00, instability 0.23, distance 0.77 — zone of pain — concrete and depended on by 23 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.SecureSettings(net10.0) — UniGetUI.Core.SecureSettings(net10.0): abstractness 0.00, instability 0.26, distance 0.74 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
Off the main sequence: ExternalLibraries.WindowsPackageManager.Interop — ExternalLibraries.WindowsPackageManager.Interop: abstractness 0.27, instability 0.00, distance 0.73 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Hotspot: src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs— src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs changed 39 times in last 90 days, max complexity 39. 14 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs— src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs changed 10 times in last 90 days, max complexity 48. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs— src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs changed 16 times in last 90 days, max complexity 22. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs— src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs changed 10 times in last 90 days, max complexity 25. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs— src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs changed 8 times in last 90 days, max complexity 27. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs— src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs changed 10 times in last 90 days, max complexity 17. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs— src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs changed 2 times in last 90 days, max complexity 85. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs— src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs changed 8 times in last 90 days, max complexity 19. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/UniGetUI.Core.Tools/Tools.cs src/UniGetUI.Core.Tools/Tools.cs— src/UniGetUI.Core.Tools/Tools.cs changed 8 times in last 90 days, max complexity 18. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
Hotspot: src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs— src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs changed 8 times in last 90 days, max complexity 17. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, 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.
TodoComment src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:346— // TODO: Replace table parsing with JSON deserialization when bun outdated adds --json flag.
TodoComment src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgDetailsHelper.cs:61— // TODO: most packages are hosted on Github; see if there's a way to use the repository — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:57— // TODO: since each change results in a new commit to the file, you could determine the `UpdateDate` via figuring out the date of the last commit that changed the file was.
TodoComment src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:62— // TODO: the "features" and "dependencies" keys could also be good candidates for tags, however their type specifications are all over -
TodoComment src/UniGetUI.PackageEngine.Managers.Vcpkg/Vcpkg.cs:106— // TODO: Perhaps use --x-json when it is fixed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UniGetUI.PackageEngine.Managers.Vcpkg/Vcpkg.cs:260— // TODO: Once --x-json is stable migrate to --x-json — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:243— // TODO: Restart required to finish installation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:266— // TODO: Integrity failed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FileTooLong: UniGetUI.Interface.IpcApi/IpcServer.cs src/UniGetUI.Interface.IpcApi/IpcServer.cs:0— FileTooLong — 1114 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Views/MainWindow.axaml.cs src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:0— FileTooLong — 1112 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Infrastructure/AvaloniaAutoUpdater.cs src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:0— FileTooLong — 922 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.Interface.IpcApi/IpcClient.cs src/UniGetUI.Interface.IpcApi/IpcClient.cs:0— FileTooLong — 823 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SoftwarePages/PackagesPageViewModel.cs src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:0— FileTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.Core.Tools/Tools.cs src/UniGetUI.Core.Tools/Tools.cs:0— FileTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs:0— FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs:0— FileTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (15 lines × 2) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:784— src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:784-798 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:944-959 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:784` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:882— src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:882-900 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1003-1017 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:882` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:82— src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:82-96 | src/UniGetUI.Interface.IpcApi/IpcBackupApi.cs:506-523 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:82` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/UniGetUI.Interface.IpcApi/IpcServer.cs:706— src/UniGetUI.Interface.IpcApi/IpcServer.cs:706-720 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:767-781 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Interface.IpcApi/IpcServer.cs:706` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/UniGetUI.PackageEngine.Operations/SourceOperations.cs:70— src/UniGetUI.PackageEngine.Operations/SourceOperations.cs:70-84 | src/UniGetUI.PackageEngine.Operations/SourceOperations.cs:167-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Operations/SourceOperations.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:181— src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:181-195 | src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:226-240 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:181` 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.
ClassTooLong: IpcCliCommandRunner src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs:0— ClassTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: NativeWinGetHelper src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs:0— ClassTooLong — 475 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AbstractOperation src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:0— ClassTooLong — 463 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PackageManagerPage src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs:0— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: IpcBundleApi src/UniGetUI.Interface.IpcApi/IpcBundleApi.cs:0— ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Duplicated block (6 lines × 2) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:853— src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:853-858 | src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:861-866 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:853` 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) src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:385— src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:385-390 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:369-374 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:385` 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) src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:54— src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:54-59 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:72-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:54` 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 (6 lines × 2) src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs:122— src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs:122-127 | src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7SourceHelper.cs:129-134 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:179— src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:179-184 | src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:313-318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:179` 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.
Low cohesion: MainWindow (LCOM4 10) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:48— MainWindow's methods form 10 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: ObservablePackageCollection (LCOM4 5) src/UniGetUI.Avalonia/Models/PackageCollections.cs:423— ObservablePackageCollection's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: HelpPage (LCOM4 4) src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:7— HelpPage's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: AbstractPackagesPage (LCOM4 4) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:30— AbstractPackagesPage's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: WinGet (LCOM4 4) src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs:21— WinGet's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
BarePragmaDisable src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1327— #pragma warning disable SYSLIB0057 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/UniGetUI.Core.Classes.Tests/SortableObservableCollectionTests.cs:1— #pragma warning disable CA1852 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/UniGetUI.Core.Logging.Tests/LoggerTests.cs:1— #pragma warning disable CA2201 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetIconsHelper.cs:29— #pragma warning disable SYSLIB0014 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
Duplicated block (26 lines × 2) src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:127— src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:127-152 | src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs:126-151 — before extracting anything, compare `src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs` and `src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 `src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:127` 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 (26 lines × 2) src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:160— src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:160-185 | src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs:159-184 — before extracting anything, compare `src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs` and `src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 `src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs:59— src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs:59-84 | src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7SourceHelper.cs:59-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:16— src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:16-31 | src/UniGetUI.Avalonia/Views/Pages/ReleaseNotesPage.axaml.cs:15-30 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:111— src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:111-128 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:93-108 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/UniGetUI.PackageEngine.Managers.Snap/SnapParsing.cs:13— src/UniGetUI.PackageEngine.Managers.Snap/SnapParsing.cs:13-28 | src/UniGetUI.PackageEngine.Managers.Snap/SnapParsing.cs:96-111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Snap/SnapParsing.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:87— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:87-102 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/UpdatesViewModel.cs:60-72 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/UniGetUI.Avalonia/Infrastructure/WindowsAppNotificationBridge.cs:114— src/UniGetUI.Avalonia/Infrastructure/WindowsAppNotificationBridge.cs:114-126 | src/UniGetUI.Avalonia/Infrastructure/WindowsAppNotificationBridge.cs:154-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/WindowsAppNotificationBridge.cs:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:69— src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:69-81 | src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:214-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewSourceHelper.cs:21— src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewSourceHelper.cs:21-31 | src/UniGetUI.PackageEngine.Managers.Flatpak/Helpers/FlatpakSourceHelper.cs:24-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewSourceHelper.cs:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:141— src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:141-151 | src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:92-102 — 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 (11 lines × 2) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/PingetCliHelper.cs:174— src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/PingetCliHelper.cs:174-184 | src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:434-446 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/PingetCliHelper.cs:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/UniGetUILogPageViewModel.cs:73— src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/UniGetUILogPageViewModel.cs:73-81 | src/UniGetUI.Interface.IpcApi/IpcLogsApi.cs:174-181 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/UniGetUILogPageViewModel.cs:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:162— src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:162-169 | src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:248-256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:162` 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) src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:174— src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:174-181 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:257-264 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (23 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:132— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:132-154 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/UpdatesViewModel.cs:99-121 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (23 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:126— src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:126-150 | src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:109-131 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:126` 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 (21 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:124— src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:124-162 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:125-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (21 lines × 2) src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:16— src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:16-38 | src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:16-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs:263— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs:263-269 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PackageManagerViewModel.cs:182-188 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs:263` 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 (7 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:111— src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:111-117 | src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:110-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:111` 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.
WinGetPkgOperationHelper._getOperationParameters (cyclomatic 48) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:31— WinGetPkgOperationHelper._getOperationParameters has cyclomatic complexity 48 (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.
MainWindow.OnWindowsWndProc (cyclomatic 39) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1088— MainWindow.OnWindowsWndProc 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.
Bun.ParseBunOutdatedTable (cyclomatic 34) src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:349— Bun.ParseBunOutdatedTable has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 14 of the 34 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 379, 380). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AbstractOperation.MainThreadCore (cyclomatic 31) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:223— AbstractOperation.MainThreadCore has cyclomatic complexity 31 (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.
MainWindow.Window_KeyDown (cyclomatic 30) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:267— MainWindow.Window_KeyDown has cyclomatic complexity 30 (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.
WinGetPkgOperationHelper._getOperationResult (cyclomatic 29) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:232— WinGetPkgOperationHelper._getOperationResult has cyclomatic complexity 29 (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.
AbstractOperation._runOperation (cyclomatic 28) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:425— AbstractOperation._runOperation 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.
ScoopPkgDetailsHelper.GetDetails_UnSafe (cyclomatic 28) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:17— ScoopPkgDetailsHelper.GetDetails_UnSafe 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.
PackageManagerPage.BuildPage (cyclomatic 27) src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs:56— PackageManagerPage.BuildPage has cyclomatic complexity 27 (threshold 15). Of this number, 15 points are the body's own statements and 12 belong to 6 function literals inside it that branch. 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.
AbstractProcessOperation.PerformOperation (cyclomatic 27) src/UniGetUI.PackageEngine.Operations/AbstractProcessOperation.cs:76— AbstractProcessOperation.PerformOperation 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.
PackagesPageViewModel.FilterPackages (cyclomatic 25) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:538— PackagesPageViewModel.FilterPackages has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 belong to 2 function literals inside it that branch. 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.
PacmanPkgDetailsHelper.GetDetails_UnSafe (cyclomatic 25) src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:15— PacmanPkgDetailsHelper.GetDetails_UnSafe 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.
AptPkgDetailsHelper.GetDetails_UnSafe (cyclomatic 24) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:15— AptPkgDetailsHelper.GetDetails_UnSafe has cyclomatic complexity 24 (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.
WinGetCliHelper.GetAvailableUpdates_UnSafe (cyclomatic 24) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:44— WinGetCliHelper.GetAvailableUpdates_UnSafe has cyclomatic complexity 24 (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.
AbstractPackagesPage.AbstractPackagesPage.ctor (cyclomatic 22) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:44— AbstractPackagesPage.AbstractPackagesPage.ctor has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 4 function literals inside it that branch. 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.
UpdaterDownloadEngine.DownloadInstallerPartAsync (cyclomatic 22) src/UniGetUI.Core.Tools/UpdaterDownloadEngine.cs:102— UpdaterDownloadEngine.DownloadInstallerPartAsync has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScoopPkgOperationHelper._getOperationParameters (cyclomatic 22) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgOperationHelper.cs:15— ScoopPkgOperationHelper._getOperationParameters has cyclomatic complexity 22 (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.
WinGetCliHelper.GetInstalledPackages_UnSafe (cyclomatic 22) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:186— WinGetCliHelper.GetInstalledPackages_UnSafe 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.
ProcessTaskLogger.AsColoredString (cyclomatic 21) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:224— ProcessTaskLogger.AsColoredString has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SnapPkgDetailsHelper.GetDetails_UnSafe (cyclomatic 21) src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:15— SnapPkgDetailsHelper.GetDetails_UnSafe 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.
IpcClient.BuildPackageQueryParameters (cyclomatic 20) src/UniGetUI.Interface.IpcApi/IpcClient.cs:1209— IpcClient.BuildPackageQueryParameters has cyclomatic complexity 20 (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.
IpcClient.GetRequestTimeout (cyclomatic 20) src/UniGetUI.Interface.IpcApi/IpcClient.cs:1353— IpcClient.GetRequestTimeout has cyclomatic complexity 20 (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.
AvaloniaAutoUpdater.CheckAndInstallUpdatesAsync (cyclomatic 19) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:383— AvaloniaAutoUpdater.CheckAndInstallUpdatesAsync 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.
BaseNuGetDetailsHelper.GetDetails_UnSafe (cyclomatic 19) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:18— BaseNuGetDetailsHelper.GetDetails_UnSafe has cyclomatic complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
OperationViewModel.RebuildMenu (cyclomatic 18) src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:199— OperationViewModel.RebuildMenu has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CoreData.GetNewDataDirectoryOrMoveOld (cyclomatic 18) src/UniGetUI.Core.Data/CoreData.cs:447— CoreData.GetNewDataDirectoryOrMoveOld has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CoreTools.VersionStringToStruct (cyclomatic 18) src/UniGetUI.Core.Tools/Tools.cs:500— CoreTools.VersionStringToStruct has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PEInterface.CreateManagers (cyclomatic 18) src/UniGetUI.PackageEngine.PackageEngine/PEInterface.cs:85— PEInterface.CreateManagers has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NativeTaskLogger.AsColoredString (cyclomatic 18) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:398— NativeTaskLogger.AsColoredString has cyclomatic complexity 18 (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.
PowerShellPkgOperationHelper._getOperationParameters (cyclomatic 18) src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs:13— PowerShellPkgOperationHelper._getOperationParameters has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InstallOptionsViewModel.InstallOptionsViewModel.ctor (cyclomatic 17) src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:229— InstallOptionsViewModel.InstallOptionsViewModel.ctor 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.
SvgIcon.ParseSvg (cyclomatic 17) src/UniGetUI.Avalonia/Views/Controls/SvgIcon.cs:113— SvgIcon.ParseSvg has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AbstractPackageLoader.ReloadPackages (cyclomatic 17) src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:131— AbstractPackageLoader.ReloadPackages 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.
WinGet.GetLocalSource (cyclomatic 17) src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs:256— WinGet.GetLocalSource has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 2 function literals inside it that branch. 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.
CrashHandler.ReportFatalException (cyclomatic 16) src/UniGetUI.Avalonia/CrashHandler.cs:93— CrashHandler.ReportFatalException 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.
PowerShell7PkgOperationHelper._getOperationParameters (cyclomatic 16) src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7PkgOperationHelper.cs:13— PowerShell7PkgOperationHelper._getOperationParameters 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.
D17 · Explicit Debt· BarePragmaDisable repeated 11 times in 4 files · ×1
BarePragmaDisable repeated 11 times in 4 files src/ExternalLibraries.FilePickers/Classes/Helper.cs:46— The identical BarePragmaDisable (`#pragma warning disable CA1416`) appears 11 times in 4 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 11 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)
Monorepo: only 1 of 2 solutions was scored — This repository contains 2 .NET solutions, but a scan analyzes ONE. Every score, lens, and finding here reflects only `src/UniGetUI.Windows.slnx` — the other 1 (`InstallerExtras/MsiCreator/MsiInstallerWrapper.sln`) were not analyzed and are not represented in the headline. To cover them, scan each solution as its own target and group them in a Solution or Product for a portfolio roll-up. If a secondary solution is an archived or vendored tree, declare it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — to exclude it from discovery the same way generated code is.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[1] | LineNumber: 0 | BytePositionInLine: 1154.
MainWindow.OnWindowsWndProc (cognitive 78) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1088— MainWindow.OnWindowsWndProc has cognitive complexity 78 (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.
PacmanPkgDetailsHelper.GetDetails_UnSafe (cognitive 50) src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:15— PacmanPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 50 (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.
WinGetPkgOperationHelper._getOperationParameters (cognitive 45) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:31— WinGetPkgOperationHelper._getOperationParameters has cognitive complexity 45 (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.
AbstractOperation.MainThreadCore (cognitive 44) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:223— AbstractOperation.MainThreadCore has cognitive complexity 44 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ScoopPkgDetailsHelper.GetDetails_UnSafe (cognitive 43) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:17— ScoopPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 43 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AbstractOperation._runOperation (cognitive 42) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:425— AbstractOperation._runOperation has cognitive complexity 42 (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.
AbstractProcessOperation.PerformOperation (cognitive 37) src/UniGetUI.PackageEngine.Operations/AbstractProcessOperation.cs:76— AbstractProcessOperation.PerformOperation has cognitive complexity 37 (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.
AptPkgDetailsHelper.GetDetails_UnSafe (cognitive 37) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:15— AptPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 37 (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.
WinGetCliHelper.GetAvailableUpdates_UnSafe (cognitive 37) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:44— WinGetCliHelper.GetAvailableUpdates_UnSafe has cognitive complexity 37 (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.
AbstractPackageLoader.ReloadPackages (cognitive 34) src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:131— AbstractPackageLoader.ReloadPackages has cognitive complexity 34 (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.
SnapPkgDetailsHelper.GetDetails_UnSafe (cognitive 34) src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:15— SnapPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 34 (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.
CoreData.GetNewDataDirectoryOrMoveOld (cognitive 31) src/UniGetUI.Core.Data/CoreData.cs:447— CoreData.GetNewDataDirectoryOrMoveOld has cognitive complexity 31 (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.
InstalledPackagesLoader.ReloadPackagesSilently (cognitive 31) src/UniGetUI.PackageEngine.PackageLoader/InstalledPackagesLoader.cs:48— InstalledPackagesLoader.ReloadPackagesSilently has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WinGetCliHelper.GetInstalledPackages_UnSafe (cognitive 31) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:186— WinGetCliHelper.GetInstalledPackages_UnSafe has cognitive complexity 31 (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.
WinGetPkgOperationHelper._getOperationResult (cognitive 31) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:232— WinGetPkgOperationHelper._getOperationResult has cognitive complexity 31 (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.
BaseNuGet.FindPackages_UnSafe (cognitive 31) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:61— BaseNuGet.FindPackages_UnSafe has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PackageManagerPage.BuildPage (cognitive 28) src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs:56— PackageManagerPage.BuildPage has cognitive complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 6 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ProcessTaskLogger.AsColoredString (cognitive 28) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:224— ProcessTaskLogger.AsColoredString has cognitive complexity 28 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CoreTools.VersionStringToStruct (cognitive 27) src/UniGetUI.Core.Tools/Tools.cs:500— CoreTools.VersionStringToStruct has cognitive complexity 27 (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.
PipPkgDetailsHelper.GetDetails_UnSafe (cognitive 27) src/UniGetUI.PackageEngine.Managers.Pip/Helpers/PipPkgDetailsHelper.cs:18— PipPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 27 (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.
UserAvatarViewModel.RefreshAsync (cognitive 26) src/UniGetUI.Avalonia/ViewModels/Controls/UserAvatarViewModel.cs:67— UserAvatarViewModel.RefreshAsync has cognitive complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
IpcClient.BuildPackageQueryParameters (cognitive 25) src/UniGetUI.Interface.IpcApi/IpcClient.cs:1209— IpcClient.BuildPackageQueryParameters has cognitive complexity 25 (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.
IpcCliSyntax.Parse (cognitive 24) src/UniGetUI.Interface.IpcApi/IpcCliSyntax.cs:27— IpcCliSyntax.Parse has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
BaseNuGetDetailsHelper.GetDetails_UnSafe (cognitive 24) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:18— BaseNuGetDetailsHelper.GetDetails_UnSafe has cognitive complexity 24 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
OperationViewModel.RebuildMenu (cognitive 23) src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:199— OperationViewModel.RebuildMenu has cognitive complexity 23 (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.
UpdaterDownloadEngine.DownloadInstallerPartAsync (cognitive 23) src/UniGetUI.Core.Tools/UpdaterDownloadEngine.cs:102— UpdaterDownloadEngine.DownloadInstallerPartAsync has cognitive complexity 23 (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.
ArpRegistryHelper.BuildIndex (cognitive 23) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/ArpRegistryHelper.cs:111— ArpRegistryHelper.BuildIndex has cognitive complexity 23 (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.
CrashHandler.ReportFatalException (cognitive 22) src/UniGetUI.Avalonia/CrashHandler.cs:93— CrashHandler.ReportFatalException has cognitive complexity 22 (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.
MainWindow.Window_KeyDown (cognitive 22) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:267— MainWindow.Window_KeyDown has cognitive complexity 22 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Scoop.ParseInstalledPackages (cognitive 22) src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:298— Scoop.ParseInstalledPackages 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.
PackagesPageViewModel.FilterPackages (cognitive 21) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:538— PackagesPageViewModel.FilterPackages has cognitive complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AvaloniaAutoUpdater.CheckAndInstallUpdatesAsync (cognitive 21) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:383— AvaloniaAutoUpdater.CheckAndInstallUpdatesAsync has cognitive complexity 21 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DWMThreadHelper.ChangeState (cognitive 21) src/UniGetUI.Core.Tools/DWMThreadHelper.cs:137— DWMThreadHelper.ChangeState 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.
NativeTaskLogger.AsColoredString (cognitive 21) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:398— NativeTaskLogger.AsColoredString has cognitive complexity 21 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
InstallOptionsFactory.EnsureSecureOptions (cognitive 21) src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/InstallOptionsFactory.cs:223— InstallOptionsFactory.EnsureSecureOptions 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.
WinGetPkgOperationHelper.TryGetPortableInstallLocation (cognitive 21) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:535— WinGetPkgOperationHelper.TryGetPortableInstallLocation 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.
AbstractPackagesPage.UpdateFilterPaneColumn (cognitive 20) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:462— AbstractPackagesPage.UpdateFilterPaneColumn 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.
LanguageData.LoadLanguageTranslatorList (cognitive 20) src/UniGetUI.Core.LanguageEngine/LanguageData.cs:124— LanguageData.LoadLanguageTranslatorList 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.
IpcClient.GetRequestTimeout (cognitive 20) src/UniGetUI.Interface.IpcApi/IpcClient.cs:1353— IpcClient.GetRequestTimeout has cognitive complexity 20 (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.
Scoop.ParseAvailableUpdates (cognitive 20) src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:216— Scoop.ParseAvailableUpdates 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.
ArpRegistryHelper.ReadLocation (cognitive 19) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/ArpRegistryHelper.cs:162— ArpRegistryHelper.ReadLocation has cognitive complexity 19 (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.
WinGetCliHelper.FindPackages_UnSafe (cognitive 19) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:320— WinGetCliHelper.FindPackages_UnSafe has cognitive complexity 19 (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.
InstallOptionsViewModel.InstallOptionsViewModel.ctor (cognitive 18) src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:229— InstallOptionsViewModel.InstallOptionsViewModel.ctor 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.
ManagerLogsPageViewModel.LoadForManager (cognitive 18) src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/ManagerLogsPageViewModel.cs:25— ManagerLogsPageViewModel.LoadForManager 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.
PackagesPageViewModel.GetSelectedSourceFilters (cognitive 18) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:796— PackagesPageViewModel.GetSelectedSourceFilters 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.
SvgIcon.ParseSvg (cognitive 18) src/UniGetUI.Avalonia/Views/Controls/SvgIcon.cs:113— SvgIcon.ParseSvg 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.
SerializationHelpers.ConvertXmlNode (cognitive 18) src/UniGetUI.Core.Tools/SerializationHelpers.cs:45— SerializationHelpers.ConvertXmlNode 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.
PowerShellPkgOperationHelper._getOperationParameters (cognitive 18) src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs:13— PowerShellPkgOperationHelper._getOperationParameters 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.
PowerShell7SourceHelper.GetSources_UnSafe (cognitive 18) src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7SourceHelper.cs:57— PowerShell7SourceHelper.GetSources_UnSafe has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ScoopSourceHelper.ParseSources (cognitive 18) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopSourceHelper.cs:84— ScoopSourceHelper.ParseSources 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.
MainWindow.SetupTitleBar (cognitive 17) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:501— MainWindow.SetupTitleBar 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.
MainWindow.IsRectangleFullyVisible (cognitive 17) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:905— MainWindow.IsRectangleFullyVisible 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.
AbstractPackagesPage.AbstractPackagesPage.ctor (cognitive 17) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:44— AbstractPackagesPage.AbstractPackagesPage.ctor has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 132, 66, 55, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AvaloniaBootstrapper.GetMissingDependenciesAsync (cognitive 17) src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:491— AvaloniaBootstrapper.GetMissingDependenciesAsync has cognitive complexity 17 (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.
UpgradablePackagesLoader.IsPackageValid (cognitive 17) src/UniGetUI.PackageEngine.PackageLoader/UpgradablePackagesLoader.cs:34— UpgradablePackagesLoader.IsPackageValid has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CargoPkgOperationHelper._getOperationParameters (cognitive 17) src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgOperationHelper.cs:11— CargoPkgOperationHelper._getOperationParameters 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.
DnfPkgDetailsHelper.GetDetails_UnSafe (cognitive 17) src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:15— DnfPkgDetailsHelper.GetDetails_UnSafe 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.
InternetViewModel.BuildProxyCompatTable (cognitive 16) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:81— InternetViewModel.BuildProxyCompatTable 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.
OperationFailedDialog.BuildRetryButton (cognitive 16) src/UniGetUI.Avalonia/Views/DialogPages/OperationFailedDialog.axaml.cs:87— OperationFailedDialog.BuildRetryButton 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.
SoftwareUpdatesPage.WhenPackagesLoaded (cognitive 16) src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:388— SoftwareUpdatesPage.WhenPackagesLoaded has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PEInterface.CreateManagers (cognitive 16) src/UniGetUI.PackageEngine.PackageEngine/PEInterface.cs:85— PEInterface.CreateManagers 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.
BasePkgDetailsHelper.GetScreenshots (cognitive 16) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BasePkgDetailsHelper.cs:110— BasePkgDetailsHelper.GetScreenshots has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DesktopShortcutsDatabase.HandleNewShortcuts (cognitive 16) src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/DesktopShortcutsDatabase.cs:202— DesktopShortcutsDatabase.HandleNewShortcuts has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Bun.ParseBunOutdatedTable (cognitive 16) src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:349— Bun.ParseBunOutdatedTable has cognitive complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals 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.
Npm.ParseSearchOutput (cognitive 16) src/UniGetUI.PackageEngine.Managers.Npm/Npm.cs:233— Npm.ParseSearchOutput has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
NativeWinGetHelper.FindPackages_UnSafe (cognitive 16) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs:182— NativeWinGetHelper.FindPackages_UnSafe has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Change coupling: InvalidImportedPackage.cs ↔ Package.cs src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/InvalidImportedPackage.cs— `src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/InvalidImportedPackage.cs` and `src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Package.cs` change together 71% of the time (22 of the 31 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). 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.
Change coupling clique: DiscoverSoftwarePage.cs, InstalledPackagesPage.cs, PackageBundlesPage.cs, SoftwareUpdatesPage.cs src/UniGetUI.Avalonia/Views/SoftwarePages/DiscoverSoftwarePage.cs— 4 files — `src/UniGetUI.Avalonia/Views/SoftwarePages/DiscoverSoftwarePage.cs`, `src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs`, `src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs`, `src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 28 floating ref(s) across 5 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
D36 · Supply-chain Provenance & Signing· PR-triggered workflow without a permissions block · ×1
PR-triggered workflow without a permissions block — 3 workflow(s) triggered by pull_request declare no `permissions:` block (translation-validation.yml, dotnet-test.yml, cli-headless-e2e.yml) and so run with the repository's default GITHUB_TOKEN scope, while 2 sibling workflows in the same repository are already scoped. Pull-request runs build the least-trusted code in the repository; give each of these workflows its own least-privilege block — `permissions: {contents: read}` at the top of the workflow, widened per job only where a job genuinely writes.
D36 · Supply-chain Provenance & Signing· Secret passed as a command-line argument · ×1
Secret passed as a command-line argument — 6 CI command(s) pass a credential as a bare command-line argument, where it is visible in the runner's process table to any other process on the host (and to anything that logs a command line): build-release.yml: -KeyVaultUrl '${{ secrets.CODE_SIGNING_KEYVAULT_URL }}' `; build-release.yml: -ClientSecret '${{ secrets.CODE_SIGNING_CLIENT_SECRET }}' `; build-release.yml: -CertificateName '${{ secrets.CODE_SIGNING_CERTIFICATE_NAME }}' ` …. Pass the credential through the environment instead (an `env:` mapping on the step, read by the tool from its own variable) or on stdin, so it never appears in an argument vector.
Duplicated block (36 lines × 2) src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:182— src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:182-221 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:175-210 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:182` 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 (33 lines × 3) src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:313— src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:313-345 | src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:85-117 | src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs:84-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:313` 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 (30 lines × 2) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:288— src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:288-317 | src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:444-473 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.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. 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 (29 lines × 2) src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:163— src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:163-191 | src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:125-163 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
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.