Hummingbird — Watchdog Audit

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.

guoming/Hummingbird carries serious risk (41%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.

It is strongest in Architecture (85%) — the structure is clean and changes stay contained.

Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.

The area that most needs attention is Readiness (23%) — operating, monitoring and recovering the system safely is harder. Code Health (50%) is the next concern — changes there are slower and more error-prone.

Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); Run what this repository's stack ships (Security & performance tooling); 14 Deprecated finding(s) in Dependency Hygiene (Dependency Hygiene).

For scale: Small (~14,486 production lines); rebuilding it from scratch would take roughly ~0.2 person-years (~1 engineer). 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.

Code Health 50% Weak · gated by D18, X5 Architecture 85% Strong Maturity 55% Adequate · gated by M2 Readiness 23% ⚠ Critical · gated by D8, D12, P1, P3 Security 71% Adequate · gated by D30 Performance 63% Adequate

How the score is built — each lens's share of the headline Width 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.

Readiness 23% · 46% weightCode Health 50% · 25% weightMaturity 55% · 14% weightPerformance 63% · 8% weightSecurity 71% · 4% weightArchitecture 85% · 2% weight

Raise Readiness 23 → 70 (the Healthy floor) ⇒ headline 41 → ~56.

Code composition — where the lines go

Business logic 30%Plumbing 63%Tests 7%

New since the last scan (6+)

6 finding(s) are new versus the previous scan (2026-07-29) — surfaced by this scheduled scan itself, no pull request required.

D24 · LLM evaluation failed
D30 · High CVE: System.Text.Encodings.Web 4.0.0
D30 · High CVE: System.Text.Encodings.Web 4.0.0
D30 · Medium CVE: System.Text.Encodings.Web 4.0.0
D30 · Medium CVE: System.Text.Encodings.Web 4.0.0
D34 · Orphaned knowledge src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs

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.

Rebuild cost & value ~ Modeled — €8,500–€43,000

Cost to rebuild	€8,500–€43,000 (0.1–0.3 person-years (141–454 h), ~1 engineer)
Domain complexity	Low — harder problems cost more per line
Quality factor	0.7× (at 41% quality) — the last 20% of quality is most of the work
Size & shape	Small · 43% boilerplate · 25% straight-line · 32% branching logic

This codebase represents roughly ~0.2 person-years of build effort (about ~€26,000 to rebuild). Its weakest lens is Readiness at 23% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Low (×1.0) — service/app, transaction-script/CRUD × 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.

Resolve the 6 Vulnerable finding(s) in Dependency Hygiene.

+13.3 pts · Low effort · Dependency Hygiene

Resolve the 4 No assertions finding(s) in Test Quality — start with CacheManagerUnitTest.cs (2), ConsulDistributedLockUnitTest.cs, RedisDistributedLockUnitTest.cs.

+9.3 pts · Low effort · Test Quality

Resolve the 2 Banned license finding(s) in License Compliance.

+9.3 pts · Low effort · License Compliance

Diagnosis — what's actually going on

Highest-leverage move: fix the build · Critical · Leverage

The solution doesn't compile, so every Roslyn-derived dimension (complexity, duplication, cohesion, dead code, API surface) ran on incomplete models and is PROVISIONAL. Fixing the build is the single change that makes the rest of the report trustworthy — do it first. The compiler reported: CS0234: The type or namespace name 'Configurations' does not exist in the namespace 'Microsoft.Extensions' (are you missing an assembly reference?).

Evidence: D18 build: The compiler reported: CS0234: The type or namespace name 'Configurations' does not exist in the namespace 'Microsoft.Extensions' (are you missing an assembly reference?).

→ Fix the build, then re-run for a reliable grade.

Value concentrated against a weak lens · High · Value at risk

This is a Small asset (~0.2 person-years to rebuild), and its weakest lens is Readiness at 23%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Small, ~0.2 person-years rebuild (14,486 LoC) · weakest lens: Readiness 23%

→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.

Root cause: tests don't protect the risk · High · Root cause

Coverage is low and what exists is mis-aimed (concentrated on the trivial layer and/or weak on assertions) — the test suite isn't protecting the code that actually carries risk. More of the same tests won't help; the gap is WHERE and HOW you test.

Evidence: D8 coverage: 1.0/10 · D10 test quality: weak assertions

→ Shift testing onto the domain/decision logic; gate on domain coverage, not overall %.

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

49 modules, 46 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.)

At a glance — Code Health · 50% · Weak · gated by D18, X5

The Good

D1 · .NET / C# Cyclomatic Complexity 8.5 D3 · .NET / C# God Classes 9.4 D4 · .NET / C# Code Duplication 9.8 D17 · .NET / C# Explicit Debt 9.3 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.4

The Bad

D2 · .NET / C# Cognitive Complexity 6.6 X1 · Repo Async correctness 6.7 X2 · Repo Cancellation propagation 6.5 X3 · Repo Exception handling 5.3 X4 · Repo Structured logging 5.0

The Ugly

D18 · .NET / C# Solution Shape 3.0 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 85% · Strong

The Good

D5 · .NET / C# Coupling 9.9 D6 · .NET / C# Cohesion (LCOM4) 9.5 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 8.2 D35 · .NET / C# Change Coupling 9.8 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 9.3 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.8 AX8 · Repo Test isolation 10.0

The Bad

AX2 · Repo Stateful singletons 5.9

At a glance — Maturity · 55% · Adequate · gated by M2

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 9.8 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

D19 · .NET / C# Documentation Quality 6.0 D34 · .NET / C# Knowledge Freshness 5.9 M1 · Repo Documentation (README) 6.0

The Ugly

D21 · .NET / C# Naming Consistency 3.5 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 23% · Critical · gated by D8, D12, P1, P3

The Good

D9 · .NET / C# Test Distribution 10.0 D13 · .NET / C# Secret Scanning 10.0 P2 · Repo Observability 8.2 P7 · Repo Outbound HTTP resilience 10.0

The Bad

D14 · .NET / C# License Compliance 6.0 P10 · Repo Library API & versioning 6.0 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0 P8 · Repo Schema migrations 6.0

The Ugly

D8 · .NET / C# Code Coverage 1.0 D10 · .NET / C# Test Quality 4.0 D12 · .NET / C# Dependency Hygiene 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 71% · Adequate · gated by D30

The Good

D28 · .NET / C# Secrets (history) 7.0 D29 · .NET / C# Static Analysis (SAST) 8.6 D31 · .NET / C# IaC & Container Security 10.0 S1 · Repo Cryptographic Hygiene 8.0

The Ugly

D30 · .NET / C# Dependency Vulnerabilities 0.0

At a glance — Performance · 63% · Adequate

The Bad

PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 6.9 PF3 · Repo Async & latency hygiene 6.1

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A06:2021 — Vulnerable & Outdated Components	50	High / Critical
A02:2021 — Cryptographic Failures	4	High / Critical
A03:2021 — Injection	3	Medium

Roadmap

First, establish a CI/CD pipeline that builds the code and runs the test suite on every push or pull request. Integrate security and performance tooling, such as CodeQL or Semgrep, into this workflow to ensure security regressions fail the build. Next, address the 14 deprecated dependencies to improve hygiene. Finally, implement readiness and liveness probes with a rolling-update strategy to enable automatic rollback, and maintain a changelog to track each release.

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

Do this	Helps	Effort	Dimension
Resolve the 6 Vulnerable finding(s) in Dependency Hygiene.	+13.3 pts	Low	Dependency Hygiene
Resolve the 4 No assertions finding(s) in Test Quality — start with CacheManagerUnitTest.cs (2), ConsulDistributedLockUnitTest.cs, RedisDistributedLockUnitTest.cs.	+9.3 pts	Low	Test Quality
Resolve the 2 Banned license finding(s) in License Compliance.	+9.3 pts	Low	License Compliance
Add a CI workflow that builds and runs the test suite on every push/PR.	+16.5 pts	Medium	CI/CD gates
Run 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 — — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.	+16.5 pts	Medium	Security & performance tooling
Resolve the 14 Deprecated finding(s) in Dependency Hygiene.	+16.3 pts	Medium	Dependency Hygiene
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.	+15.6 pts	Medium	Deployment & Rollback
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.	+15.6 pts	Medium	Release Hygiene

File quality

Per-file score 0–10 — a quality signature. Of 64 files carrying findings, judged against the Production bar: 3% slop · 13% mixed · 84% near-clean.

