Public report — UniTask, 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.
167findings with an exact file:lineof 195 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
52/98dimensions across the health lenses39925 LoC · 7 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.
Cysharp/UniTask is sound in substance but carries real gaps (54%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (100%) — the structure is clean and changes stay contained. Code Health (76%) is solid too.
The area that most needs attention is Performance (48%) — it raises ongoing delivery and operational cost. Maturity (51%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: Make the call chain async end-to-end and await it (Async & latency hygiene); Raise allocation-aware density on the hot paths (Allocation hygiene); [MemoryDiagnoser] to the benchmarks so allocation regressions… (Benchmark discipline).
For scale: Medium (~39,925 production lines); rebuilding it from scratch would take roughly ~0.9 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (100%); 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.
Business logic 32%Plumbing 27%Tests 26%Generated 14%Analyzers 0%
New since the last scan (3+)
3 finding(s) are new versus the previous scan (2026-08-01) — surfaced by this scheduled scan itself, no pull request required.
D22 · Semantic overlap and confusion between factory methods. `Create` and `Defer` both accept a factory function to produce a `UniTask`, but `Defer` explicitly implies lazy evaluation (not executing until awaited), whereas `Create` is ambiguous about when the factory runs. `Lazy` is a specialized form of `Defer` for single-shot caching. The naming `Create` vs `Defer` is confusingly similar in intent (both create tasks), yet behave differently regarding execution timing.
D22 · Inconsistent naming for conversion methods. `AsUniTaskAsyncEnumerable` converts a standard `IAsyncEnumerable` to a UniTask-specific interface, while `AsUniTask` converts a `ValueTask` to a `UniTask`. The verb `As` is used for both, but the target types are different (interface vs struct). More importantly, `UniTaskValueTaskExtensions.AsUniTask` converts from `ValueTask`, whereas `AsyncEnumerableExtensions.AsUniTaskAsyncEnumerable` converts from `IAsyncEnumerable`. The naming convention `As[TargetType]` is used, but the source types are disparate standard library types. This is acceptable, but `AsUniTask` is a very generic name that could conflict with other conversions.
D22 · Redundant methods for running synchronous actions on the thread pool. `Run` takes an `Action` and returns a `UniTask`. `Void` takes an `Action` (or `Func` with state) and returns `void` (or `UniTaskVoid`). `Action` takes an `Action` and returns an `Action` (a delegate). These three methods all essentially schedule a synchronous action to run on the thread pool, but with different return types and signatures. `Run` is for fire-and-forget or awaiting, `Void` is for fire-and-forget without a task, `Action` is for getting a delegate. The distinction between `Run` and `Void` is subtle and confusing.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
This codebase represents roughly ~0.9 person-years of build effort (about ~€120,000 to rebuild). Its weakest lens is Performance at 48% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — library/CLI, CQRS, high decision density × a 0.8× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 4 redundant comment finding(s) in Comment Value — start with UniTask.Delay.cs (2), AsyncReactivePropertyTest.cs, ChannelTest.cs.
Raise allocation-aware density on the hot paths — currently 46 use(s) across 49,253 production line(s) (~0.9/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Value concentrated against a weak lens · Medium · Value at risk
This is a Medium asset (~0.9 person-years to rebuild), and its weakest lens is Performance at 48%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Performance 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: Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
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
7 modules, 5 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
24
High / Critical
A06:2021 — Vulnerable & Outdated Components
3
High / Critical
Roadmap
First, refactor the call chain to be fully asynchronous, ensuring no synchronous blocking calls remain in library code. Next, optimize hot paths by introducing allocation-aware patterns like Span and pooling to reduce memory pressure. Then, enable memory diagnostics in benchmarks to prevent allocation regressions. Finally, document key architectural decisions in a centralized location and reorganize the folder structure to ensure tests are discoverable and properly scoped in CI.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 4 redundant comment finding(s) in Comment Value — start with UniTask.Delay.cs (2), AsyncReactivePropertyTest.cs, ChannelTest.cs.
Raise allocation-aware density on the hot paths — currently 46 use(s) across 49,253 production line(s) (~0.9/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
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).
Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
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 52 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.7 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 52 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, 167 of 195 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
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
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.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
The LLM boundary
LLM-set scores this run (5): D19, D21, D22, 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.
12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was _CombineLatest.MoveNextAsync at 48. A further 2 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 ArrayPool.GetQueueIndex at 19 — they are counted neither in the figure above nor in this dimension's score.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 _CombineLatest.MoveNextAsync (cyclomatic 48) finding(s) in Cyclomatic Complexity — start with CombineLatest.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 _CombineLatest.MoveNextAsync (cyclomatic 45) finding(s) in Cyclomatic Complexity — start with CombineLatest.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 _CombineLatest.MoveNextAsync (cyclomatic 42) finding(s) in Cyclomatic Complexity — start with CombineLatest.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.
+ 22 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 _DistinctUntilChanged.MoveNext (cognitive 18) finding(s) in Cognitive Complexity — start with DistinctUntilChanged.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 UniTaskCompletionSource.TrySignalCompletion (cognitive 17) finding(s) in Cognitive Complexity — start with UniTaskCompletionSource.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 _CombineLatest.MoveNextAsync (cognitive 64) finding(s) in Cognitive Complexity — start with CombineLatest.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 Classes10.0 / 10Exemplary✓ 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.
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.
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 28 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with MinMax.cs (25), Max.cs (3). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 20 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with MinMax.cs (15), GroupJoin.cs, Max.cs. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 2 Duplicated block (25 lines × 2) finding(s) in Code Duplication — start with DistinctUntilChanged.cs, Select.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
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.
183 test methods: 183 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 Quality9.8 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 3 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 183 tests.
No assertions: Empty · ×3src/UniTask.NetCoreTests/TaskBuilderCases.cs:20
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, 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.
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 the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The UniTask project has strong documentation: a single README.md (5k words) and docs/index.md (14 words), plus an outline-driven table of contents. The README is the longest document in the set and gives a clear value proposition with features like zero-allocation Struct<T> and custom AsyncMethodBuilder, full awaitability for Unity Coroutines/MessageEvents/uGUI Events, PlayerLoop-based task types, TaskTracker memory protection, and links to two detailed blog posts (UniTask v2 and async decorator pattern). The docs are well-organized around a TOC with the outline present. However, the XML-doc coverage is extremely low: 49/2281 for UniTask.NetCore and 0/1 for both NetCoreSandbox and Analyzer projects, leaving much of the API surface undocumented.
Resolve the 3 Low XML-doc coverage finding(s) in Documentation Quality — start with UniTask.NetCore.csproj, UniTask.NetCoreSandbox.csproj, UniTask.Analyzer.csproj. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API Consistency / 10Strong◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
3 API inconsistencies across a 400-member sample of 303 exposed types.
Semantic overlap and confusion between factory methods. `Create` and `Defer` both accept a factory function to produce a `UniTask`, but `Defer` explicitly implies lazy evaluation (not executing until awaited), whereas `Create` is ambiguous about when the factory runs. `Lazy` is a specialized form of `Defer` for single-shot caching. The naming `Create` vs `Defer` is confusingly similar in intent (both create tasks), yet behave differently regarding execution timing.
Inconsistent naming for conversion methods. `AsUniTaskAsyncEnumerable` converts a standard `IAsyncEnumerable` to a UniTask-specific interface, while `AsUniTask` converts a `ValueTask` to a `UniTask`. The verb `As` is used for both, but the target types are different (interface vs struct). More importantly, `UniTaskValueTaskExtensions.AsUniTask` converts from `ValueTask`, whereas `AsyncEnumerableExtensions.AsUniTaskAsyncEnumerable` converts from `IAsyncEnumerable`. The naming convention `As[TargetType]` is used, but the source types are disparate standard library types. This is acceptable, but `AsUniTask` is a very generic name that could conflict with other conversions.
Redundant methods for running synchronous actions on the thread pool. `Run` takes an `Action` and returns a `UniTask`. `Void` takes an `Action` (or `Func` with state) and returns `void` (or `UniTaskVoid`). `Action` takes an `Action` and returns an `Action` (a delegate). These three methods all essentially schedule a synchronous action to run on the thread pool, but with different return types and signatures. `Run` is for fire-and-forget or awaiting, `Void` is for fire-and-forget without a task, `Action` is for getting a delegate. The distinction between `Run` and `Void` is subtle and confusing.
What to do
Resolve the 1 Semantic overlap and confusion between factory methods. `Create` and… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent naming for conversion methods. `AsUniTaskAsyncEnumerable`… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Redundant methods for running synchronous actions on the thread pool.… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment Value / 10Critical◐ 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.
Resolve the 4 redundant comment finding(s) in Comment Value — start with UniTask.Delay.cs (2), AsyncReactivePropertyTest.cs, ChannelTest.cs. — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
82 % of calls cross a namespace and 2 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries 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.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: github-actions-mutable-action-tag · ×24.github/workflows/build-debug.yaml:18detected by semgrep finding
What to do
Resolve the 24 High finding(s) in Static Analysis (SAST) — start with build-release.yaml (12), build-debug.yaml (7), build-docs.yaml (4). — One of this dimension's main actionable groups (24 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
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 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No artifact signing finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified
Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×8) — UniTask.Delay.cs:13, UniTask.Delay.cs:20, UniTask.Delay.cs:25, …
`Forget` has an empty body — confirm it's an intentional no-op and not an unfinished method. — UniTaskVoid.cs:14
What to do
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the 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 4 of 4 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.
No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
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).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
Only 4/7 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries. Exhaustive, deterministic.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Performance — Whether the library protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way a library pressures its host's GC) aren't being measured.
What to do
Add [MemoryDiagnoser] to the benchmarks so allocation regressions are visible, not just time.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Raise allocation-aware density on the hot paths — currently 46 use(s) across 49,253 production line(s) (~0.9/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
121 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.
Only 0/1003 awaits use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
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.
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 1/5 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. (×4) — UniTask.Run.cs:9, UniTask.Run.cs:35, UniTask.Run.cs:61, …
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.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
1/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
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 CQRS 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.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D23 Boundary Type-Coupling — Bounded contexts not declared
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 OSV Dependency Vulnerabilities — Scanner failed to run — not a clean result
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — no coverage collector is wired up
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this check looks for
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this check looks for (20 CQRS handler(s))
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — 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
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
High: github-actions-mutable-action-tag .github/workflows/build-debug.yaml:18— 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: Cysharp/Actions/.github/actions/checkout@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/checkout@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/checkout` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/checkout` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-debug.yaml:19— 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: Cysharp/Actions/.github/actions/setup-dotnet@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/setup-dotnet@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/setup-dotnet` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/setup-dotnet` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-debug.yaml:47— 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: Cysharp/Actions/.github/actions/checkout@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/checkout@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/checkout` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/checkout` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-debug.yaml:53— 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: Cysharp/Actions/.github/actions/unity-builder@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/unity-builder@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/unity-builder` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/unity-builder` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-debug.yaml:67— 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: Cysharp/Actions/.github/actions/unity-builder@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/unity-builder@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/unity-builder` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/unity-builder` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-debug.yaml:83— 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: Cysharp/Actions/.github/actions/check-metas@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/check-metas@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/check-metas` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/check-metas` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-debug.yaml: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: Cysharp/Actions/.github/actions/upload-artifact@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/upload-artifact@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/upload-artifact` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/upload-artifact` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-docs.yaml:28— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: Cysharp/Actions/.github/actions/checkout@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/checkout@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/checkout` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/checkout` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-docs.yaml:32— 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: Cysharp/Actions/.github/actions/unity-builder@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/unity-builder@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/unity-builder` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/unity-builder` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-docs.yaml:43— 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: Cysharp/Actions/.github/actions/checkout@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/checkout@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/checkout` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/checkout` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-docs.yaml:47— 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: Cysharp/Actions/.github/actions/setup-dotnet@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/setup-dotnet@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/setup-dotnet` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/setup-dotnet` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml:34— 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: Cysharp/Actions/.github/actions/checkout@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/checkout@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/checkout` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/checkout` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml:37— 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: Cysharp/Actions/.github/actions/setup-dotnet@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/setup-dotnet@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/setup-dotnet` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/setup-dotnet` path in `uses:` and query only `Cysharp/Actions`.
High: run-shell-injection .github/workflows/build-release.yaml:39— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-release.yaml:41— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml:43— 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: Cysharp/Actions/.github/actions/upload-artifact@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/upload-artifact@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/upload-artifact` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/upload-artifact` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml:71— 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: Cysharp/Actions/.github/actions/checkout@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/checkout@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/checkout` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/checkout` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml:77— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: Cysharp/Actions/.github/actions/unity-builder@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/unity-builder@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/unity-builder` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/unity-builder` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml: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: Cysharp/Actions/.github/actions/check-metas@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/check-metas@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/check-metas` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/check-metas` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml:93— 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: Cysharp/Actions/.github/actions/upload-artifact@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/upload-artifact@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/upload-artifact` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/upload-artifact` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml:109— 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: Cysharp/Actions/.github/actions/setup-dotnet@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/setup-dotnet@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/setup-dotnet` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/setup-dotnet` path in `uses:` and query only `Cysharp/Actions`.
High: github-actions-mutable-action-tag .github/workflows/build-release.yaml:110— 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: Cysharp/Actions/.github/actions/download-artifact@<40-character SHA>`. This step references `Cysharp/Actions/.github/actions/download-artifact@main`; resolve the SHA it points at today with `gh api repos/Cysharp/Actions/commits/main --jq .sha`. `Cysharp/Actions/.github/actions/download-artifact` is hosted INSIDE the `Cysharp/Actions` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `Cysharp/Actions/.github/actions/download-artifact` path in `uses:` and query only `Cysharp/Actions`.
High: secrets-inherit .github/workflows/build-release.yaml:136— This workflow uses `secrets: inherit` to pass all of the calling workflow's secrets to a reusable workflow. This violates the principle of least privilege because the called workflow receives access to every secret in the repository, not just the ones it needs. If the called workflow is compromised or sourced from a third party, an attacker gains access to all repository secrets. Instead, explicitly pass only the secrets that the called workflow requires using the `secrets:` map, e.g. `secrets: { MY_SECRET: ${{ secrets.MY_SECRET }} }`.
High: secrets-inherit .github/workflows/toc.yaml:15— This workflow uses `secrets: inherit` to pass all of the calling workflow's secrets to a reusable workflow. This violates the principle of least privilege because the called workflow receives access to every secret in the repository, not just the ones it needs. If the called workflow is compromised or sourced from a third party, an attacker gains access to all repository secrets. Instead, explicitly pass only the secrets that the called workflow requires using the `secrets:` map, e.g. `secrets: { MY_SECRET: ${{ secrets.MY_SECRET }} }`.
High CVE: Newtonsoft.Json 9.0.1 — Newtonsoft.Json 9.0.1 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Http 4.3.0 — System.Net.Http 4.3.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Text.RegularExpressions 4.3.0 — System.Text.RegularExpressions 4.3.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
NoWarnInCsproj src/UniTask.NetCore/UniTask.NetCore.csproj:10— CS1591 — 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.
Duplicated block (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:84— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:84-102 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Min.cs:84-102 — before extracting anything, compare `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs` and `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Min.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:123— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:123-141 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Min.cs:123-141 — before extracting anything, compare `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs` and `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Min.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:123` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:162— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:162-180 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Min.cs:162-180 — before extracting anything, compare `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs` and `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Min.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:362— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:362-380 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2240-2258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:362` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:401— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:401-419 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2279-2297 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:401` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:439— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:439-457 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2317-2335 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:439` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:514— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:514-532 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2392-2410 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:514` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:553— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:553-571 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2431-2449 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:553` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:591— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:591-609 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2469-2487 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:591` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:666— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:666-684 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2544-2562 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:666` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:705— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:705-723 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2583-2601 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:705` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:743— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:743-761 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2621-2639 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:743` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:818— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:818-836 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2696-2714 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:818` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:857— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:857-875 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2735-2753 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:857` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:895— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:895-913 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2773-2791 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:895` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:970— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:970-988 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2848-2866 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:970` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1009— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1009-1027 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2887-2905 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1009` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1047— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1047-1065 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2925-2943 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1047` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1164— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1164-1182 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3042-3060 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1164` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1204— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1204-1222 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3082-3100 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1204` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1324— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1324-1342 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3202-3220 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1324` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1364— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1364-1382 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3242-3260 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1364` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1484— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1484-1502 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3362-3380 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1484` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1524— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1524-1542 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3402-3420 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1524` 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 (19 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1644— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1644-1662 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3522-3540 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1644` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupJoin.cs:347— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupJoin.cs:347-366 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupJoin.cs:542-561 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupJoin.cs:347` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:46— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:46-65 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Min.cs:46-65 — before extracting anything, compare `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs` and `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Min.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Max.cs:46` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:324— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:324-343 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2202-2221 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:324` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:476— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:476-495 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2354-2373 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:476` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:628— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:628-647 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2506-2525 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:628` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:780— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:780-799 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2658-2677 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:780` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:932— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:932-951 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2810-2829 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:932` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1085— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1085-1104 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:2963-2982 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1085` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1125— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1125-1144 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3003-3022 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1125` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1245— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1245-1264 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3123-3142 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1245` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1285— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1285-1304 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3163-3182 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1285` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1405— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1405-1424 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3283-3302 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1405` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1445— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1445-1464 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3323-3342 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1445` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1565— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1565-1584 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3443-3462 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1565` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1605— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1605-1624 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3483-3502 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1605` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1725— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1725-1744 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3603-3622 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1725` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1765— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1765-1784 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:3643-3662 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/MinMax.cs:1765` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:315— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:315-334 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:487-506 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:315` 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 (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/UniTask.WhenAll.cs:71— src/UniTask/Assets/Plugins/UniTask/Runtime/UniTask.WhenAll.cs:71-90 | src/UniTask/Assets/Plugins/UniTask/Runtime/UniTask.WhenAny.cs:191-210 — 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/UniTask/Assets/Plugins/UniTask/Runtime/UniTask.WhenAll.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:676— src/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:676-695 | src/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:867-886 — 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/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:676` 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.
BarePragmaDisable src/UniTask.Analyzer/UniTaskAnalyzer.cs:1— #pragma warning disable RS2008 — 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/UniTask.NetCore/NetCore/AsyncEnumerableExtensions.cs:3— #pragma warning disable 0649 — 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/UniTask.NetCoreSandbox/Program.cs:1— #pragma warning disable CS1998 — 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/UniTask.NetCoreTests/Linq/CreateTest.cs:1— #pragma warning disable CS1998 — 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/UniTask.NetCoreTests/Linq/Merge.cs:1— #pragma warning disable CS1998 — 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/UniTask.NetCoreTests/TaskBuilderCases.cs:1— #pragma warning disable CS1998 — 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/UniTask.NetCoreTests/TaskExtensionsTest.cs:1— #pragma warning disable CS1998 — 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/UniTask.NetCoreTests/Linq/CreateTest.cs:2— #pragma warning disable CS0162 — 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.
No assertions: Empty src/UniTask.NetCoreTests/TaskBuilderCases.cs:20— Test method exercises code but verifies nothing — add an assertion.
No assertions: Task_Done src/UniTask.NetCoreTests/TaskBuilderCases.cs:41— Test method exercises code but verifies nothing — add an assertion.
No assertions: AwaitUnsafeOnCompletedCall_Task_SetResult src/UniTask.NetCoreTests/TaskBuilderCases.cs:74— Test method exercises code but verifies nothing — add an assertion.
Dead code: StateMachineUtility src/UniTask/Assets/Plugins/UniTask/Runtime/CompilerServices/StateMachineRunner.cs:41— NamedType StateMachineUtility — no references found in solution.
Dead code: ArrayUtil src/UniTask/Assets/Plugins/UniTask/Runtime/Internal/ArrayUtil.cs:9— NamedType ArrayUtil — no references found in solution.
_DistinctUntilChanged.MoveNext (cognitive 18) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:112— _DistinctUntilChanged.MoveNext 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.
_DistinctUntilChanged.MoveNext (cognitive 18) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:254— _DistinctUntilChanged.MoveNext 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.
UniTaskCompletionSource.TrySignalCompletion (cognitive 17) src/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:704— UniTaskCompletionSource.TrySignalCompletion 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.
UniTaskCompletionSource.TrySignalCompletion (cognitive 17) src/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:895— UniTaskCompletionSource.TrySignalCompletion 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.
Duplicated block (25 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:464— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:464-488 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:622-646 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:464` 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 (25 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:129— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:129-153 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:238-262 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:129` 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 (23 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:94— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:94-116 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:250-272 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:94` 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 (23 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:146— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:146-168 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:310-332 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:146` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:635— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:635-656 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:877-898 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:635` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:527— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:527-548 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:803-824 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:527` 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 (21 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:422— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:422-442 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:652-672 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:422` 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 (21 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:492— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:492-512 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:768-788 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:492` 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 (20 lines × 3) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:288— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:288-307 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:542-561 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:818-837 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:288` 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 (20 lines × 3) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipLast.cs:80— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipLast.cs:80-100 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntil.cs:106-125 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntilCanceled.cs:86-105 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipLast.cs:80` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 3) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:295— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:295-312 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:514-531 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:756-773 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/GroupBy.cs:295` 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 (18 lines × 3) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:96— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:96-113 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:250-267 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:422-439 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/AsyncLazy.cs:77— src/UniTask/Assets/Plugins/UniTask/Runtime/AsyncLazy.cs:77-93 | src/UniTask/Assets/Plugins/UniTask/Runtime/AsyncLazy.cs:196-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/AsyncLazy.cs:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntil.cs:136— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntil.cs:136-152 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntilCanceled.cs:116-132 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntil.cs:136` 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:338— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:338-353 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:510-525 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:338` 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/UniTask/Assets/Plugins/UniTask/Runtime/UniTask.WhenAll.cs:166— src/UniTask/Assets/Plugins/UniTask/Runtime/UniTask.WhenAll.cs:166-181 | src/UniTask/Assets/Plugins/UniTask/Runtime/UniTask.WhenAny.cs:282-297 — 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/UniTask/Assets/Plugins/UniTask/Runtime/UniTask.WhenAll.cs:166` 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.
_CombineLatest.MoveNextAsync (cyclomatic 48) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:10233— _CombineLatest.MoveNextAsync has cyclomatic complexity 48 (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.
_CombineLatest.MoveNextAsync (cyclomatic 45) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:8964— _CombineLatest.MoveNextAsync has cyclomatic complexity 45 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_CombineLatest.MoveNextAsync (cyclomatic 42) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:7779— _CombineLatest.MoveNextAsync has cyclomatic complexity 42 (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.
_CombineLatest.MoveNextAsync (cyclomatic 39) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:6678— _CombineLatest.MoveNextAsync has cyclomatic complexity 39 (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.
_CombineLatest.MoveNextAsync (cyclomatic 36) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:5661— _CombineLatest.MoveNextAsync has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_CombineLatest.MoveNextAsync (cyclomatic 33) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:4728— _CombineLatest.MoveNextAsync has cyclomatic complexity 33 (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.
_CombineLatest.MoveNextAsync (cyclomatic 30) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:3879— _CombineLatest.MoveNextAsync has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_CombineLatest.MoveNextAsync (cyclomatic 27) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:3114— _CombineLatest.MoveNextAsync has cyclomatic complexity 27 (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.
_CombineLatest.MoveNextAsync (cyclomatic 24) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:2433— _CombineLatest.MoveNextAsync has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_CombineLatest.MoveNextAsync (cyclomatic 21) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:1836— _CombineLatest.MoveNextAsync 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.
_CombineLatest.MoveNextAsync (cyclomatic 18) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:1323— _CombineLatest.MoveNextAsync 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.
_CombineLatest.DisposeAsync (cyclomatic 16) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:11305— _CombineLatest.DisposeAsync has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dormant codebase — no living knowledge left to concentrate — All 2 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
D18 · Solution Shape· Analyzed solution does not cover the bulk of the repository · ×1
Analyzed solution does not cover the bulk of the repository — The scored solution `UniTask.NetCore.sln` is not representative of this repository — it references only 64 of 242 discovered C# files (26 %). Lenses that need the product's source (domain modelling, event-driven, event sourcing) abstain because the aggregates, EF configs, and domain events under the product tree were not loaded. Point the scan at the product solution (or scan its directory directly) so the whole codebase is analyzed, not a build-tooling sub-solution.
_CombineLatest.MoveNextAsync (cognitive 64) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:10233— _CombineLatest.MoveNextAsync has cognitive complexity 64 (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.
_CombineLatest.MoveNextAsync (cognitive 60) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:8964— _CombineLatest.MoveNextAsync has cognitive complexity 60 (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.
_CombineLatest.MoveNextAsync (cognitive 56) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:7779— _CombineLatest.MoveNextAsync has cognitive complexity 56 (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.
_CombineLatest.MoveNextAsync (cognitive 52) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:6678— _CombineLatest.MoveNextAsync has cognitive complexity 52 (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.
_CombineLatest.MoveNextAsync (cognitive 48) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:5661— _CombineLatest.MoveNextAsync has cognitive complexity 48 (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.
_CombineLatest.MoveNextAsync (cognitive 44) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:4728— _CombineLatest.MoveNextAsync 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.
_CombineLatest.MoveNextAsync (cognitive 40) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:3879— _CombineLatest.MoveNextAsync has cognitive complexity 40 (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.
_CombineLatest.MoveNextAsync (cognitive 36) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:3114— _CombineLatest.MoveNextAsync has cognitive complexity 36 (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.
_CombineLatest.MoveNextAsync (cognitive 32) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:2433— _CombineLatest.MoveNextAsync has cognitive complexity 32 (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.
_CombineLatest.MoveNextAsync (cognitive 28) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:1836— _CombineLatest.MoveNextAsync 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.
AsyncEnumerableSorter.QuickSort (cognitive 26) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/OrderBy.cs:240— AsyncEnumerableSorter.QuickSort has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CombineLatest.MoveNextAsync (cognitive 24) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:1323— _CombineLatest.MoveNextAsync has cognitive complexity 24 (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.
_DistinctUntilChangedAwait.MoveNext (cognitive 21) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:400— _DistinctUntilChangedAwait.MoveNext 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.
_DistinctUntilChangedAwaitWithCancellation.MoveNext (cognitive 21) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:558— _DistinctUntilChangedAwaitWithCancellation.MoveNext 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.
WeakDictionary.AddToBuckets (cognitive 20) src/UniTask/Assets/Plugins/UniTask/Runtime/Internal/WeakDictionary.cs:115— WeakDictionary.AddToBuckets has cognitive complexity 20 (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.
_BufferSkip.MoveNextCore (cognitive 20) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Buffer.cs:287— _BufferSkip.MoveNextCore has cognitive complexity 20 (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.
_CombineLatest.MoveNextAsync (cognitive 20) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:894— _CombineLatest.MoveNextAsync 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, 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.
TriggerEvent.Remove (cognitive 20) src/UniTask/Assets/Plugins/UniTask/Runtime/TriggerEvent.cs:226— TriggerEvent.Remove 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.
SingleConsumerUnboundedChannelReader.TryRead (cognitive 19) src/UniTask/Assets/Plugins/UniTask/Runtime/Channel.cs:216— SingleConsumerUnboundedChannelReader.TryRead has cognitive complexity 19 (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.
SequenceEqual.SequenceEqualAsync (cognitive 19) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SequenceEqual.cs:27— SequenceEqual.SequenceEqualAsync has cognitive complexity 19 (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.
_Do.MoveNextCore (cognitive 18) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Do.cs:201— _Do.MoveNextCore 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.
_SelectManyAwait.SeletedSourceMoveNextCore (cognitive 18) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:517— _SelectManyAwait.SeletedSourceMoveNextCore 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.
_SelectManyAwaitWithCancellation.SeletedSourceMoveNextCore (cognitive 18) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SelectMany.cs:793— _SelectManyAwaitWithCancellation.SeletedSourceMoveNextCore 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.
_TakeLast.MoveNextCore (cognitive 17) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/TakeLast.cs:123— _TakeLast.MoveNextCore 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.
_CombineLatest.MoveNextAsync (cognitive 16) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/CombineLatest.cs:549— _CombineLatest.MoveNextAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
D22 · Internal API Consistency· Semantic overlap and confusion between factory methods. `Create` and `Defer` both accept a factory function to produce a `UniTask`, but `Defer` explicitly implies lazy evaluation (not executing until awaited), whereas `Create` is ambiguous about when the factory runs. `Lazy` is a specialized form of `Defer` for single-shot caching. The naming `Create` vs `Defer` is confusingly similar in intent (both create tasks), yet behave differently regarding execution timing. · ×1
Semantic overlap and confusion between factory methods. `Create` and `Defer` both accept a factory function to produce a `UniTask`, but `Defer` explicitly implies lazy evaluation (not executing until awaited), whereas `Create` is ambiguous about when the factory runs. `Lazy` is a specialized form of `Defer` for single-shot caching. The naming `Create` vs `Defer` is confusingly similar in intent (both create tasks), yet behave differently regarding execution timing. — Rename `Create` to `FromFactory` or `FromAsyncFactory` to distinguish it from `Defer` (lazy) and `Lazy` (cached). Or, if `Create` is meant to be eager, rename `Defer` to `FromLazyFactory` to clarify the lazy evaluation aspect. (signatures: UniTask.Create(...) | UniTask.Defer(...) | UniTask.Lazy(...))
D22 · Internal API Consistency· Inconsistent naming for conversion methods. `AsUniTaskAsyncEnumerable` converts a standard `IAsyncEnumerable` to a UniTask-specific interface, while `AsUniTask` converts a `ValueTask` to a `UniTask`. The verb `As` is used for both, but the target types are different (interface vs struct). More importantly, `UniTaskValueTaskExtensions.AsUniTask` converts from `ValueTask`, whereas `AsyncEnumerableExtensions.AsUniTaskAsyncEnumerable` converts from `IAsyncEnumerable`. The naming convention `As[TargetType]` is used, but the source types are disparate standard library types. This is acceptable, but `AsUniTask` is a very generic name that could conflict with other conversions. · ×1
Inconsistent naming for conversion methods. `AsUniTaskAsyncEnumerable` converts a standard `IAsyncEnumerable` to a UniTask-specific interface, while `AsUniTask` converts a `ValueTask` to a `UniTask`. The verb `As` is used for both, but the target types are different (interface vs struct). More importantly, `UniTaskValueTaskExtensions.AsUniTask` converts from `ValueTask`, whereas `AsyncEnumerableExtensions.AsUniTaskAsyncEnumerable` converts from `IAsyncEnumerable`. The naming convention `As[TargetType]` is used, but the source types are disparate standard library types. This is acceptable, but `AsUniTask` is a very generic name that could conflict with other conversions. — The naming is actually quite consistent (`As[Target]`), but the sheer number of `As...` methods across different extension classes (`UniTaskValueTaskExtensions`, `AsyncEnumerableExtensions`, `UniTaskExtensions`) makes it hard to find them. Consider grouping them or using a more specific verb like `ToUniTask` for all conversions to be consistent with `ToAsyncLazy` in `UniTaskExtensions`. (signatures: AsyncEnumerableExtensions.AsUniTaskAsyncEnumerable | UniTaskValueTaskExtensions.AsUniTask)
D22 · Internal API Consistency· Redundant methods for running synchronous actions on the thread pool. `Run` takes an `Action` and returns a `UniTask`. `Void` takes an `Action` (or `Func` with state) and returns `void` (or `UniTaskVoid`). `Action` takes an `Action` and returns an `Action` (a delegate). These three methods all essentially schedule a synchronous action to run on the thread pool, but with different return types and signatures. `Run` is for fire-and-forget or awaiting, `Void` is for fire-and-forget without a task, `Action` is for getting a delegate. The distinction between `Run` and `Void` is subtle and confusing. · ×1
Redundant methods for running synchronous actions on the thread pool. `Run` takes an `Action` and returns a `UniTask`. `Void` takes an `Action` (or `Func` with state) and returns `void` (or `UniTaskVoid`). `Action` takes an `Action` and returns an `Action` (a delegate). These three methods all essentially schedule a synchronous action to run on the thread pool, but with different return types and signatures. `Run` is for fire-and-forget or awaiting, `Void` is for fire-and-forget without a task, `Action` is for getting a delegate. The distinction between `Run` and `Void` is subtle and confusing. — Consolidate `Run` and `Void` into a single `Run` method that returns `UniTask` (fire-and-forget) or use a single `Run` that returns `UniTask` and a separate `RunVoid` for fire-and-forget. The existence of `Action` as a third way to run a sync action is confusing. (signatures: UniTask.Run | UniTask.Void | UniTask.Action)
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 26 floating ref(s) across 6 workflow file(s), 26 of them mutable BRANCH refs — pin those first. The reusable-workflow ref(s) below are the SAST lens's blind spot — pin these first: `Cysharp/Actions/.github/workflows/toc-generator.yaml@main` (.github/workflows/toc.yaml:12), `Cysharp/Actions/.github/workflows/stale-issue.yaml@main` (.github/workflows/stale.yaml:14), `Cysharp/Actions/.github/workflows/pr-harness.yaml@main` (.github/workflows/pr-harness.yaml:12), `Cysharp/Actions/.github/workflows/update-packagejson.yaml@main` (.github/workflows/build-release.yaml:20), `Cysharp/Actions/.github/workflows/create-release.yaml@main` (.github/workflows/build-release.yaml:128), `Cysharp/Actions/.github/workflows/clean-packagejson-branch.yaml@main` (.github/workflows/build-release.yaml:143)
Duplicated block (28 lines × 4) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:371— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:371-398 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:503-530 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:634-661 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:766-793 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:371` 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 (28 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:131— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:131-158 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:249-276 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:160— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:160-186 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:304-330 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:160` 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 (24 lines × 4) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:347— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:347-370 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:469-492 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:590-613 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:712-735 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Select.cs:347` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:725— src/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:725-748 | src/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:916-939 — 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/UniTask/Assets/Plugins/UniTask/Runtime/UniTaskCompletionSource.cs:725` 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 (22 lines × 4) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:122— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:122-143 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:264-285 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:410-431 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/DistinctUntilChanged.cs:568-589 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (22 lines × 3) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:180— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:180-201 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:380-401 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:610-631 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:180` 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 (21 lines × 3) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:128— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:128-148 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:282-302 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:454-474 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Zip.cs:128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:448— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:448-465 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:678-695 — 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/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Join.cs:448` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:484— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:484-500 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:615-631 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:747-763 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/Where.cs:484` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntil.cs:82— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntil.cs:82-96 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/TakeUntil.cs:88-103 — 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 (12 lines × 2) src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntilCanceled.cs:52— src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/SkipUntilCanceled.cs:52-63 | src/UniTask/Assets/Plugins/UniTask/Runtime/Linq/TakeUntilCanceled.cs:51-64 — 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.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: the test suite built and its tests PASSED, but the run produced no coverage data — `--collect:"XPlat Code Coverage"` found no data collector, which is what a test project with no `coverlet.collector` PackageReference does. Nothing is wrong with the suite or the build; there is simply no coverage instrumentation wired up. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
redundant comment src/UniTask.NetCore/NetCore/UniTask.Delay.cs:20— "throw new NotImplementedException();" — delete - boilerplate marker, no WHY or constraint.
redundant comment src/UniTask.NetCoreTests/AsyncReactivePropertyTest.cs:55— "[Fact]" — delete - generated attribute; the test method's [Fact] already says this. Remove it so reviewers don't mistake a non-ignored attribute for code.
redundant comment src/UniTask.NetCoreTests/ChannelTest.cs:105— "Empty." — delete - generated filler, no intent or constraint.
Thin analysable surface across projects — 1 project(s) carry only a thin slice of real code (e.g. `UniTask.Analyzer` with 47 significant line(s)). The mean analysable-surface weight is 93 %, lowering Solution Shape by about 0.6 point(s). Consolidate thin projects or grow them into substantial, well-scoped assemblies.
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 29458 LoC spread over 7 projects the codebase is large and multi-module, so explicit bounded contexts are needed. Name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
No build provenance — No SLSA provenance generation or build attestation found in CI — nothing binds a released artifact to the build that produced it, so a consumer cannot tell your artifact from a substituted one. On GitHub Actions, `actions/attest-build-provenance` (or slsa-github-generator) emits one from the job's own OIDC identity; elsewhere, run `cosign attest` over the released artifact from the release pipeline and publish the attestation beside it.
No artifact signing — No artifact signing found in CI — sign your released artifacts with whatever your ecosystem ships (a GPG/minisign detached signature — or `cosign sign-blob` — over the release archives, or over a checksum file published alongside them, Authenticode via signtool, or `dotnet nuget sign` for packages) so consumers can verify what you built.
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`sbom-tool generate` (install it with `dotnet tool install --global Microsoft.Sbom.DotNetTool`) or `dotnet CycloneDX` over the solution, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing.
D38 · OSV Dependency Vulnerabilities· Scanner failed to run · ×1
Scanner failed to run — not a clean result — osv-scanner exited 128 with no findings — the advisory database was likely unreachable. The scanner exited non-zero and produced no findings (typically the advisory DB was unreachable), so this is reported as a measurement gap rather than a clean pass.
Outdated: FluentAssertions — FluentAssertions 5.10.3 → 8.10.0 available (referenced by UniTask.NetCoreTests).
Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 16.6.1 → 18.8.1 available (referenced by UniTask.NetCoreTests).
Outdated: System.Interactive.Async — System.Interactive.Async 4.1.1 → 7.0.1 available (referenced by UniTask.NetCoreTests).
Outdated: System.Linq.Async — System.Linq.Async 4.1.1 → 7.0.1 available (referenced by UniTask.NetCoreTests).
Outdated: System.Reactive — System.Reactive 4.4.1 → 7.0.0 available (referenced by UniTask.NetCoreTests).
Outdated: xunit — xunit 2.4.1 → 2.9.3 available (referenced by UniTask.NetCoreTests).
Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 2.4.1 → 3.1.5 available (referenced by UniTask.NetCoreTests).
Outdated: System.Threading.Tasks.Extensions — System.Threading.Tasks.Extensions 4.5.4 → 4.6.3 available (referenced by UniTask.NetCore).
Outdated: BenchmarkDotNet — BenchmarkDotNet 0.12.1 → 0.15.8 available (referenced by UniTask.NetCoreSandbox).
Outdated: Microsoft.CodeAnalysis.Analyzers — Microsoft.CodeAnalysis.Analyzers 3.3.2 → 5.6.0 available (referenced by UniTask.Analyzer).
Outdated: Microsoft.CodeAnalysis.CSharp — Microsoft.CodeAnalysis.CSharp 3.8.0 → 5.6.0 available (referenced by UniTask.Analyzer).
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 019fd1d0-4b30-765d-bf3b-4cfceca6f510 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 28 · Warnings: 146 · Recommendations: 10 · Info: 11 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 05-08-2026 @ 12:05 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.