Public report — DotNetty, published 1 Jul 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
457findings with an exact file:lineof 523 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
53/94dimensions across the health lenses83815 LoC · 85 projects — wide & deep
Executive summary
Read through the Preview lens: this repo is pre-1.0 / in development, so the colour bands are relaxed to what a preview needs — *green* means good enough for a preview, not yet production-stable. Code correctness and security stay near-strict even here; the score itself is absolute and comparable across repos.
hench/DotNetty is sound in substance but carries real gaps (49%). 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 (85%) — the structure is clean and changes stay contained.
The area that most needs attention is Readiness (45%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Code Health (50%) is the next concern — changes there are slower and more error-prone.
Leadership focus, highest impact first: 9 Deprecated finding(s) in Dependency Hygiene (Dependency Hygiene); readiness/liveness probes and a rolling-update (or blue/green)… (Deployment & Rollback); Keep a changelog (e.g. Keep-a-Changelog) recording what shipped… (Release Hygiene).
For scale: Medium (~83,815 production lines); rebuilding it from scratch would take roughly ~1.5 person-years (~1–3 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (85%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
This codebase represents roughly ~1.5 person-years of build effort (about ~€220,000 to rebuild). Its weakest lens is Readiness at 45% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — library/CLI, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 9 Deprecated finding(s) in Dependency Hygiene.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~1.5 person-years to rebuild), and its weakest lens is Readiness at 45%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
At a glance — Code Health · 50% · Adequate · gated by X1
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
A06:2021 — Vulnerable & Outdated Components
6
High / Critical
Roadmap
Begin by addressing dependency hygiene, specifically resolving the nine deprecated and two vulnerable findings to reduce technical debt and security risks. Next, implement automated deployment strategies, such as readiness probes and rolling updates, to ensure bad releases are caught and rolled back automatically. Then, establish a changelog to clearly record what is shipped in each release. Finally, enforce quality gates by running the full test suite in CI and blocking merges that fail tests.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 9 Deprecated finding(s) in Dependency Hygiene.
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 53 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 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 — 53 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 457 of 523 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D31 IaC & Container Security — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D32 Data Compliance (PII/GDPR) — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D33 JS/npm Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D36 Supply-chain Provenance & Signing — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D37 Vulnerability-disclosure Policy — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D38 OSV Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
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 (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (EF migrations, designer files, snapshots) 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.
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".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
+ 36 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Inflate.Inflate_I (cyclomatic 101) finding(s) in Cyclomatic Complexity — start with Inflate.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 InfBlocks.Proc (cyclomatic 74) finding(s) in Cyclomatic Complexity — start with InfBlocks.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 InfCodes.Proc (cyclomatic 58) finding(s) in Cyclomatic Complexity — start with InfCodes.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.
+ 95 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 ByteBufferUtil.WriteUtf8 (cognitive 19) finding(s) in Cognitive Complexity — start with ByteBufferUtil.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Inflate.Inflate_I (cognitive 264) finding(s) in Cognitive Complexity — start with Inflate.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 InfBlocks.Proc (cognitive 236) finding(s) in Cognitive Complexity — start with InfBlocks.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 Classes7.5 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 40 TooManyMethods finding(s) in God Classes — start with AbstractBootstrap.cs, AbstractByteBuffer.cs, AbstractChannel.cs. — One of this dimension's main actionable groups (40 warning-level).
Resolve the 11 FileTooLong finding(s) in God Classes — start with AbstractByteBuffer.cs, AbstractChannelHandlerContext.cs, AsciiString.cs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with HttpObjectDecoder.cs, HttpPostRequestEncoder.cs, Inflate.cs. — One of this dimension's main actionable groups (3 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.8 / 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.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
2126 test methods: 2126 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.
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.
Resolve the 9 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 issue-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
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: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
No source file's living knowledge is concentrated in a single author.
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md.
Do you agree with this assessment?
D17 · Explicit Debt9.0 / 10Strong✓ Tool-verified
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 NoWarnInCsproj finding(s) in Explicit Debt — start with UWPEcho.Client.csproj (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 3 EmptyCatchBlock finding(s) in Explicit Debt — start with Program.cs (2), DefaultSocketChannelConfiguration.cs. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 NoWarnInCsproj repeated across 11 files finding(s) in Explicit Debt — start with DotNetty.Transport.csproj. — One of this dimension's main actionable groups (1 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
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 DotNetty project has a strong README that introduces the framework and contributes links to NuGet, MyGet, GitHub issues, and Microsoft Azure contribution guidelines. However, it is incomplete: there are no examples (only one UWPEcho.Client example with SSL using StreamSocketChannel) for most major packages in the set, and only one package's XML documentation coverage is non-zero across 19 packages (DotNetty.Common at 20%, DotNetty.Codecs.Mqtt at 0%).
Resolve the 28 Low XML-doc coverage finding(s) in Documentation Quality — start with Discard.Client.csproj, Discard.Server.csproj, DotNetty.Buffers.csproj. — One of this dimension's main actionable groups (28 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 / 10Adequate◐ 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 1034 exposed types.
Ambiguous lifecycle and cleanup operations. 'Remove' and 'Destroy' are used interchangeably or in parallel across FastThreadLocal and InternalThreadLocalMap, creating confusion about whether one is for cleanup and the other for removal.
Inconsistent naming for asynchronous scheduling. 'ScheduleAsync' is used, but the return type is 'Task' rather than 'Task<T>' or 'IScheduledTask', and the naming convention differs from 'SubmitAsync' used in AbstractExecutorService.
Inconsistent naming for queue insertion. 'TryEnqueue' and 'Offer' are used for similar operations, causing confusion about whether one is non-blocking and the other is blocking or vice versa.
What to do
Resolve the 1 Ambiguous lifecycle and cleanup operations. 'Remove' and 'Destroy' are… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent naming for asynchronous scheduling. 'ScheduleAsync' is… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent naming for queue insertion. 'TryEnqueue' and 'Offer' are… 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 / 10Adequate◐ 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 1 redundant comment finding(s) in Comment Value — start with DiscardClientHandler.cs. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 43 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.0 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
41 % of calls cross a namespace and 13 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What to do
Improve Navigability — currently 8.0/10. — 41 % of calls cross a namespace and 13 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
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.
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D39 · IL Efficiency9.9 / 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 dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
`IInternalLogger` declares 49 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IInternalLogger.cs:12, IInternalLogger.cs:12
`IByteBuffer` declares 188 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IByteBuffer.cs:22, IByteBuffer.cs:22
`IByteBufferAllocator` declares 18 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IByteBufferAllocator.cs:9, IByteBufferAllocator.cs:9
`IPoolArenaMetric` declares 46 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IPoolArenaMetric.cs:8, IPoolArenaMetric.cs:8
`IChannel` declares 40 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IChannel.cs:12, IChannel.cs:12
`IChannelConfiguration` declares 27 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IChannelConfiguration.cs:9, IChannelConfiguration.cs:9
`IChannelHandler` declares 19 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IChannelHandler.cs:10, IChannelHandler.cs:10
`IChannelHandlerContext` declares 31 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IChannelHandlerContext.cs:13, IChannelHandlerContext.cs:13
`IChannelPipeline` declares 50 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IChannelPipeline.cs:181, IChannelPipeline.cs:181
`IChannelGroup` declares 17 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IChannelGroup.cs:10, IChannelGroup.cs:10
`IDatagramChannelConfig` declares 27 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IDatagramChannelConfig.cs:9, IDatagramChannelConfig.cs:9
`ISocketChannelConfiguration` declares 21 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — ISocketChannelConfiguration.cs:6, ISocketChannelConfiguration.cs:6
`IHeaders` declares 90 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IHeaders.cs:8, IHeaders.cs:8
`IValueConverter` declares 19 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IValueConverter.cs:6, IValueConverter.cs:6
`ICookie` declares 23 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — ICookie.cs:9, ICookie.cs:9
`IHttpData` declares 26 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IHttpData.cs:10, IHttpData.cs:10
`IInterfaceHttpPostRequestDecoder` declares 17 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — IInterfaceHttpPostRequestDecoder.cs:9, IInterfaceHttpPostRequestDecoder.cs:9
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation7.5 / 10Strong✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
`DotNetty.Transport.Tests.Performance` (production) references the test project `DotNetty.Tests.Common`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Other · Security — Whether access is authorized by default — [Authorize]/policies or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
What to do
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×6) — TcpSocketChannel.cs:72, TcpSocketChannel.cs:189, TcpSocketChannel.cs:226, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
`IsWritable` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — EmptyByteBuffer.cs:66, EmptyByteBuffer.cs:66
`ToString` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — EmptyByteBuffer.cs:446, EmptyByteBuffer.cs:446
`IsReadable` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — EmptyByteBuffer.cs:470, EmptyByteBuffer.cs:470
`Release` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×12) — EmptyByteBuffer.cs:486, EmptyByteBuffer.cs:486, UnreleasableByteBuffer.cs:50, …
`Contains` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — EmptyHttpHeaders.cs:57, EmptyHttpHeaders.cs:57
`IsContentAlwaysEmpty` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — HttpObjectEncoder.cs:206, HttpObjectEncoder.cs:206
`IsContentLengthInvalid` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — WebSocketFrameAggregator.cs:34, WebSocketFrameAggregator.cs:34
`NewContinueResponse` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×4) — WebSocketFrameAggregator.cs:36, WebSocketFrameAggregator.cs:36, RedisBulkStringAggregator.cs:28, …
`TryDequeue` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — ExecutorTaskScheduler.cs:46, ExecutorTaskScheduler.cs:46
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 101 words — likely missing build/run/architecture context.
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
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 43 of 43 project(s) that lack one — worth up to 2 pts.
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.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Exemplary✓ Tool-verified
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.
A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (dotnet test / npm test / pytest / a test job) was matched — the gate may be running tests, or "test" may be incidental (a path, "latest", a reporter). Make the test step explicit so the gate is unambiguous.
What to do
Run the test suite in CI via an explicit runner step (e.g. `dotnet test`) and gate merges on it.
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/Roslyn scan: CodeQL, Dependabot, secret-scanning, and BenchmarkDotNet presence in pipelines and projects. Exhaustive, deterministic.
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.
Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether the library protects its performance with benchmarks — a BenchmarkDotNet suite, an allocation MemoryDiagnoser, 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.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's GC — Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask, value-type structs 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 66 use(s) across 168,074 production line(s) (~0.4/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.
52 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/196 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 · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
MD5/SHA1 is broken for security purposes (collision-vulnerable). Use SHA-256+ for content integrity; for password storage, use a KDF (PBKDF2/Argon2/BCrypt). — WebSocketUtil.cs:22
What to do
Replace MD5/SHA1 with SHA-256+ for content hashing; switch to a KDF (PBKDF2/Argon2/BCrypt) for password storage.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Make the caller `async` and `await` instead. (×11) — SingleThreadEventExecutor.cs:491, XThread.cs:93, HashedWheelTimer.cs:420, …
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` unless this is a top-level event handler. (×14) — FixedChannelPool.cs:231, FixedChannelPool.cs:306, SimpleChannelPool.cs:161, …
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 2/68 async methods accept a CancellationToken, so requests can't be cancelled cleanly under load or on client disconnect. In Blazor Server circuits and other short-write hosts, omitting it can be an accepted convention — judge against your hosting model.
No CancellationToken parameter — work can't be cancelled cleanly on disconnect/shutdown. (×25) — HashedWheelTimer.cs:186, HashedWheelTimer.cs:186, AbstractBootstrap.cs:253, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — DefaultSocketChannelConfiguration.cs:29, DefaultSocketChannelConfiguration.cs:29, Program.cs:68, …
`throw e;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. (×2) — ByteToMessageDecoder.cs:273, ByteToMessageDecoder.cs:273
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.
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 — 42 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
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 — no data
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.
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.
D11 Test Reliability — No tests discovered
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 ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 OSV Dependency Vulnerabilities — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — test suite did not build
DM1 Domain Modelling — not run — 0/3 markers found
ED1 Event-Driven — not run — 0/3 markers found
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not run — 0/3 markers found
P12 CI test-gate honesty — no data
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
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 — run tests with `--collect:"XPlat Code Coverage"` (or in CI) to enable this cross-layer check
SC1 Supply-chain hygiene — no data
X5 Nullable reference types — no NRT-eligible projects
X6 Hand-rolled structured-format parsing — no data
X7 Silent fallback defaults — no data
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 CVE: System.Net.Http 4.3.0 — System.Net.Http 4.3.0 (transitive) has a High advisory; affects 43 projects — one upgrade fixes all. 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 43 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Google.Protobuf 3.2.0 — Google.Protobuf 3.2.0 (direct) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.Jit 1.0.2 — Microsoft.NETCore.Jit 1.0.2 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.0.0 — Microsoft.NETCore.App 2.0.0 (direct) has a High advisory; affects 29 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Newtonsoft.Json 9.0.1 — Newtonsoft.Json 9.0.1 (transitive) has a High advisory; affects 29 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
D10 · Test Quality· No assertions (empty test) · ×5
No assertions (empty test): ReadBytes test/DotNetty.Buffers.Tests/SlicedByteBufferTest.cs:27— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): ForEachByteDesc2 test/DotNetty.Buffers.Tests/SlicedByteBufferTest.cs:33— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): ForEachByte2 test/DotNetty.Buffers.Tests/SlicedByteBufferTest.cs:39— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): DuplicateCapacityChange test/DotNetty.Buffers.Tests/SlicedByteBufferTest.cs:45— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): RetainedDuplicateCapacityChange test/DotNetty.Buffers.Tests/SlicedByteBufferTest.cs:51— Test method has an empty body — it asserts nothing and exercises no code.
NoWarnInCsproj repeated across 11 files src/DotNetty.Transport/DotNetty.Transport.csproj:13— The identical NoWarnInCsproj (`CS1591`) appears in 11 files (11 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 11 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
TodoComment src/DotNetty.Buffers/ByteBufferUtil.cs:110— // TODO: maybe use Boyer Moore for efficiency. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PoolArena.cs:68— // TODO: Test if adding padding helps under contention — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PoolChunk.cs:109— // TODO: Test if adding padding helps under contention — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PoolChunkList.cs:27— // TODO: Test if adding padding helps under contention — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PoolSubpage.cs:28— // TODO: Test if adding padding helps under contention — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PoolThreadCache.cs:51— // TODO: Test if adding padding helps under contention — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PoolArena.cs:723— //TODO: Maybe use Memory or OwnedMemory as direct arena/byte buffer type parameter in NETStandard 2.0 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PoolThreadCache.cs:134— // TODO: maybe use cacheSize / cache.length — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PoolThreadCache.cs:168— // todo: revisit this vs IntegerExtensions.(Ceil/Floor)Log2 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Buffers/PooledByteBufferAllocator.cs:64— // todo: Determine reasonable default for heapArenaCount — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Http/HttpObjectDecoder.cs:844— // TODO: Respond with Bad Request and discard the traffic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Http/WebSockets/WebSocket08FrameDecoder.cs:206— // TODO: check if it's bigger than 0x7FFFFFFFFFFFFFFF, Maybe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Http/WebSockets/WebSocketClientHandshaker.cs:241— // TODO: Make handshake work without HttpObjectAggregator at all. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Http/WebSockets/WebSocketServerHandshaker.cs:160— // TODO: Make handshake work without HttpObjectAggregator at all. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Mqtt/MqttDecoder.cs:470— // todo: enforce string definition by MQTT spec — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Mqtt/MqttEncoder.cs:323— // todo: review: validate? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Mqtt/MqttEncoder.cs:396— // todo: review: validate? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Mqtt/MqttEncoder.cs:467— // todo: validate against extra limitations per MQTT's UTF-8 string definition — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs.Protobuf/ProtobufEncoder.cs:32— //todo: Implement ByteBufferStream to avoid allocations. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs/LengthFieldBasedFrameDecoder.cs:11— //TODO: format as XML-DOC — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs/MessageToMessageEncoder.cs:59— // todo: we don't have a stack on EncoderException but it's present on inner exception. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs/MessageToMessageEncoder.cs:75— // todo: optimize: once IChannelHandlerContext allows, pass "not interested in task" flag — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Codecs/Protobuf/ProtobufVarint32FrameDecoder.cs:26— // todo: maxFrameLength + safe skip + fail-fast option (just like LengthFieldBasedFrameDecoder) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Common/Concurrency/AbstractExecutorService.cs:140— // todo: handle fatal — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/DotNetty.Common/Concurrency/ScheduledTask.cs:67— // todo: check for fatal — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
Low cohesion: CorsConfigBuilder (LCOM4 9) src/DotNetty.Codecs.Http/Cors/CorsConfigBuilder.cs:14— CorsConfigBuilder's methods form 9 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: Timer (LCOM4 6) src/DotNetty.Transport.Libuv/Native/Timer.cs:10— Timer's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: SocketDatagramChannel (LCOM4 6) src/DotNetty.Transport/Channels/Sockets/SocketDatagramChannel.cs:20— SocketDatagramChannel's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: AbstractByteBuffer (LCOM4 5) src/DotNetty.Buffers/AbstractByteBuffer.cs:23— AbstractByteBuffer's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: ComposedLastHttpContent (LCOM4 5) src/DotNetty.Codecs.Http/ComposedLastHttpContent.cs:11— ComposedLastHttpContent's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: Pipe (LCOM4 5) src/DotNetty.Transport.Libuv/Native/Pipe.cs:14— Pipe's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: PoolArena (LCOM4 4) src/DotNetty.Buffers/PoolArena.cs:24— PoolArena's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: NativeChannel (LCOM4 4) src/DotNetty.Transport.Libuv/NativeChannel.cs:17— NativeChannel's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: DefaultChannelPipeline (LCOM4 4) src/DotNetty.Transport/Channels/DefaultChannelPipeline.cs:21— DefaultChannelPipeline's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: EmbeddedChannel (LCOM4 4) src/DotNetty.Transport/Channels/Embedded/EmbeddedChannel.cs:17— EmbeddedChannel's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
No assertions: ReaderIndexBoundaryCheck4 test/DotNetty.Buffers.Tests/AbstractByteBufferTests.cs:132— Test method exercises code but verifies nothing — add an assertion.
No assertions: WriterIndexBoundaryCheck4 test/DotNetty.Buffers.Tests/AbstractByteBufferTests.cs:160— Test method exercises code but verifies nothing — add an assertion.
No assertions: DuplicateBytesInArrayMultipleThreads test/DotNetty.Buffers.Tests/AbstractByteBufferTests.cs:2060— Test method exercises code but verifies nothing — add an assertion.
No assertions: SliceBytesInArrayMultipleThreads test/DotNetty.Buffers.Tests/AbstractByteBufferTests.cs:2063— Test method exercises code but verifies nothing — add an assertion.
No assertions: TestNewTimeoutShouldStopThrowingRejectedExecutionExceptionWhenExistingTimeoutIsExecuted test/DotNetty.Common.Tests/Utilities/HashedWheelTimerTest.cs:188— Test method exercises code but verifies nothing — add an assertion.
No assertions: TestReleaseClosed test/DotNetty.Transport.Tests/Channel/Pool/FixedChannelPoolTest.cs:265— Test method exercises code but verifies nothing — add an assertion.
No assertions: ChunkCorrect test/DotNetty.Codecs.Http.Tests/Multipart/HttpPostRequestDecoderTest.cs:250— Test method exercises code but verifies nothing — add an assertion.
XxxComment src/DotNetty.Codecs.Http/Multipart/HttpPostRequestDecoder.cs:63— // Check if Post using "multipart/form-data; boundary=--89421926422648 [; charset=xxx]" — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment src/DotNetty.Codecs.Http/Multipart/HttpPostRequestEncoder.cs:323— // Add Content-Length: xxx — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment src/DotNetty.Codecs.Http/Multipart/HttpPostRequestEncoder.cs:505— // Add Content-Length: xxx — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment src/DotNetty.Common/Concurrency/SingleThreadEventExecutor.cs:430— // XXX: Hard-coded value - will make it configurable if it is really a problem. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment src/DotNetty.Transport.Libuv/LoopExecutor.cs:307— // XXX: Hard-coded value - will make it configurable if it is really a problem. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment test/DotNetty.Buffers.Tests/AbstractCompositeByteBufferTests.cs:225— // XXX Same tests with several buffers in wrappedCheckedBuffer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment test/DotNetty.Buffers.Tests/AbstractCompositeByteBufferTests.cs:386— //XXX Same tests than testEquals with written AggregateChannelBuffers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/DotNetty.Buffers/CompositeByteBuffer.cs:728— // FIXME: No need to create a padding buffer and consolidate. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/DotNetty.Codecs.Http/Multipart/HttpPostMultipartRequestDecoder.cs:1145— // FIXME what do we do here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/DotNetty.Codecs.Http/Multipart/HttpPostMultipartRequestDecoder.cs:1287— // FIXME what do we do here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
Change coupling: DefaultChannelPipeline.cs ↔ EmbeddedEventLoop.cs src/DotNetty.Transport/Channels/DefaultChannelPipeline.cs— `src/DotNetty.Transport/Channels/DefaultChannelPipeline.cs` and `src/DotNetty.Transport/Channels/Embedded/EmbeddedEventLoop.cs` change together 57% of the time (8 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: AbstractChannel.cs ↔ AbstractChannelHandlerContext.cs src/DotNetty.Transport/Channels/AbstractChannel.cs— `src/DotNetty.Transport/Channels/AbstractChannel.cs` and `src/DotNetty.Transport/Channels/AbstractChannelHandlerContext.cs` change together 55% of the time (11 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: AbstractByteBuffer.cs ↔ EmptyByteBuffer.cs src/DotNetty.Buffers/AbstractByteBuffer.cs— `src/DotNetty.Buffers/AbstractByteBuffer.cs` and `src/DotNetty.Buffers/EmptyByteBuffer.cs` change together 50% of the time (13 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
HackComment src/DotNetty.Common/Concurrency/ExecutorTaskScheduler.cs:27— // hack: enables this executor to be seen as default on Executor's worker thread. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
HackComment src/DotNetty.Handlers/Tls/TlsHandler.cs:723— // hack: this tricks SslStream's continuation to run synchronously instead of dispatching to TP. Remove once Begin/EndRead are available. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
Off the main sequence: DotNetty.Handlers(netstandard1.3) — DotNetty.Handlers(netstandard1.3): abstractness 0.07, instability 0.16, distance 0.77 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: DotNetty.Codecs(netstandard1.3) — DotNetty.Codecs(netstandard1.3): abstractness 0.20, instability 0.09, distance 0.71 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Monorepo: only 1 of 2 solutions was scored — This repository contains 2 .NET solutions, but a scan analyzes ONE. Every score, lens, and finding here reflects only `DotNetty.sln` — the other 1 (`examples/UWPEcho.Client/UWPEcho.Client.sln`) were not analyzed and are not represented in the headline. To cover them, scan each solution as its own target and group them in a Solution or Product for a portfolio roll-up. If a secondary solution is an archived or vendored tree, declare it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — to exclude it from discovery the same way generated code is.
D22 · Internal API Consistency· Ambiguous lifecycle and cleanup operations. 'Remove' and 'Destroy' are used interchangeably or in parallel across FastThreadLocal and InternalThreadLocalMap, creating confusion about whether one is for cleanup and the other for removal. · ×1
Ambiguous lifecycle and cleanup operations. 'Remove' and 'Destroy' are used interchangeably or in parallel across FastThreadLocal and InternalThreadLocalMap, creating confusion about whether one is for cleanup and the other for removal. — Unify to a single 'Dispose' or 'Clear' pattern. Use 'Dispose' for full cleanup and 'Clear' for resetting state, removing the ambiguous 'Destroy'/'Remove' duality. (signatures: void FastThreadLocal.RemoveAll() | void FastThreadLocal.Destroy() | void InternalThreadLocalMap.Remove() | void InternalThreadLocalMap.Destroy())
D22 · Internal API Consistency· Inconsistent naming for asynchronous scheduling. 'ScheduleAsync' is used, but the return type is 'Task' rather than 'Task<T>' or 'IScheduledTask', and the naming convention differs from 'SubmitAsync' used in AbstractExecutorService. · ×1
Inconsistent naming for asynchronous scheduling. 'ScheduleAsync' is used, but the return type is 'Task' rather than 'Task<T>' or 'IScheduledTask', and the naming convention differs from 'SubmitAsync' used in AbstractExecutorService. — Standardize on 'SubmitAsync' for fire-and-forget or 'ScheduleAsync' for delayed tasks, but ensure return types are consistent (e.g., all return Task or all return IScheduledTask). (signatures: Task AbstractEventExecutor.ScheduleAsync(...) | Task AbstractEventExecutorGroup.ScheduleAsync(...) | Task AbstractScheduledEventExecutor.ScheduleAsync(...))
D22 · Internal API Consistency· Inconsistent naming for queue insertion. 'TryEnqueue' and 'Offer' are used for similar operations, causing confusion about whether one is non-blocking and the other is blocking or vice versa. · ×1
Inconsistent naming for queue insertion. 'TryEnqueue' and 'Offer' are used for similar operations, causing confusion about whether one is non-blocking and the other is blocking or vice versa. — Standardize on 'TryEnqueue' for all queue implementations to reflect the non-blocking, try-catch pattern common in .NET collections. (signatures: bool IQueue<T>.TryEnqueue(T item) | bool ILinkedQueue<T>.Offer(T e) | bool CompatibleConcurrentQueue<T>.TryEnqueue(T element))
Coverage not measured — test suite did not build — Coverage NOT MEASURED: the repo's own test suite did not build (a C#/MSBuild compiler error in the test code), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. Fix the test build, or commit the Cobertura/OpenCover/lcov report your CI already produces, and real coverage will be measured.
No tests discovered — Test reliability not scored — the test tier(s) built and ran but no tests were discovered, so reliability couldn't be exercised.
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 83k LoC across 85 projects the codebase is both large and multi-module, so its structure warrants explicit bounded-context boundaries. Declare architecture.contexts (≥2) in config to assess cross-boundary type coupling.
redundant comment examples/Discard.Client/DiscardClientHandler.cs:1— "COPYRIGHT (c) Microsoft. All rights reserved." — ignore - repeated boilerplate, not explanatory
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 43 project(s) overshoot their size bounds, lowering Project Cohesion to 9.5/10. The most over is `DotNetty.Codecs.Http(netstandard1.3)` (18416 LoC, 146 public types across 7 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
IL efficiency: 25 authored method(s) exceed the IL budget src/DotNetty.Codecs/Compression/InfBlocks.cs:163— 25 of 7550 first-party methods compile to oversized IL bodies (> 250 instructions); worst: DotNetty.Codecs.Compression.InfBlocks.Proc @ src/DotNetty.Codecs/Compression/InfBlocks.cs:163, 1770 IL instructions; large bodies don't JIT-inline, which pulled this dimension to 9.9/10; splitting the hottest bodies recovers the most.
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.
trivy: not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
osv-scanner: not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
0
—
Run 019f1ec8-7165-7bf8-b4d4-9c1c6a732545 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 23 · Warnings: 456 · Recommendations: 5 · Info: 39 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 01-07-2026 @ 17:44 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.