File	Score	Band	Worst signal
src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs	2.7	Slop	Explicit Debt: EmptyCatchBlock
src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs	3.5	Slop	Explicit Debt: EmptyCatchBlock
Sample/Hummingbird.WebApi/Startup.cs	5.1	Mixed	Secrets (history): Secret: generic-api-key
src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs	7.2	Mixed	Cyclomatic Complexity: ConsulServiceDiscoveryProvider.Init (cyclomatic 16)
src/Hummingbird.Extensions.Cacheing/StackExchange/RedisCacheManage.cs	7.4	Mixed	Cyclomatic Complexity: RedisCacheManage.Create (cyclomatic 16)
src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceLocator.cs	7.8	Mixed	Cognitive Complexity: ConsulServiceLocator.GetAsync (cognitive 16)
test/Hummingbird.Extensions.Cacheing.UnitTest/CacheManagerUnitTest.cs	7.8	Mixed	Test Quality: No assertions: Test1
example/Hummingbird.Example/Controllers/BaseController.cs	7.9	Mixed	Static Analysis (SAST): Medium: missing-or-broken-authorization
example/Hummingbird.Example/Controllers/DistribuctedLockController.cs	7.9	Mixed	Static Analysis (SAST): Medium: missing-or-broken-authorization
example/Hummingbird.Example/Controllers/HttpController.cs	7.9	Mixed	Static Analysis (SAST): Medium: missing-or-broken-authorization
src/Hummingbird.Extensions.HealthChecks.SqlServer/HealthCheckBuilderSqlServerExtensions.cs	8.2	Near-clean	Explicit Debt: TodoComment
src/Hummingbird.Extensions.UidGenerator.ConsulWorkIdStrategy/ConsulWorkIdCreateStrategy.cs	8.5	Near-clean	Cognitive Complexity: ConsulWorkIdCreateStrategy.CreateWorkId (cognitive 39)
src/Hummingbird.Extensions.Canal/Formatters/MaxwellJson/MaxwellJsonFormatter.cs	8.5	Near-clean	Cognitive Complexity: Formatter.Format (cognitive 24)
src/Hummingbird.Extensions.Resilience.Http/Implements/UrlResolver.cs	8.5	Near-clean	Cognitive Complexity: HttpUrlResolver.Resolve (cognitive 21)
src/Hummingbird.Extensions.Quartz/CornJobSchedulerHostedService.cs	8.5	Near-clean	Cognitive Complexity: CornJobSchedulerHostedService.StartAsync (cognitive 20)
src/Hummingbird.Extensions.Canal/Internal/CanalClientHostedService.cs	8.5	Near-clean	Cognitive Complexity: CanalClientHostedService.StartAsync (cognitive 17)
src/Hummingbird.Extensions.FileSystem.Oss/StaticFiles/OssStaticFileMiddleware.cs	8.5	Near-clean	Cognitive Complexity: OssStaticFileMiddleware.Invoke (cognitive 17)
src/Hummingbird.Extensions.Cacheing/StackExchange/RedisClientHelper.cs	8.5	Near-clean	God Classes: TooManyMethods: RedisClientHelper
src/Hummingbird.Extensions.HealthChecks/Checks/NumericChecks.cs	8.5	Near-clean	Code Duplication: Duplicated block (9 lines × 2)
src/Hummingbird.Extensions.EventBus.RabbitMQ/Extersions/DependencyInjectionExtersion.cs	8.5	Near-clean	Cohesion (LCOM4): Low cohesion: RabbitMqOption (LCOM4 5)

Methodology & how to trust this report

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. 54 of 56 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 56 dimensions across the health lenses

D1D2D3D4D5D6D8D9D10D12D13D14D15D16D17D18D19D21D26D27D28D29D30D31D34D35AX1AX10AX2AX3AX5AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P6P7P8PF1PF2PF3S1X1X2X3X4X5

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, 89 of 243 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
jscpd	Code duplication	—	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.302	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.302	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 019fc7fe-0177-7319-987b-543e27fbd0ba.

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

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D24 Comment Value — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.

