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.
crane-soft/csModbus carries serious gaps (47%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Security (100%) — its security and compliance posture is in good shape. Code Health (98%) is solid too.
The area that most needs attention is Readiness (23%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Maturity (39%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); 1 No automated tests finding(s) in Code Coverage (Code Coverage); 1 No tests found finding(s) in Test Distribution (Test Distribution).
For scale: Small (~3,854 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
Encouragingly, the gaps are in documentation and release process — not in the code's correctness, structure or security, which are strong. They're low-risk to close, and doing so would lift the grade without re-engineering anything that already works.
Code Health
98% ★
Exemplary
Architecture
98% ★
Exemplary
Maturity
39%
Weak · gated by D34, M2
Readiness
23% ⚠
Critical · gated by D8, D9, P1, P3
Security
100% ★
Exemplary
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% · 47% weightMaturity 39% · 26% weightArchitecture 98% · 14% weightCode Health 98% · 8% weightSecurity 100% · 4% weight
Raise Readiness 23 → 70 (the Healthy floor) ⇒ headline 47 → ~63.
Code composition — where the lines go
Business logic 19%Plumbing 56%Generated 25%
New since the last scan (1+)
- D24 · LLM evaluation failed
Rebuild cost & value ~ Modeled — €1,500–€7,600
| Cost to rebuild | €1,500–€7,600 |
| Domain complexity | Standard |
| Quality factor | 0.7× (at 47% quality) |
| Size & shape | Small · 32% boilerplate · 42% straight-line · 26% branching logic |
This codebase represents roughly ~0.1 person-years of build effort (about ~€4,600 to rebuild). Its weakest lens is Readiness at 23% — the part of that asset most exposed by the findings below.
Top priorities
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
2
Resolve the 1 No tests found finding(s) in Test Distribution.
3
Add a CI workflow that builds and runs the test suite on every push/PR.
Diagnosis — what's actually going on
Value concentrated against a weak lens
This is a Small asset (~0.1 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.
Highest-leverage move
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Architecture — bounded-context dependency graph
Architecture — module dependency matrix
At a glance — Code Health
The Good
D1 · .NET / C#
Cyclomatic Complexity
9.6
D2 · .NET / C#
Cognitive Complexity
9.3
D3 · .NET / C#
God Classes
10.0
D4 · .NET / C#
Code Duplication
10.0
D17 · .NET / C#
Explicit Debt
9.5
D18 · .NET / C#
Solution Shape
10.0
GD1 · Repo
Unfinished & placeholder code
10.0
IC1 · Repo
Incompleteness & stubs
10.0
X1 · Repo
Async correctness
10.0
X3 · Repo
Exception handling
10.0
X4 · Repo
Structured logging
10.0
At a glance — Architecture
The Good
At a glance — Maturity
The Good
The Ugly
At a glance — Readiness
The Ugly
At a glance — Security
Roadmap
First, establish a continuous integration workflow to build and run tests on every push or pull request. Next, address the lack of automated tests by resolving the single code coverage gap and ensuring all identified test distribution issues are fixed. Then, implement a changelog to track each release's changes. Finally, create architecture decision records to document significant design choices and their consequences in a central location.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +16.4 pts | Low | Code Coverage |
| Resolve the 1 No tests found finding(s) in Test Distribution. | +16.4 pts | Low | Test Distribution |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +23.0 pts | Medium | CI/CD gates |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +16.4 pts | Medium | Release Hygiene |
| 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). | +15.6 pts | Medium | Architecture documentation |
| Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root. | +15.5 pts | Medium | Folder & project structure |
| 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. | +15.1 pts | Medium | Observability |
| Resolve the 2 Low XML-doc coverage finding(s) in Documentation Quality — start with csModbus.csproj, csModbusView.csproj. | +6.5 pts | Low | Documentation Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| ClassLib/csModbusLib/lib/Modbus/MbFrame.cs | 6.0 | Mixed | Explicit Debt: TodoComment |
| ClassLib/csModbusLib/lib/Modbus/MbMaster.cs | 7.3 | Mixed | Explicit Debt: TodoComment |
| ClassLib/csModbusView/lib/MasterGridView.cs | 7.3 | Mixed | Explicit Debt: TodoComment |
| DemoApps/VB.NET/csModMaster/frmModsMaster.vb | 7.3 | Mixed | Explicit Debt: TodoComment |
| ClassLib/csModbusLib/lib/SlaveDataServer/MbSlaveDataServer.cs | 7.8 | Mixed | Cyclomatic Complexity: MbSlaveDataServer.DataServices (cyclomatic 21) |
| ClassLib/csModbusLib/lib/Interface/MbRTU.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| ClassLib/csModbusLib/lib/Interface/MbSerial.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| ClassLib/csModbusLib/lib/Modbus/MbBase.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| ClassLib/csModbusLib/lib/Modbus/MbMasterEx.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| ClassLib/csModbusLib/lib/Modbus/MbSlave.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| ClassLib/csModbusView/lib/SlaveGridView.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| ClassLib/csModbusLib/lib/Modbus/MbSlaveStateMachine.cs | 8.5 | Near-clean | Cognitive Complexity: MbSlaveStateMachine.SerialInterface_DataReceivedEvent (cognitive 22) |
| ClassLib/csModbusView/lib/MbGridView.cs | 8.5 | Near-clean | Cognitive Complexity: MbGridView.InitGridView (cognitive 18) |
| DemoApps/VB.NET/csModBus.sln | 8.5 | Near-clean | Solution Shape: Solution references a project that does not exist |
| ClassLib/csModbusLib/csModbus.csproj | 8.5 | Near-clean | Documentation Quality: Low XML-doc coverage: csModbus |
| ClassLib/csModbusView/csModbusView.csproj | 8.5 | Near-clean | Documentation Quality: Low XML-doc coverage: csModbusView |
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. 35 of 37 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.5 — 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.
What we checked — 37 dimensions across the health lenses
D1D2D3D4D5D6D8D9D12D13D15D17D18D19D21D26D28D29D34D35AX10AX3AX4AX5GD1IC1M1M2M3M4P1P2P3P6X1X3X4
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, 26 of 39 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- 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.
Tools & methods
| 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 | 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 |
Run transparency — what happened this run
- 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.
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
- 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.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
- D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MbSlaveDataServer.DataServices at 21.
MbSlaveDataServer.DataServices (cyclomatic 21)ClassLib/csModbusLib/lib/SlaveDataServer/MbSlaveDataServer.cs:29
Do you agree with this assessment?
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was MbSlaveDataServer.DataServices at 23.
MbSlaveDataServer.DataServices (cognitive 23)ClassLib/csModbusLib/lib/SlaveDataServer/MbSlaveDataServer.cs:29
MbSlaveStateMachine.SerialInterface_DataReceivedEvent (cognitive 22)ClassLib/csModbusLib/lib/Modbus/MbSlaveStateMachine.cs:110
MbGridView.InitGridView (cognitive 18)ClassLib/csModbusView/lib/MbGridView.cs:105
Do you agree with this assessment?
D3 · God Classes
0 god class(es) detected.
Do you agree with this assessment?
D4 · Code Duplication
0 duplicated block group(s) detected.
Do you agree with this assessment?
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
Off the main sequence: csModbus
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Coupling 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.
Do you agree with this assessment?
D6 · Cohesion (LCOM4)
1 of 20 classes have LCOM4 above 3.
Low cohesion: MBSFrame (LCOM4 4)ClassLib/csModbusLib/lib/Modbus/MbFrame.cs:219
Do you agree with this assessment?
D8 · Code Coverage
No automated tests — no test code was found in this repository.
No automated tests
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- 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.
Do you agree with this assessment?
D9 · Test Distribution
No test suite found.
No tests found
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D12 · Dependency Hygiene
0 outdated, 0 vulnerable, 0 deprecated packages.
Do you agree with this assessment?
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
Do you agree with this assessment?
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
Do you agree with this assessment?
D17 · Explicit Debt
15 deducted debt markers + 0 dead symbols across 4311 LoC (0.3/KLoC) → score 9.5.
TodoComment ClassLib/csModbusLib/lib/Interface/MbRTU.cs:9
CommentedOutCodeClassLib/csModbusLib/lib/Modbus/MbMaster.cs:178
Do you agree with this assessment?
D18 · Solution Shape
4 projects, 31 source files, 4311 hand-written lines of code (4311 production / 0 test), plus 1284 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 5 inter-project edges (build status unknown — did not finish).
Monorepo: only 1 of 2 solutions was scored
Solution references a project that does not existDemoApps/VB.NET/csModBus.sln
Build status unknown
Do you agree with this assessment?
D19 · Documentation Quality
The single README is a decent feature/usage description of the library but lacks architecture and design documentation. It lists features (Master/Slave, TCP/UDP/RTU/ASCII, multimaster, easy data server in slave mode, multiple-node-id management, gridview user control), supported Modbus functions, and a usage example for a 'SlaveSimple' application that starts a listening MbSlaveServer on TCP port 502. It also mentions an additional master/user-control library but does not explain the master side or the master/user-control interface in detail. The document is clipped mid-usage code before covering architecture/design, so any outline sections present are assumed present and not flagged as missing.
Low XML-doc coverage: csModbus ClassLib/csModbusLib/csModbus.csproj
XML-doc coverage: csModMaster DemoApps/VB.NET/csModMaster/csModMaster.vbproj
What to do
- Resolve the 2 Low XML-doc coverage finding(s) in Documentation Quality — start with csModbus.csproj, csModbusView.csproj. — One of this dimension's main actionable groups (2 warning-level).
Do you agree with this assessment?
D21 · Naming Consistency
3 naming inconsistencies across 200 sampled symbols.
Inconsistent naming for the same logical concept: checking or processing the end of a frame. One method is named 'Check_EndOfFrame' while the other is 'EndOffFrameLenthth' (which also contains a typo 'Lenthth' and likely 'Off' instead of 'Of').
Different interfaces/classes use different names for the same or similar functionality regarding the end of a frame. 'EndOfFrame' vs 'EndOffFrameLenthth'.
Inconsistent naming for setting endianness. One uses 'setLongEndianess' (specific to 32-bit/long) while the other uses the more generic 'setEndianess'.
What to do
- Resolve the 1 Inconsistent naming for the same logical concept finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Different interfaces/classes use different names for the same or similar… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Inconsistent naming for setting endianness. One uses 'setLongEndianess'… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D26 · Project Cohesion
0 of 4 projects flagged as possibly oversized/incoherent.
Do you agree with this assessment?
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
Do you agree with this assessment?
D29 · Static Analysis (SAST)
semgrep found no security issues.
Do you agree with this assessment?
D34 · Knowledge Freshness
20 of 20 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is ClassLib/csModbusLib/lib/Modbus/MbFrame.cs.
Dormant codebase
Largest orphaned fileClassLib/csModbusLib/lib/Modbus/MbFrame.cs
What to do
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Largest orphaned file finding(s) in Knowledge Freshness — start with MbFrame.cs. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D35 · Change Coupling
No strong hidden change-coupling between production files.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
AX10 · Code composition
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?
AX3 · Project dependency cycles
Do you agree with this assessment?
AX4 · Dependency direction
Do you agree with this assessment?
AX5 · Architecture & structure
Do you agree with this assessment?
GD1 · Unfinished & placeholder code
Do you agree with this assessment?
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — MbSerial.cs:167, MbFrame.cs:271, MbFrame.cs:344, …
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Do you agree with this assessment?
M1 · Documentation (README)
What to do
- Add a 'Testing' section to the root README — how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 4 of 4 project(s) that lack one — worth up to 2 pts.
Do you agree with this assessment?
M2 · Architecture documentation
- 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 structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
- No test surface was found — there are no tests here to separate from production code, so the folder question hasn't been reached yet.
- Only 1/4 projects share a common root namespace — the code's module identity is inconsistent.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Do you agree with this assessment?
M4 · Documentation accuracy
Do you agree with this assessment?
P1 · CI/CD gates
- 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?
P2 · Observability
- Only 1/2 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 2, 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.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
Do you agree with this assessment?
P3 · Security & performance tooling
- 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?
P6 · Release Hygiene
- 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?
X1 · Async correctness
Do you agree with this assessment?
X3 · Exception handling
Do you agree with this assessment?
X4 · Structured logging
Do you agree with this assessment?
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 98% | Exemplary | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 39% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 23% | Critical — gated by D8, D9, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Strongest area. |
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — Test reliability not included
- D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
- D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
- 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 — At only 4311 LoC the codebase is small despite four projects and no boundaries declared, so explicit bounded-context boundaries are not needed.
- D24 Comment Value — LLM evaluation failed
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
- D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
- 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 none of the 3 signals this check looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
- P12 CI test-gate honesty — no CI workflow found
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X2 Cancellation propagation — no async methods found
- X5 Nullable reference types — no NRT-eligible projects
- 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)
Issue — 1 finding(s)
D8 · Code Coverage
- No automated tests
Warning — 27 finding(s)
D17 · Explicit Debt
- TodoComment ClassLib/csModbusLib/lib/Interface/MbRTU.cs:9
- TodoComment ClassLib/csModbusLib/lib/Interface/MbSerial.cs:108
- TodoComment ClassLib/csModbusLib/lib/Modbus/MbBase.cs:69
- TodoComment ClassLib/csModbusLib/lib/Modbus/MbFrame.cs:358
- TodoComment ClassLib/csModbusLib/lib/Modbus/MbFrame.cs:521
- TodoComment ClassLib/csModbusLib/lib/Modbus/MbFrame.cs:538
- TodoComment ClassLib/csModbusLib/lib/Modbus/MbMaster.cs:166
- TodoComment ClassLib/csModbusLib/lib/Modbus/MbMasterEx.cs:8
- TodoComment ClassLib/csModbusLib/lib/Modbus/MbSlave.cs:94
- TodoComment ClassLib/csModbusView/lib/MasterGridView.cs:122
- TodoComment ClassLib/csModbusView/lib/MasterGridView.cs:177
- TodoComment ClassLib/csModbusView/lib/SlaveGridView.cs:166
- TodoComment DemoApps/VB.NET/csModMaster/frmModsMaster.vb:90
- TodoComment DemoApps/VB.NET/csModMaster/frmModsMaster.vb:148
D19 · Documentation Quality
- Low XML-doc coverage: csModbus ClassLib/csModbusLib/csModbus.csproj
- Low XML-doc coverage: csModbusView ClassLib/csModbusView/csModbusView.csproj
D1 · Cyclomatic Complexity
- MbSlaveDataServer.DataServices (cyclomatic 21) ClassLib/csModbusLib/lib/SlaveDataServer/MbSlaveDataServer.cs:29
D16 · Bus Factor
- single-maintainer — knowledge-concentration (bus factor) risk
D17 · Explicit Debt
- CommentedOutCode ClassLib/csModbusLib/lib/Modbus/MbMaster.cs:178
D18 · Solution Shape
- Monorepo: only 1 of 2 solutions was scored
D18 · Solution Shape
- Solution references a project that does not exist DemoApps/VB.NET/csModBus.sln
D2 · Cognitive Complexity
- MbSlaveDataServer.DataServices (cognitive 23) ClassLib/csModbusLib/lib/SlaveDataServer/MbSlaveDataServer.cs:29
D2 · Cognitive Complexity
- MbSlaveStateMachine.SerialInterface_DataReceivedEvent (cognitive 22) ClassLib/csModbusLib/lib/Modbus/MbSlaveStateMachine.cs:110
D2 · Cognitive Complexity
- MbGridView.InitGridView (cognitive 18) ClassLib/csModbusView/lib/MbGridView.cs:105
D24 · Comment Value
- LLM evaluation failed
D5 · Coupling
- Off the main sequence: csModbus
D6 · Cohesion (LCOM4)
- Low cohesion: MBSFrame (LCOM4 4) ClassLib/csModbusLib/lib/Modbus/MbFrame.cs:219
Recommendation — 7 finding(s)
D11 · Test Reliability
- Test reliability not included
D21 · Naming Consistency
- Inconsistent naming for the same logical concept: checking or processing the end of a frame. One method is named 'Check_EndOfFrame' while the other is 'EndOffFrameLenthth' (which also contains a typo 'Lenthth' and likely 'Off' instead of 'Of').
D21 · Naming Consistency
- Different interfaces/classes use different names for the same or similar functionality regarding the end of a frame. 'EndOfFrame' vs 'EndOffFrameLenthth'.
D21 · Naming Consistency
- Inconsistent naming for setting endianness. One uses 'setLongEndianess' (specific to 32-bit/long) while the other uses the more generic 'setEndianess'.
D34 · Knowledge Freshness
- Dormant codebase
D34 · Knowledge Freshness
- Largest orphaned file ClassLib/csModbusLib/lib/Modbus/MbFrame.cs
D9 · Test Distribution
- No tests found
Info — 4 finding(s)
D19 · Documentation Quality
- XML-doc coverage: csModMaster DemoApps/VB.NET/csModMaster/csModMaster.vbproj
- XML-doc coverage: csModSlave DemoApps/VB.NET/csModSlave/csModSlave.vbproj
D18 · Solution Shape
- Build status unknown
D22 · Internal API Consistency
- No exposed public API
Appendix B — Reproduction & audit trail
| 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 . | 0 | 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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet: not applicable — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess. | 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 | — |