Repo exclusion declarations (.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 (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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
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.
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.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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 (3): D19, D21, 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.

Dimensions

D1 · Cyclomatic Complexity8.5 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EventBusKafka.RegisterBatch at 38.

EventBusKafka.RegisterBatch (cyclomatic 38)src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:546

EventBusRabbitMQ.RegisterBatch (cyclomatic 35)src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:581

EventBusKafka.Register (cyclomatic 28)src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:258

EventBusRabbitMQ.Register (cyclomatic 27)src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:311

RedisCacheManage.Create (cyclomatic 16)src/Hummingbird.Extensions.Cacheing/StackExchange/RedisCacheManage.cs:55

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

What to do

Resolve the 1 EventBusKafka.RegisterBatch (cyclomatic 38) finding(s) in Cyclomatic Complexity — start with EventBusKafka.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 EventBusRabbitMQ.RegisterBatch (cyclomatic 35) finding(s) in Cyclomatic Complexity — start with EventBusRabbitMQ.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 EventBusKafka.Register (cyclomatic 28) finding(s) in Cyclomatic Complexity — start with EventBusKafka.cs. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

Do you agree with this assessment?

D2 · Cognitive Complexity6.6 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

14 method(s) exceeded the cognitive complexity threshold of 15; the worst was EventBusRabbitMQ.RegisterBatch at 131.

EventBusRabbitMQ.RegisterBatch (cognitive 131)src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:581

EventBusKafka.RegisterBatch (cognitive 120)src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:546

EventBusKafka.Register (cognitive 78)src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:258

RedisCacheManage.Create (cognitive 70)src/Hummingbird.Extensions.Cacheing/StackExchange/RedisCacheManage.cs:55

EventBusRabbitMQ.Register (cognitive 53)src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:311

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

What to do

Resolve the 1 EventBusRabbitMQ.RegisterBatch (cognitive 131) finding(s) in Cognitive Complexity — start with EventBusRabbitMQ.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 EventBusKafka.RegisterBatch (cognitive 120) finding(s) in Cognitive Complexity — start with EventBusKafka.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 EventBusKafka.Register (cognitive 78) finding(s) in Cognitive Complexity — start with EventBusKafka.cs. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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 Classes9.4 / 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.

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

2 god class(es) detected.

TooManyMethods: RedisClientHelper · ×2src/Hummingbird.Extensions.Cacheing/StackExchange/RedisClientHelper.cs:0

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D4 · Code Duplication9.8 / 10Exemplary✓ Tool-verified

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.

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

5 duplicated block group(s) detected.

Duplicated block (6 lines × 2) · ×2src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:315

Duplicated block (11 lines × 2)src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceLocator.cs:129

Duplicated block (9 lines × 2)src/Hummingbird.Extensions.HealthChecks/Checks/NumericChecks.cs:22

Duplicated block (8 lines × 2)src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs:340

✓ 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.9 / 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.

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

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

Off the main sequence: Hummingbird.Extensions.HealthChecks(netstandard2.0)

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

2 of 50 classes have LCOM4 above 3.

Low cohesion: RabbitMqOption (LCOM4 5) · ×2src/Hummingbird.Extensions.EventBus.RabbitMQ/Extersions/DependencyInjectionExtersion.cs:16

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D8 · Code Coverage1.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

Line coverage 0.0%, branch coverage 0.0%.

What to do

Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d8_recommendation.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.

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

7 test methods: 7 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 Quality4.0 / 10Weak✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 10 tests.

No assertions: Test1 · ×4test/Hummingbird.Extensions.Cacheing.UnitTest/CacheManagerUnitTest.cs:10

What to do

Resolve the 4 No assertions finding(s) in Test Quality — start with CacheManagerUnitTest.cs (2), ConsulDistributedLockUnitTest.cs, RedisDistributedLockUnitTest.cs. — One of this dimension's main actionable groups (4 warning-level).
Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D12 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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.

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

68 outdated, 6 vulnerable, 14 deprecated packages.

Vulnerable: Microsoft.NETCore.App · ×6

Deprecated: Microsoft.NETCore.App · ×14

Outdated: Microsoft.AspNetCore.Http.Abstractions · ×68

What to do

Resolve the 14 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 6 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (6 issue-level).
Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

2 of 77 packages use a banned license.

Banned license: DumpExtensions · ×2

What to do

Resolve the 2 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (2 issue-level).
Stand up a CI pipeline, then gate License Compliance in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D16 · Bus Factor9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs.

Off-boarding risk: anonymized user #1

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D17 · Explicit Debt9.3 / 10Exemplary✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

7 deducted debt markers + 0 dead symbols across 14486 LoC (0.4/KLoC) → score 9.3.

EmptyCatchBlock · ×6src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:318

TodoCommentsrc/Hummingbird.Extensions.HealthChecks.SqlServer/HealthCheckBuilderSqlServerExtensions.cs:27

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D18 · Solution Shape3.0 / 10Weak✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

67 projects, 346 source files, 15611 hand-written lines of code (14486 production / 1125 test), 132 inter-project edges (build failed).

Build failed

What to do

Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D19 · Documentation Quality / 10Adequate◐ Sampled · advisory

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.

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

Hummingbird's README is a single-file project description with an outline that lists every documented feature (distributed locks, caches, distributed IDs, tracing, message brokers, health checks, load balancing, config centers, service discovery, HTTP clients, Canal, OSS, and more) plus a dedicated 4.1-4.12 deployment section covering Consul/Apollo/Mysql/Redis/Elasticsearch/Kafka/RabbitMQ/Grafana/InfluxDB/Jaeger/Canal/Nacos docker stacks. The body is clipped mid-3.7 (distributed lock test code), so the detailed usage of each feature and a 4.x environment setup are not shown, but the outline is complete and every listed section exists; this leaves room for quality over the visible content.

Low XML-doc coverage: Hummingbird.Core(netcoreapp2.2) · ×39src/Hummingbird.Core/Hummingbird.Core.csproj

XML-doc coverage: Hummingbird.Extensions.Cacheing(net4.6.1)src/Hummingbird.Extensions.Cacheing/Hummingbird.Extensions.Cacheing.csproj

What to do

Resolve the 39 Low XML-doc coverage finding(s) in Documentation Quality — start with Hummingbird.Core.csproj, Hummingbird.Extensions.UidGenerator.csproj, Hummingbird.Extensions.Idempotency.csproj. — One of this dimension's main actionable groups (39 warning-level).

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

Do you agree with this assessment?

D21 · Naming Consistency / 10Weak◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

5 naming inconsistencies across 200 sampled symbols.

Inconsistent namespace/implementation naming for Redis cache components. One class is named 'RedisCacheManage' (implying a manager/handler) while the other is 'RedisClientHelper' (implying a utility/helper). They appear to be related components within the same 'Cacheing' feature area but use different suffixes ('Manage' vs 'Helper') and are split across different namespaces ('StackExchangeImplement' vs 'StackExchangeImplement' - wait, they are in the same namespace but different classes). More critically, there is a third class 'RedisConnectionHelp' (typo: Help vs Helper) and 'RedisCacheManage' vs 'RedisClientHelper'. The inconsistency is between 'Manage' and 'Helper' suffixes for similar Redis interaction classes.

Typo in the word 'Extensions' in the namespace or class name. The namespace is 'Hummingbird.Extensions.EventBus.Kafka' but the class is 'EventLogEntryExtersions' (missing 'n' in Extensions). This typo is repeated across multiple classes in different namespaces (Kafka, RabbitMQ).

Typo in the word 'Extension' in the class name. The class is named 'DependencyInjectionExtersion' (missing 'n' in Extension). This typo is present in all extension classes in this codebase.

Inconsistent naming for Redis-related classes. 'RedisCacheManage' uses 'Manage' (likely meant Manager), 'RedisClientHelper' uses 'Helper', and 'RedisConnectionHelp' has a typo ('Help' instead of 'Helper' or 'Manager'). The suffixes 'Manage', 'Helper', and 'Help' are used inconsistently for similar Redis interaction classes.

Typo in the namespace 'Abastracts' (missing 'c' in Abstracts).

What to do

Resolve the 1 Inconsistent namespace/implementation naming for Redis cache components.… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Typo in the word 'Extensions' in the namespace or class name. The… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Typo in the word 'Extension' in the class name. The class is named… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 45 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D27 · Navigability8.2 / 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.

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

67 % of calls cross a namespace and 13 % go through an interface, but 93 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

What to do

Improve Navigability — currently 8.2/10. — 67 % of calls cross a namespace and 13 % go through an interface, but 93 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)7.0 / 10Strong✓ Tool-verified

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.

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

3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

Secret: generic-api-key · ×3Sample/Hummingbird.WebApi/Startup.cs:29detected by gitleaks finding

Rotate the exposed credentials — git history can't be un-committed

What to do

Resolve the 3 Secret finding(s) in Secrets (history) — start with Startup.cs (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)8.6 / 10Strong✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

3 finding(s): 0 critical, 0 high, 3 medium, 0 low.

Medium: missing-or-broken-authorization · ×3example/Hummingbird.Example/Controllers/BaseController.cs:11detected by semgrep finding

What to do

Resolve the 3 Medium finding(s) in Static Analysis (SAST) — start with BaseController.cs, DistribuctedLockController.cs, HttpController.cs. — One of this dimension's main actionable groups (3 warning-level).

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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.

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

51 vulnerable package(s): 4 critical, 31 high, 16 medium, 0 low.

High CVE: Microsoft.NETCore.App 2.2.0 · ×31detected by dotnet list package --vulnerable

Critical CVE: System.Text.Encodings.Web 4.5.0 · ×4detected by dotnet list package --vulnerable

Medium CVE: Microsoft.NETCore.App 2.2.0 · ×15detected by dotnet list package --vulnerable

What to do

Resolve the 31 High CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (31 issue-level).
Resolve the 15 Medium CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (4 issue-level).

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

Do you agree with this assessment?

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

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

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

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

trivy found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

Do you agree with this assessment?

D34 · Knowledge Freshness5.9 / 10Adequate✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

27 of 66 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs.

Orphaned knowledgesrc/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs

Further orphaned files (smaller)

What to do

Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with EventBusRabbitMQ.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.

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

Strongest change-coupling: ResilientHttpClient.cs↔StandardHttpClient.cs 73%; KafkaBatchingExtensions.cs↔EventBusKafka.cs 61%

Change coupling: ResilientHttpClient.cs ↔ StandardHttpClient.cs · ×2src/Hummingbird.Extensions.Resilience.Http/Implements/ResilientHttpClient.cs

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

Do you agree with this assessment?

AX10 · Code composition9.3 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.

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

Do you agree with this assessment?

AX2 · Stateful singletons5.9 / 10Adequate✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

`EventBusRabbitMQ` is a singleton (one shared instance) but mutates instance state outside any lock (_subscribeAckHandler, _subscribeNackHandler; e.g. `_subscribeAckHandler` at line 867). — EventBusRabbitMQ.cs:29
`ConsulConfig` is a singleton (one shared instance) but mutates instance state outside any lock (SERVICE_REGISTRY_ADDRESS, SERVICE_REGISTRY_PORT, SERVICE_SELF_REGISTER, SERVICE_REGION, SERVICE_NAME, SERVICE_CHECK_HTTP; e.g. `SERVICE_REGISTRY_ADDRESS` at line 81). — ConsulConfig.cs:9
`EventBusKafka` is a singleton (one shared instance) but mutates instance state outside any lock (_subscribeAckHandler, _subscribeNackHandler; e.g. `_subscribeAckHandler` at line 841). — EventBusKafka.cs:29

What to do

Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.

Do you agree with this assessment?

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

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

Do you agree with this assessment?

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

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

AX6 · Interface segregation9.8 / 10Exemplary✓ Tool-verified

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.

`ICacheManager` declares 67 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. — ICacheManager.cs:8

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

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

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

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

A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — OssFileProvider.cs:56, OssFileProvider.cs:177, OssStaticFileMiddleware.cs:118

What to do

Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.

Do you agree with this assessment?

IC1 · Incompleteness & stubs7.4 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

`StartAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — CanalClientHostedService.cs:31, ConsulServiceRegisterHostedService.cs:41
`Enqueue` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — EventBusKafka.cs:191
`GetDirectoryContents` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — OssFileProvider.cs:54
`Watch` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — OssFileProvider.cs:175
`UploadAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — PhysicalFileSystemBucket.cs:16
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×11) — HashAlgorithm.cs:30, HashAlgorithm.cs:31, RedisClientHelper.cs:352, …

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.

Do you agree with this assessment?

M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

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 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 45 of 45 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — no conventional ADR directory, no `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.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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 gates0.0 / 10Critical✓ 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.

No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

Add a CI workflow that builds and runs the test suite on every push/PR.

Do you agree with this assessment?

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries. Exhaustive, deterministic.

279/351 types (79%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.

What to do

Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.

Do you agree with this assessment?

P2 · Observability8.2 / 10Strong✓ Tool-verified

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

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

Only 12/29 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 29, 0 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build.

What to do

Run 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 — — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

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.

Do you agree with this assessment?

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

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

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

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

What to do

Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

Do you agree with this assessment?

P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Roslyn scan: Polly resilience markers (Retry, CircuitBreaker, Timeout) on outbound HTTP invocations. Computed per type, deterministic.

Do you agree with this assessment?

P8 · Schema migrations6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage. Exhaustive per project, deterministic.

EF Core is used but neither migrations nor EnsureCreated were detected — confirm how the production schema is created and evolved.

What to do

Adopt a versioned schema-migration mechanism (with EF Core: dotnet ef migrations add + Migrate() on startup) as the explicit, versioned schema strategy — no migration mechanism was detected.

Do you agree with this assessment?

PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

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.

No benchmark suite was found. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).

Do you agree with this assessment?

PF2 · Allocation hygiene6.9 / 10Adequate✓ Tool-verified

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.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit. Reward-only. Deterministic, syntax/text detection.

What to do

Raise allocation-aware density on the hot paths — currently 29 use(s) across 15,839 production line(s) (~1.8/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.

Do you agree with this assessment?

PF3 · Async & latency hygiene6.1 / 10Adequate✓ Tool-verified

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.

Only 8/216 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

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.

Do you agree with this assessment?

S1 · Cryptographic Hygiene8.0 / 10Strong✓ Tool-verified

Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. Deterministic.

MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — HashAlgorithm.cs:26

What to do

Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.

Do you agree with this assessment?

X1 · Async correctness6.7 / 10Adequate✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×4) — ConsulServiceDiscoveryProvider.cs:235, ConsulServiceDiscoveryProvider.cs:338, ConsulServiceDiscoveryProvider.cs:365, …

What to do

async void method: Heartbeat

Do you agree with this assessment?

X2 · Cancellation propagation6.5 / 10Adequate✓ Tool-verified

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 37/88 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. (×25) — HttpResponseMessageExtensions.cs:12, ResilientHttpClient.cs:381, RedisClientHelper.cs:73, …

What to do

Thread a CancellationToken through async methods so work stops promptly on cancellation.

Do you agree with this assessment?

X3 · Exception handling5.3 / 10Adequate✓ Tool-verified

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

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

`throw ex;` 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) — EventBusRabbitMQ.cs:296, EventBusKafka.cs:242
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) — EventBusRabbitMQ.cs:392, EventBusRabbitMQ.cs:700, EventBusKafka.cs:318, …
`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. — JsonConfigurationParser.cs:49

What to do

Rethrow loses stack trace (`throw ex;`)

Do you agree with this assessment?

X4 · Structured logging5.0 / 10Adequate✓ Tool-verified

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.

Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×20) — DependencyInjectionExtersion.cs:74, DependencyInjectionExtersion.cs:81, EventBusRabbitMQ.cs:539, …

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

0/3 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.

Lens	Score	Rating	Impact
Code Health	50%	Weak — gated by D18, X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	85%	Strong	Strongest area.
Maturity	55%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	23%	Critical — gated by D8, D12, P1, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	71%	Adequate — gated by D30	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	63%	Adequate	Acceptable, with room to improve.

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.
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
D11 Test Reliability — Test runner surfaced no tests
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.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D24 Comment Value — LLM evaluation failed
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — Data compliance (PII/GDPR) was not assessed in this scan — no ruleset is currently available for it. This says nothing about how this repository handles personal data, in either direction.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
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 — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
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 (a message-bus package)
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 — no CI workflow found
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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
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.

Issue — 53 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×31

High CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a High advisory; affects 10 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a High advisory; affects 10 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Newtonsoft.Json 12.0.1 — Newtonsoft.Json 12.0.1 (direct) has a High advisory; affects 9 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.Http 2.1.1 — Microsoft.AspNetCore.Http 2.1.1 (direct) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Newtonsoft.Json 12.0.2 — Newtonsoft.Json 12.0.2 (transitive) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.1.0 — Microsoft.NETCore.App 2.1.0 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.1.0 — Microsoft.NETCore.App 2.1.0 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.1.0 — Microsoft.NETCore.App 2.1.0 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.1.0 — Microsoft.NETCore.App 2.1.0 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Data.SqlClient 4.4.0 — System.Data.SqlClient 4.4.0 (transitive) has a High advisory; affects 3 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 9 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: MongoDB.Driver 2.4.4 — MongoDB.Driver 2.4.4 (direct) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Security 4.0.0 — System.Net.Security 4.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Security 4.0.0 — System.Net.Security 4.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.X509Certificates 4.1.0 — System.Security.Cryptography.X509Certificates 4.1.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. 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; affects 9 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 11 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Newtonsoft.Json 11.0.2 — Newtonsoft.Json 11.0.2 (transitive) has a High advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.Http 1.0.2 — Microsoft.AspNetCore.Http 1.0.2 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Text.Encodings.Web 4.0.0 — System.Text.Encodings.Web 4.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Text.Encodings.Web 4.0.0 — System.Text.Encodings.Web 4.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Data.SqlClient 4.3.0 — System.Data.SqlClient 4.3.0 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Security 4.3.0 — System.Net.Security 4.3.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Security 4.3.0 — System.Net.Security 4.3.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Newtonsoft.Json 10.0.2 — Newtonsoft.Json 10.0.2 (transitive) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
+ 6 more in this group — see findings.md.

D12 · Dependency Hygiene · Vulnerable · ×6

Vulnerable: Microsoft.NETCore.App — Microsoft.NETCore.App [2.2.0, — ) severity. 2.2.0
Vulnerable: Newtonsoft.Json — Newtonsoft.Json 12.0.1 — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: Microsoft.AspNetCore.Http — Microsoft.AspNetCore.Http 2.1.1 — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: MongoDB.Driver — MongoDB.Driver 2.4.4 — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: System.Data.SqlClient — System.Data.SqlClient 4.3.0 — Moderate severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: Microsoft.Extensions.Caching.Memory — Microsoft.Extensions.Caching.Memory 8.0.0 — High severity. https://github.com/advisories/[GHSA redacted]

D17 · Explicit Debt · EmptyCatchBlock · ×6

EmptyCatchBlock src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:318 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:328 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:628 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:637 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:392 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:700 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.

D30 · Dependency Vulnerabilities · Critical CVE · ×4

Critical CVE: System.Text.Encodings.Web 4.5.0 — System.Text.Encodings.Web 4.5.0 (transitive) has a Critical advisory; affects 19 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Critical CVE: System.Text.Encodings.Web 4.0.0 — System.Text.Encodings.Web 4.0.0 (transitive) has a Critical advisory. https://github.com/advisories/[GHSA redacted]
Critical CVE: System.Text.Encodings.Web 4.6.0 — System.Text.Encodings.Web 4.6.0 (transitive) has a Critical advisory. https://github.com/advisories/[GHSA redacted]
Critical CVE: System.Drawing.Common 4.7.0 — System.Drawing.Common 4.7.0 (transitive) has a Critical advisory. https://github.com/advisories/[GHSA redacted]

D28 · Secrets (history) · Secret · ×3

Secret: generic-api-key Sample/Hummingbird.WebApi/Startup.cs:29 — matched rule 'generic-api-key'
Secret: generic-api-key Sample/Hummingbird.WebApi/Startup.cs:122 — matched rule 'generic-api-key'
Secret: generic-api-key Sample/Hummingbird.WebApi/Startup.cs:29 — matched rule 'generic-api-key'

D14 · License Compliance · Banned license · ×2

Banned license: DumpExtensions — DumpExtensions 2.0.0 is licensed GPL-3.0-only (banned by policy).
Banned license: MySql.Data — MySql.Data 8.0.32.1 is licensed GPL-2.0-only (banned by policy).

D34 · Knowledge Freshness · Orphaned knowledge · ×1

Orphaned knowledge src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.

Warning — 110 finding(s)

D19 · Documentation Quality · Low XML-doc coverage · ×39

Low XML-doc coverage: Hummingbird.Core(netcoreapp2.2) src/Hummingbird.Core/Hummingbird.Core.csproj — Hummingbird.Core(netcoreapp2.2): 9 % XML-doc coverage (1/11).
Low XML-doc coverage: Hummingbird.Extensions.UidGenerator(netcoreapp2.2) src/Hummingbird.Extensions.UidGenerator/Hummingbird.Extensions.UidGenerator.csproj — Hummingbird.Extensions.UidGenerator(netcoreapp2.2): 8 % XML-doc coverage (3/39).
Low XML-doc coverage: Hummingbird.Extensions.Idempotency src/Hummingbird.Extensions.Idempotency/Hummingbird.Extensions.Idempotency.csproj — Hummingbird.Extensions.Idempotency: 17 % XML-doc coverage (3/18).
Low XML-doc coverage: Hummingbird.Extensions.Resilience.Http src/Hummingbird.Extensions.Resilience.Http/Hummingbird.Extensions.Resilience.Http.csproj — Hummingbird.Extensions.Resilience.Http: 12 % XML-doc coverage (5/42).
Low XML-doc coverage: Hummingbird.Extensions.EventBus(netcoreapp2.2) src/Hummingbird.Extensions.EventBus/Hummingbird.Extensions.EventBus.csproj — Hummingbird.Extensions.EventBus(netcoreapp2.2): 37 % XML-doc coverage (14/38).
Low XML-doc coverage: Hummingbird.Extensions.EventBus.RabbitMQ src/Hummingbird.Extensions.EventBus.RabbitMQ/Hummingbird.Extensions.EventBus.RabbitMQ.csproj — Hummingbird.Extensions.EventBus.RabbitMQ: 44 % XML-doc coverage (23/52).
Low XML-doc coverage: Hummingbird.Extensions.Cache(netcoreapp2.1) src/Hummingbird.Extensions.Cache/Hummingbird.Extensions.Cache.csproj — Hummingbird.Extensions.Cache(netcoreapp2.1): 8 % XML-doc coverage (2/26).
Low XML-doc coverage: Hummingbird.Extensions.EventBus.SqlServerLogging src/Hummingbird.Extensions.EventBus.SqlServerLogging/Hummingbird.Extensions.EventBus.SqlServerLogging.csproj — Hummingbird.Extensions.EventBus.SqlServerLogging: 19 % XML-doc coverage (3/16).
Low XML-doc coverage: Hummingbird.Extensions.DistributedLock(netstandard2.0) src/Hummingbird.Extensions.DistributedLock/Hummingbird.Extensions.DistributedLock.csproj — Hummingbird.Extensions.DistributedLock(netstandard2.0): 0 % XML-doc coverage (0/8).
Low XML-doc coverage: Hummingbird.Extensions.HealthChecks.Redis src/Hummingbird.Extensions.HealthChecks.Redis/Hummingbird.Extensions.HealthChecks.Redis.csproj — Hummingbird.Extensions.HealthChecks.Redis: 0 % XML-doc coverage (0/8).
Low XML-doc coverage: Hummingbird.Extensions.HealthChecks.MongoDb src/Hummingbird.Extensions.HealthChecks.MongoDb/Hummingbird.Extensions.HealthChecks.MongoDb.csproj — Hummingbird.Extensions.HealthChecks.MongoDb: 0 % XML-doc coverage (0/8).
Low XML-doc coverage: Hummingbird.Extensions.EventBus.MySqlLogging src/Hummingbird.Extensions.EventBus.MySqlLogging/Hummingbird.Extensions.EventBus.MySqlLogging.csproj — Hummingbird.Extensions.EventBus.MySqlLogging: 25 % XML-doc coverage (4/16).
Low XML-doc coverage: Hummingbird.Extensions.Configuration.Json src/Hummingbird.Extensions.Configuration.Json/Hummingbird.Extensions.Configuration.Json.csproj — Hummingbird.Extensions.Configuration.Json: 0 % XML-doc coverage (0/22).
Low XML-doc coverage: Hummingbird.Extensions.HealthChecks(netstandard2.0) src/Hummingbird.Extensions.HealthChecks/Hummingbird.Extensions.HealthChecks.csproj — Hummingbird.Extensions.HealthChecks(netstandard2.0): 9 % XML-doc coverage (12/129).
Low XML-doc coverage: Hummingbird.AspNet.HealthChecks(net46) src/Hummingbird.AspNet.HealthChecks/Hummingbird.AspNet.HealthChecks.csproj — Hummingbird.AspNet.HealthChecks(net46): 0 % XML-doc coverage (0/15).
Low XML-doc coverage: Hummingbird.AspNetCore.HealthChecks src/Hummingbird.AspNetCore.HealthChecks/Hummingbird.AspNetCore.HealthChecks.csproj — Hummingbird.AspNetCore.HealthChecks: 0 % XML-doc coverage (0/22).
Low XML-doc coverage: Hummingbird.Extensions.HealthChecks.SqlServer src/Hummingbird.Extensions.HealthChecks.SqlServer/Hummingbird.Extensions.HealthChecks.SqlServer.csproj — Hummingbird.Extensions.HealthChecks.SqlServer: 0 % XML-doc coverage (0/8).
Low XML-doc coverage: Hummingbird.Extensions.HealthChecks.MySql src/Hummingbird.Extensions.HealthChecks.MySql/Hummingbird.Extensions.HealthChecks.MySql.csproj — Hummingbird.Extensions.HealthChecks.MySql: 0 % XML-doc coverage (0/8).
Low XML-doc coverage: Hummingbird.Extensions.HealthChecks.Rabbitmq src/Hummingbird.Extensions.HealthChecks.Rabbitmq/Hummingbird.Extensions.HealthChecks.Rabbitmq.csproj — Hummingbird.Extensions.HealthChecks.Rabbitmq: 25 % XML-doc coverage (3/12).
Low XML-doc coverage: Hummingbird.Extensions.OpenTracing src/Hummingbird.Extensions.OpenTracing/Hummingbird.Extensions.OpenTracing.csproj — Hummingbird.Extensions.OpenTracing: 0 % XML-doc coverage (0/19).
Low XML-doc coverage: Hummingbird.LoadBalancers(net4.6.1) src/Hummingbird.LoadBalancers/Hummingbird.LoadBalancers.csproj — Hummingbird.LoadBalancers(net4.6.1): 0 % XML-doc coverage (0/13).
Low XML-doc coverage: Hummingbird.Extensions.DynamicRoute.Consul(netcoreapp2.2) src/Hummingbird.Extensions.DynamicRoute.Consul/Hummingbird.Extensions.DynamicRoute.Consul.csproj — Hummingbird.Extensions.DynamicRoute.Consul(netcoreapp2.2): 36 % XML-doc coverage (15/42).
Low XML-doc coverage: Hummingbird.DynamicRoute src/Hummingbird.DynamicRoute/Hummingbird.DynamicRoute.csproj — Hummingbird.DynamicRoute: 0 % XML-doc coverage (0/7).
Low XML-doc coverage: Hummingbird.Extensions.EventBus.Kafka src/Hummingbird.Extensions.EventBus.Kafka/Hummingbird.Extensions.EventBus.Kafka.csproj — Hummingbird.Extensions.EventBus.Kafka: 37 % XML-doc coverage (20/54).
Low XML-doc coverage: Hummingbird.Extensions.UidGenerator.ConsulWorkIdStrategy(netcoreapp2.2) src/Hummingbird.Extensions.UidGenerator.ConsulWorkIdStrategy/Hummingbird.Extensions.UidGenerator.ConsulWorkIdStrategy.csproj — Hummingbird.Extensions.UidGenerator.ConsulWorkIdStrategy(netcoreapp2.2): 31 % XML-doc coverage (4/13).
+ 14 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Medium CVE · ×15

Medium CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a Medium advisory; affects 10 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.NETCore.App 2.1.0 — Microsoft.NETCore.App 2.1.0 (direct) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.NETCore.App 2.1.0 — Microsoft.NETCore.App 2.1.0 (direct) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.NETCore.App 2.1.0 — Microsoft.NETCore.App 2.1.0 (direct) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.NETCore.App 2.1.0 — Microsoft.NETCore.App 2.1.0 (direct) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Data.SqlClient 4.4.0 — System.Data.SqlClient 4.4.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Net.Security 4.0.0 — System.Net.Security 4.0.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Net.Security 4.0.0 — System.Net.Security 4.0.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Text.Encodings.Web 4.0.0 — System.Text.Encodings.Web 4.0.0 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Text.Encodings.Web 4.0.0 — System.Text.Encodings.Web 4.0.0 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Data.SqlClient 4.3.0 — System.Data.SqlClient 4.3.0 (direct) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Net.Security 4.3.0 — System.Net.Security 4.3.0 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Net.Security 4.3.0 — System.Net.Security 4.3.0 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Net.Http.WinHttpHandler 4.0.0 — System.Net.Http.WinHttpHandler 4.0.0 (transitive) has a Medium advisory; affects 6 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Net.Http.WinHttpHandler 4.0.0 — System.Net.Http.WinHttpHandler 4.0.0 (transitive) has a Medium advisory; affects 6 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]

D12 · Dependency Hygiene · Deprecated · ×14

Deprecated: Microsoft.NETCore.App — Microsoft.NETCore.App [2.2.0, — ) — the publisher's replacement is `2.2.0` Other,Legacy; migrate the reference to it.
Deprecated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 1.0.2 — Other,Legacy
Deprecated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Logging — Microsoft.Extensions.Logging 1.0.2 — Other,Legacy
Deprecated: Microsoft.AspNetCore.Hosting — Microsoft.AspNetCore.Hosting 1.0.2 — Other,Legacy
Deprecated: OpenTracing — OpenTracing 0.12.1 — Legacy — the publisher's replacement is `OpenTelemetry`; migrate the reference to it.
Deprecated: xunit — xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; migrate the reference to it.
Deprecated: App.Metrics.AspNetCore — App.Metrics.AspNetCore 4.1.0 — Legacy
Deprecated: App.Metrics.AspNetCore.Endpoints — App.Metrics.AspNetCore.Endpoints 4.1.0 — Legacy
Deprecated: App.Metrics.AspNetCore.Mvc — App.Metrics.AspNetCore.Mvc 4.1.0 — Legacy
Deprecated: App.Metrics.Formatters.Prometheus — App.Metrics.Formatters.Prometheus 4.1.0 — Legacy
Deprecated: OpenTracing.Contrib.NetCore — OpenTracing.Contrib.NetCore 0.5.0 — Legacy — the publisher's replacement is `OpenTelemetry`; migrate the reference to it.
Deprecated: Microsoft.AspNetCore.StaticFiles — Microsoft.AspNetCore.StaticFiles 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.FileProviders.Physical — Microsoft.Extensions.FileProviders.Physical 2.2.0 — Other,Legacy

D10 · Test Quality · No assertions · ×4

No assertions: Test1 test/Hummingbird.Extensions.Cacheing.UnitTest/CacheManagerUnitTest.cs:10 — Test method exercises code but verifies nothing — add an assertion.
No assertions: StringSet test/Hummingbird.Extensions.Cacheing.UnitTest/CacheManagerUnitTest.cs:46 — Test method exercises code but verifies nothing — add an assertion.
No assertions: Test1 test/Hummingbird.Extensions.DistributedLock.Consul.UnitTest/ConsulDistributedLockUnitTest.cs:13 — Test method exercises code but verifies nothing — add an assertion.
No assertions: Test1 test/Hummingbird.Extensions.DistributedLock.Redis.UnitTest/RedisDistributedLockUnitTest.cs:12 — Test method exercises code but verifies nothing — add an assertion.

D29 · Static Analysis (SAST) · Medium · ×3

Medium: missing-or-broken-authorization example/Hummingbird.Example/Controllers/BaseController.cs:11 — Anonymous access shouldn't be allowed unless explicit by design. Access control checks are missing and potentially can be bypassed. This finding violates the principle of least privilege or deny by default, where access should only be permitted for a specific set of roles or conforms to a custom policy or users. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: missing-or-broken-authorization example/Hummingbird.Example/Controllers/DistribuctedLockController.cs:10 — Anonymous access shouldn't be allowed unless explicit by design. Access control checks are missing and potentially can be bypassed. This finding violates the principle of least privilege or deny by default, where access should only be permitted for a specific set of roles or conforms to a custom policy or users. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: missing-or-broken-authorization example/Hummingbird.Example/Controllers/HttpController.cs:8 — Anonymous access shouldn't be allowed unless explicit by design. Access control checks are missing and potentially can be bypassed. This finding violates the principle of least privilege or deny by default, where access should only be permitted for a specific set of roles or conforms to a custom policy or users. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.

D3 · God Classes · TooManyMethods · ×2

TooManyMethods: RedisClientHelper src/Hummingbird.Extensions.Cacheing/StackExchange/RedisClientHelper.cs:0 — TooManyMethods — 376 significant lines (blank, comment-only and punctuation-only lines excluded), 103 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RedisCacheManage src/Hummingbird.Extensions.Cacheing/StackExchange/RedisCacheManage.cs:0 — TooManyMethods — 294 significant lines (blank, comment-only and punctuation-only lines excluded), 72 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D35 · Change Coupling · Change coupling · ×2

Change coupling: ResilientHttpClient.cs ↔ StandardHttpClient.cs src/Hummingbird.Extensions.Resilience.Http/Implements/ResilientHttpClient.cs — `src/Hummingbird.Extensions.Resilience.Http/Implements/ResilientHttpClient.cs` and `src/Hummingbird.Extensions.Resilience.Http/Implements/StandardHttpClient.cs` change together 73% of the time (11 of the 15 commits that touched the less-changed of the two, renames followed). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
Change coupling: KafkaBatchingExtensions.cs ↔ EventBusKafka.cs src/Hummingbird.Extensions.EventBus.Kafka/Extersions/KafkaBatchingExtensions.cs — `src/Hummingbird.Extensions.EventBus.Kafka/Extersions/KafkaBatchingExtensions.cs` and `src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs` change together 61% of the time (11 of the 18 commits that touched the less-changed of the two, renames followed). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2

Duplicated block (6 lines × 2) src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:315 — src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:315-320 | src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:264-269 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:315` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:585 — src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:585-591 | src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:552-557 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:585` 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.

D6 · Cohesion (LCOM4) · Low cohesion · ×2

Low cohesion: RabbitMqOption (LCOM4 5) src/Hummingbird.Extensions.EventBus.RabbitMQ/Extersions/DependencyInjectionExtersion.cs:16 — RabbitMqOption'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: KafkaOption (LCOM4 4) src/Hummingbird.Extensions.EventBus.Kafka/Extersions/DependencyInjectionExtersion.cs:14 — KafkaOption'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.

D1 · Cyclomatic Complexity · EventBusKafka.RegisterBatch (cyclomatic 38) · ×1

EventBusKafka.RegisterBatch (cyclomatic 38) src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:546 — EventBusKafka.RegisterBatch has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 5 of the 38 points are its own statements and the rest belongs to one function literal inside it that branches (line 562). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · EventBusRabbitMQ.RegisterBatch (cyclomatic 35) · ×1

EventBusRabbitMQ.RegisterBatch (cyclomatic 35) src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:581 — EventBusRabbitMQ.RegisterBatch has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 8 of the 35 points are its own statements and the rest belongs to one function literal inside it that branches (line 626). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · EventBusKafka.Register (cyclomatic 28) · ×1

EventBusKafka.Register (cyclomatic 28) src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:258 — EventBusKafka.Register has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 274). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · EventBusRabbitMQ.Register (cyclomatic 27) · ×1

EventBusRabbitMQ.Register (cyclomatic 27) src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:311 — EventBusRabbitMQ.Register has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 6 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 362, 331). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · RedisCacheManage.Create (cyclomatic 16) · ×1

RedisCacheManage.Create (cyclomatic 16) src/Hummingbird.Extensions.Cacheing/StackExchange/RedisCacheManage.cs:55 — RedisCacheManage.Create has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ConsulServiceDiscoveryProvider.Init (cyclomatic 16) · ×1

ConsulServiceDiscoveryProvider.Init (cyclomatic 16) src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs:89 — ConsulServiceDiscoveryProvider.Init has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D17 · Explicit Debt · TodoComment · ×1

TodoComment src/Hummingbird.Extensions.HealthChecks.SqlServer/HealthCheckBuilderSqlServerExtensions.cs:27 — //TODO: There is probably a much better way to do this. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

D18 · Solution Shape · Build failed · ×1

Build failed — The target solution did not build cleanly (errors: 3), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0234: The type or namespace name 'Configurations' does not exist in the namespace 'Microsoft.Extensions' (are you missing an assembly reference?).

D2 · Cognitive Complexity · EventBusRabbitMQ.RegisterBatch (cognitive 131) · ×1

EventBusRabbitMQ.RegisterBatch (cognitive 131) src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:581 — EventBusRabbitMQ.RegisterBatch has cognitive complexity 131 (threshold 15). Most of this is not in the body itself: 9 of the 131 points are its own statements and the rest belongs to one function literal inside it that branches (line 626). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · EventBusKafka.RegisterBatch (cognitive 120) · ×1

EventBusKafka.RegisterBatch (cognitive 120) src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:546 — EventBusKafka.RegisterBatch has cognitive complexity 120 (threshold 15). Most of this is not in the body itself: 4 of the 120 points are its own statements and the rest belongs to one function literal inside it that branches (line 562). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · EventBusKafka.Register (cognitive 78) · ×1

EventBusKafka.Register (cognitive 78) src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs:258 — EventBusKafka.Register has cognitive complexity 78 (threshold 15). Most of this is not in the body itself: 4 of the 78 points are its own statements and the rest belongs to one function literal inside it that branches (line 274). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · RedisCacheManage.Create (cognitive 70) · ×1

RedisCacheManage.Create (cognitive 70) src/Hummingbird.Extensions.Cacheing/StackExchange/RedisCacheManage.cs:55 — RedisCacheManage.Create has cognitive complexity 70 (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.

D2 · Cognitive Complexity · EventBusRabbitMQ.Register (cognitive 53) · ×1

EventBusRabbitMQ.Register (cognitive 53) src/Hummingbird.Extensions.EventBus.RabbitMQ/Implements/EventBusRabbitMQ.cs:311 — EventBusRabbitMQ.Register has cognitive complexity 53 (threshold 15). Most of this is not in the body itself: 5 of the 53 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 362, 331). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · ConsulServiceDiscoveryProvider.Heartbeat (cognitive 48) · ×1

ConsulServiceDiscoveryProvider.Heartbeat (cognitive 48) src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs:235 — ConsulServiceDiscoveryProvider.Heartbeat has cognitive complexity 48 (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.

D2 · Cognitive Complexity · ConsulWorkIdCreateStrategy.CreateWorkId (cognitive 39) · ×1

ConsulWorkIdCreateStrategy.CreateWorkId (cognitive 39) src/Hummingbird.Extensions.UidGenerator.ConsulWorkIdStrategy/ConsulWorkIdCreateStrategy.cs:106 — ConsulWorkIdCreateStrategy.CreateWorkId has cognitive complexity 39 (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.

D2 · Cognitive Complexity · ConsulServiceDiscoveryProvider.Init (cognitive 37) · ×1

ConsulServiceDiscoveryProvider.Init (cognitive 37) src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs:89 — ConsulServiceDiscoveryProvider.Init has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D2 · Cognitive Complexity · Formatter.Format (cognitive 24) · ×1

Formatter.Format (cognitive 24) src/Hummingbird.Extensions.Canal/Formatters/MaxwellJson/MaxwellJsonFormatter.cs:11 — Formatter.Format has cognitive complexity 24 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · HttpUrlResolver.Resolve (cognitive 21) · ×1

HttpUrlResolver.Resolve (cognitive 21) src/Hummingbird.Extensions.Resilience.Http/Implements/UrlResolver.cs:25 — HttpUrlResolver.Resolve has cognitive complexity 21 (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.

D2 · Cognitive Complexity · CornJobSchedulerHostedService.StartAsync (cognitive 20) · ×1

CornJobSchedulerHostedService.StartAsync (cognitive 20) src/Hummingbird.Extensions.Quartz/CornJobSchedulerHostedService.cs:34 — CornJobSchedulerHostedService.StartAsync 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.

D2 · Cognitive Complexity · CanalClientHostedService.StartAsync (cognitive 17) · ×1

CanalClientHostedService.StartAsync (cognitive 17) src/Hummingbird.Extensions.Canal/Internal/CanalClientHostedService.cs:31 — CanalClientHostedService.StartAsync 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.

D2 · Cognitive Complexity · OssStaticFileMiddleware.Invoke (cognitive 17) · ×1

OssStaticFileMiddleware.Invoke (cognitive 17) src/Hummingbird.Extensions.FileSystem.Oss/StaticFiles/OssStaticFileMiddleware.cs:62 — OssStaticFileMiddleware.Invoke has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ConsulServiceLocator.GetAsync (cognitive 16) · ×1

ConsulServiceLocator.GetAsync (cognitive 16) src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceLocator.cs:83 — ConsulServiceLocator.GetAsync has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D24 · Comment Value · LLM evaluation failed · ×1

LLM evaluation failed — JSON parse error: Expected start of a property name or value, but instead reached end of data. Path: $.notable[4] | LineNumber: 0 | BytePositionInLine: 954.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1

Duplicated block (11 lines × 2) src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceLocator.cs:129 — src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceLocator.cs:129-139 | src/Hummingbird.Extensions.DynamicRoute.Nacos/NacosServiceLocator.cs:76-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceLocator.cs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1

Duplicated block (9 lines × 2) src/Hummingbird.Extensions.HealthChecks/Checks/NumericChecks.cs:22 — src/Hummingbird.Extensions.HealthChecks/Checks/NumericChecks.cs:22-30 | src/Hummingbird.Extensions.HealthChecks/Checks/NumericChecks.cs:50-58 — 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/Hummingbird.Extensions.HealthChecks/Checks/NumericChecks.cs:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1

Duplicated block (8 lines × 2) src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs:340 — src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs:340-347 | src/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs:367-374 — 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/Hummingbird.Extensions.DynamicRoute.Consul/ConsulServiceDiscoveryProvider.cs:340` 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.

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: Hummingbird.Extensions.HealthChecks(netstandard2.0) — Hummingbird.Extensions.HealthChecks(netstandard2.0): abstractness 0.21, instability 0.00, distance 0.79 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.

Recommendation — 10 finding(s)

D11 · Test Reliability · Test runner surfaced no tests · ×1

Test runner surfaced no tests — Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 7 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: src/Hummingbird.Extensions.EventBus.Kafka/Implements/EventBusKafka.cs, src/Hummingbird.AspNetCore.Metrics/DependencyInjectionExtersion.cs. Pair on, review, or document these before any departure.

D21 · Naming Consistency · Inconsistent namespace/implementation naming for Redis cache components. One class is named 'RedisCacheManage' (implying a manager/handler) while the other is 'RedisClientHelper' (implying a utility/helper). They appear to be related components within the same 'Cacheing' feature area but use different suffixes ('Manage' vs 'Helper') and are split across different namespaces ('StackExchangeImplement' vs 'StackExchangeImplement' - wait, they are in the same namespace but different classes). More critically, there is a third class 'RedisConnectionHelp' (typo · ×1

Inconsistent namespace/implementation naming for Redis cache components. One class is named 'RedisCacheManage' (implying a manager/handler) while the other is 'RedisClientHelper' (implying a utility/helper). They appear to be related components within the same 'Cacheing' feature area but use different suffixes ('Manage' vs 'Helper') and are split across different namespaces ('StackExchangeImplement' vs 'StackExchangeImplement' - wait, they are in the same namespace but different classes). More critically, there is a third class 'RedisConnectionHelp' (typo: Help vs Helper) and 'RedisCacheManage' vs 'RedisClientHelper'. The inconsistency is between 'Manage' and 'Helper' suffixes for similar Redis interaction classes. — Standardize on either 'RedisCacheManager' and 'RedisClientHelper' or 'RedisCacheHandler' and 'RedisClientHelper'. Ensure consistent suffixes for related classes. (symbols: Hummingbird.Extensions.Cacheing.StackExchangeImplement.RedisCacheManage, Hummingbird.Extensions.Cacheing.StackExchangeImplement.RedisClientHelper)

D21 · Naming Consistency · Typo in the word 'Extensions' in the namespace or class name. The namespace is 'Hummingbird.Extensions.EventBus.Kafka' but the class is 'EventLogEntryExtersions' (missing 'n' in Extensions). This typo is repeated across multiple classes in different namespaces (Kafka, RabbitMQ). · ×1

Typo in the word 'Extensions' in the namespace or class name. The namespace is 'Hummingbird.Extensions.EventBus.Kafka' but the class is 'EventLogEntryExtersions' (missing 'n' in Extensions). This typo is repeated across multiple classes in different namespaces (Kafka, RabbitMQ). — Rename 'EventLogEntryExtersions' to 'EventLogEntryExtensions' and 'DateTimeExtersions' to 'DateTimeExtensions' to fix the typo. (symbols: Hummingbird.Extensions.EventBus.Kafka.EventLogEntryExtersions.WithNoRetry, Hummingbird.Extensions.EventBus.Kafka.EventLogEntryExtersions.WaitAndRetry, Hummingbird.Extensions.EventBus.RabbitMQ.EventLogEntryExtersions.WaitAndRetryForever, Hummingbird.Extensions.EventBus.Kafka.DateTimeExtersions.ToTimestamp)

D21 · Naming Consistency · Typo in the word 'Extension' in the class name. The class is named 'DependencyInjectionExtersion' (missing 'n' in Extension). This typo is present in all extension classes in this codebase. · ×1

Typo in the word 'Extension' in the class name. The class is named 'DependencyInjectionExtersion' (missing 'n' in Extension). This typo is present in all extension classes in this codebase. — Rename 'DependencyInjectionExtersion' to 'DependencyInjectionExtension'. (symbols: Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddResilientHttpClient, Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddNacosDynamicRoute, Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddSqlServerEventLogging, Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddRabbitmq, Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddConsulWorkIdCreateStrategy, Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddRateLimit, Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddRequestLimit, Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddPhysicalFileSystem, Microsoft.Extensions.DependencyInjection.DependencyInjectionExtersion.AddCacheing)

D21 · Naming Consistency · Inconsistent naming for Redis-related classes. 'RedisCacheManage' uses 'Manage' (likely meant Manager), 'RedisClientHelper' uses 'Helper', and 'RedisConnectionHelp' has a typo ('Help' instead of 'Helper' or 'Manager'). The suffixes 'Manage', 'Helper', and 'Help' are used inconsistently for similar Redis interaction classes. · ×1

Inconsistent naming for Redis-related classes. 'RedisCacheManage' uses 'Manage' (likely meant Manager), 'RedisClientHelper' uses 'Helper', and 'RedisConnectionHelp' has a typo ('Help' instead of 'Helper' or 'Manager'). The suffixes 'Manage', 'Helper', and 'Help' are used inconsistently for similar Redis interaction classes. — Standardize on 'RedisCacheManager', 'RedisClientHelper', and 'RedisConnectionHelper'. (symbols: Hummingbird.Extensions.Cacheing.StackExchangeImplement.RedisCacheManage, Hummingbird.Extensions.Cacheing.StackExchangeImplement.RedisClientHelper, Hummingbird.Extensions.Cacheing.StackExchangeImplement.RedisConnectionHelp)

D21 · Naming Consistency · Typo in the namespace 'Abastracts' (missing 'c' in Abstracts). · ×1

Typo in the namespace 'Abastracts' (missing 'c' in Abstracts). — Rename namespace 'Hummingbird.Extensions.UidGenerator.Abastracts' to 'Hummingbird.Extensions.UidGenerator.Abstracts'. (symbols: Hummingbird.Extensions.UidGenerator.Abastracts.IWorkIdCreateStrategyBuilder, Hummingbird.Extensions.UidGenerator.Implements.IdWorker.NextId, Hummingbird.Extensions.UidGenerator.Implements.WorkIdCreateStrategy.ConsulWorkIdCreateStrategy, Hummingbird.Extensions.UidGenerator.Implements.DisposableAction)

D23 · Boundary Type-Coupling · Bounded contexts not declared · ×1

Bounded contexts not declared — At 14486 LoC spread over 67 projects the codebase is both large and multi-module, so explicit bounded contexts are warranted. 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"]`.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

Rotate the exposed credentials — git history can't be un-committed — Some of these secrets are in git HISTORY: deleting the file does not remove them (the commit persists on every clone, fork and backup). The remediation is to ROTATE each historically-exposed credential and treat it as compromised — not to delete the file. Rewriting history is disruptive and unreliable across existing forks. (Working-tree-only secrets — no commit — can instead be removed from the file and moved to a secret store.) Every location above sits inside a test/fixture/sample tree, so there may be no live credential to revoke — in that case the performable actions are different ones: confirm each value was never reused outside the tests (a fixture key shared with a staging or demo environment IS a live credential and must be rotated), generate this material at test time instead of committing it so the next one cannot be mistaken for a real leak, and record the deliberate exposure where a reader of the file will see it. Rotate anything that fails the first check.

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 26 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than listed individually (27 orphaned of 66 analysed files in total, counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first).

Info — 70 finding(s)

D12 · Dependency Hygiene · Outdated · ×68

Outdated: Microsoft.AspNetCore.Http.Abstractions — Microsoft.AspNetCore.Http.Abstractions 2.1.0 → 2.3.11 available (referenced by Hummingbird.Core).
Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 2.1.0 → 10.0.10 available (referenced by Hummingbird.Core).
Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 2.1.0 → 10.0.10 available (referenced by Hummingbird.Extensions.UidGenerator).
Outdated: Microsoft.AspNetCore.Http.Features — Microsoft.AspNetCore.Http.Features 2.1.1 → 5.0.17 available (referenced by Hummingbird.Extensions.Idempotency).
Outdated: Newtonsoft.Json — Newtonsoft.Json 12.0.1 → 13.0.4 available (referenced by Hummingbird.Extensions.Idempotency).
Outdated: Microsoft.AspNetCore.Http — Microsoft.AspNetCore.Http 2.1.1 → 2.3.11 available (referenced by Hummingbird.Extensions.Resilience.Http).
Outdated: Microsoft.Extensions.Caching.Memory — Microsoft.Extensions.Caching.Memory 2.1.1 → 10.0.10 available (referenced by Hummingbird.Extensions.Resilience.Http).
Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 2.1.1 → 10.0.10 available (referenced by Hummingbird.Extensions.Resilience.Http).
Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 2.1.1 → 10.0.10 available (referenced by Hummingbird.Extensions.Resilience.Http).
Outdated: Polly — Polly 7.1.1 → 8.7.0 available (referenced by Hummingbird.Extensions.Resilience.Http).
Outdated: Microsoft.Extensions.Logging — Microsoft.Extensions.Logging 2.1.1 → 10.0.10 available (referenced by Hummingbird.Extensions.EventBus).
Outdated: Autofac.Extensions.DependencyInjection — Autofac.Extensions.DependencyInjection 4.2.2 → 11.0.2 available (referenced by Hummingbird.Extensions.EventBus.RabbitMQ).
Outdated: Microsoft.CSharp — Microsoft.CSharp 4.6.0 → 4.7.0 available (referenced by Hummingbird.Extensions.EventBus.RabbitMQ).
Outdated: RabbitMQ.Client — RabbitMQ.Client 5.1.2 → 7.2.1 available (referenced by Hummingbird.Extensions.EventBus.RabbitMQ).
Outdated: CacheManager.Core — CacheManager.Core 1.2.0 → 3.0.0 available (referenced by Hummingbird.Extensions.Cache).
Outdated: CacheManager.Microsoft.Extensions.Caching.Memory — CacheManager.Microsoft.Extensions.Caching.Memory 1.2.0 → 3.0.0 available (referenced by Hummingbird.Extensions.Cache).
Outdated: CacheManager.Microsoft.Extensions.Configuration — CacheManager.Microsoft.Extensions.Configuration 1.2.0 → 3.0.0 available (referenced by Hummingbird.Extensions.Cache).
Outdated: CacheManager.Serialization.Json — CacheManager.Serialization.Json 1.2.0 → 3.0.0 available (referenced by Hummingbird.Extensions.Cache).
Outdated: CacheManager.StackExchange.Redis — CacheManager.StackExchange.Redis 1.2.0 → 3.0.0 available (referenced by Hummingbird.Extensions.Cache).
Outdated: Microsoft.Extensions.Configuration.Abstractions — Microsoft.Extensions.Configuration.Abstractions 2.1.1 → 10.0.10 available (referenced by Hummingbird.Extensions.Cache).
Outdated: Microsoft.Extensions.Configuration.Binder — Microsoft.Extensions.Configuration.Binder 2.1.1 → 10.0.10 available (referenced by Hummingbird.Extensions.Cache).
Outdated: CacheManager.SystemRuntimeCaching — CacheManager.SystemRuntimeCaching 1.2.0 → 3.0.0 available (referenced by Hummingbird.Extensions.Cache).
Outdated: Dapper — Dapper 1.50.5 → 2.1.79 available (referenced by Hummingbird.Extensions.EventBus.SqlServerLogging).
Outdated: StackExchange.Redis — StackExchange.Redis 2.0.601 → 3.1.3 available (referenced by Hummingbird.Extensions.HealthChecks.Redis).
Outdated: MongoDB.Driver — MongoDB.Driver 2.4.4 → 3.10.0 available (referenced by Hummingbird.Extensions.HealthChecks.MongoDb).
+ 43 more in this group — see findings.md.

D19 · Documentation Quality · XML-doc coverage · ×1

XML-doc coverage: Hummingbird.Extensions.Cacheing(net4.6.1) src/Hummingbird.Extensions.Cacheing/Hummingbird.Extensions.Cacheing.csproj — Hummingbird.Extensions.Cacheing(net4.6.1): 63 % XML-doc coverage (125/198).

D22 · Internal API Consistency · No exposed public API · ×1

No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .	3	artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off .	3	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list Hummingbird.sln package --vulnerable --include-transitive --format json	51	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	0	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — Data compliance (PII/GDPR) was not assessed in this scan — no ruleset is currently available for it. This says nothing about how this repository handles personal data, in either direction.	0	—
D33 · JS/npm Dependency Vulnerabilities	trivy	—	trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D38 · OSV Dependency Vulnerabilities	osv-scanner	—	osv-scanner: not applicable — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—

Run 019fc7fe-0177-7319-987b-543e27fbd0ba · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Guoming/Hummingbird

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency graph

Architecture — module dependency matrix

At a glance — Code Health · 50% · Weak · gated by D18, X5

At a glance — Architecture · 85% · Strong

At a glance — Maturity · 55% · Adequate · gated by M2

At a glance — Readiness · 23% · Critical · gated by D8, D12, P1, P3

At a glance — Security · 71% · Adequate · gated by D30

At a glance — Performance · 63% · Adequate

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts