Executive summary
xieguigang/console falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 51 out of 100 and is rated Adequate, and none of its 17 critical findings concern security.
Production Readiness, at 28, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 6 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 12 points. Raising Production Readiness to 70 would lift the score to about 69.
Seventeen errors are caught and ignored, so failures can go unnoticed. Handling or logging the ignored errors would close this risk.
The product code is 7,539 lines, about €7,600 to rebuild.
If Production Readiness rose from 28 to 70, the lowest score rated Strong, the score would rise from 51 to about 69.
New since the last survey: 6 findings
- Code Duplication · Edited copy of a member (39 corresponding lines) SShClient/LocalShellInterface.vb
- Code Duplication · Edited copy of a member (15 corresponding lines) SShClient/LocalShellInterface.vb
- Code Duplication · Edited copy of a member (13 corresponding lines) console/Win32/AbstractProcessInterface.vb
- Code Duplication · Edited copy of a member (11 corresponding lines) SShClient/SshProcessInterface.vb
- Code Duplication · Edited copy of a member (7 corresponding lines) console/WebView2/WebViewConsole.vb
- Code Duplication · Edited copy of a member (2 corresponding lines) console/WebView2/WebViewConsole.vb
Fixed since the last survey: 2 findings
- Churn × Complexity Hotspots · Hotspot: console/AnsiEscapeRenderer.vb console/AnsiEscapeRenderer.vb
- Documentation (README) · README may be stale
Rebuild cost: about €7,600 · Estimate
| Cost to rebuild | €2,500 to €13,000, for 42 to 133 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,539 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Microsoft.VisualBasic | 2 Microsoft.VisualBasic.Windows.Forms.My | 3 Microsoft.VisualBasic.Windows.Forms.SshClient.My | 4 Microsoft.VisualBasic.Windows.Forms.WebView2 | 5 Microsoft.VisualBasic.Windows.Forms.Win32 | 6 console.WebView2.wwwroot | 7 jq | 8 jq.My | 9 lsd.My | 10 lsd.lsd | 11 Microsoft.VisualBasic.Windows.Forms | 12 Microsoft.VisualBasic.Windows.Forms.Console | 13 Microsoft.VisualBasic.Windows.Forms.SshClient |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Microsoft.VisualBasic | |||||||||||||
| 2 Microsoft.VisualBasic.Windows.Forms.My | |||||||||||||
| 3 Microsoft.VisualBasic.Windows.Forms.SshClient.My | |||||||||||||
| 4 Microsoft.VisualBasic.Windows.Forms.WebView2 | |||||||||||||
| 5 Microsoft.VisualBasic.Windows.Forms.Win32 | |||||||||||||
| 6 console.WebView2.wwwroot | |||||||||||||
| 7 jq | |||||||||||||
| 8 jq.My | |||||||||||||
| 9 lsd.My | |||||||||||||
| 10 lsd.lsd | |||||||||||||
| 11 Microsoft.VisualBasic.Windows.Forms | 2 | 6 | |||||||||||
| 12 Microsoft.VisualBasic.Windows.Forms.Console | 2 | ||||||||||||
| 13 Microsoft.VisualBasic.Windows.Forms.SshClient | 6 | 1 |
11→4 Microsoft.VisualBasic.Windows.Forms uses Microsoft.VisualBasic.Windows.Forms.WebView2✕
- Connections
- 2 pairs of types, where a type in Microsoft.VisualBasic.Windows.Forms uses a type in Microsoft.VisualBasic.Windows.Forms.WebView2.
- The types involved
Microsoft.VisualBasic.Windows.Forms.WebViewConsole→Microsoft.VisualBasic.Windows.Forms.WebView2.InboundMessageMicrosoft.VisualBasic.Windows.Forms.WebViewConsole→Microsoft.VisualBasic.Windows.Forms.WebView2.WebViewConsoleHost
- Direction
- Microsoft.VisualBasic.Windows.Forms uses Microsoft.VisualBasic.Windows.Forms.WebView2, so a change to Microsoft.VisualBasic.Windows.Forms.WebView2 can break Microsoft.VisualBasic.Windows.Forms, while a change to Microsoft.VisualBasic.Windows.Forms can't break Microsoft.VisualBasic.Windows.Forms.WebView2.
- Position
- Below the diagonal: Microsoft.VisualBasic.Windows.Forms uses a module listed above it, which is the healthy direction.
11→5 Microsoft.VisualBasic.Windows.Forms uses Microsoft.VisualBasic.Windows.Forms.Win32✕
- Connections
- 6 pairs of types, where a type in Microsoft.VisualBasic.Windows.Forms uses a type in Microsoft.VisualBasic.Windows.Forms.Win32.
- The types involved
Microsoft.VisualBasic.Windows.Forms.ConsoleControl→Microsoft.VisualBasic.Windows.Forms.Win32.AbstractProcessInterfaceMicrosoft.VisualBasic.Windows.Forms.ConsoleControl→Microsoft.VisualBasic.Windows.Forms.Win32.ProcessEventArgsMicrosoft.VisualBasic.Windows.Forms.IConsoleControl→Microsoft.VisualBasic.Windows.Forms.Win32.AbstractProcessInterfaceMicrosoft.VisualBasic.Windows.Forms.ProcessExistedEventHandler→Microsoft.VisualBasic.Windows.Forms.Win32.ProcessEventArgsMicrosoft.VisualBasic.Windows.Forms.WebViewConsole→Microsoft.VisualBasic.Windows.Forms.Win32.AbstractProcessInterfaceMicrosoft.VisualBasic.Windows.Forms.WebViewConsole→Microsoft.VisualBasic.Windows.Forms.Win32.ProcessEventArgs
- Direction
- Microsoft.VisualBasic.Windows.Forms uses Microsoft.VisualBasic.Windows.Forms.Win32, so a change to Microsoft.VisualBasic.Windows.Forms.Win32 can break Microsoft.VisualBasic.Windows.Forms, while a change to Microsoft.VisualBasic.Windows.Forms can't break Microsoft.VisualBasic.Windows.Forms.Win32.
- Position
- Below the diagonal: Microsoft.VisualBasic.Windows.Forms uses a module listed above it, which is the healthy direction.
12→11 Microsoft.VisualBasic.Windows.Forms.Console uses Microsoft.VisualBasic.Windows.Forms✕
- Connections
- 2 pairs of types, where a type in Microsoft.VisualBasic.Windows.Forms.Console uses a type in Microsoft.VisualBasic.Windows.Forms.
- The types involved
Microsoft.VisualBasic.Windows.Forms.Console.TerminalBuffer→Microsoft.VisualBasic.Windows.Forms.AnsiTerminalStateMicrosoft.VisualBasic.Windows.Forms.Console.TerminalControl→Microsoft.VisualBasic.Windows.Forms.ConsoleControl
- Direction
- Microsoft.VisualBasic.Windows.Forms.Console uses Microsoft.VisualBasic.Windows.Forms, so a change to Microsoft.VisualBasic.Windows.Forms can break Microsoft.VisualBasic.Windows.Forms.Console, while a change to Microsoft.VisualBasic.Windows.Forms.Console can't break Microsoft.VisualBasic.Windows.Forms.
- Position
- Below the diagonal: Microsoft.VisualBasic.Windows.Forms.Console uses a module listed above it, which is the healthy direction.
13→5 Microsoft.VisualBasic.Windows.Forms.SshClient uses Microsoft.VisualBasic.Windows.Forms.Win32✕
- Connections
- 6 pairs of types, where a type in Microsoft.VisualBasic.Windows.Forms.SshClient uses a type in Microsoft.VisualBasic.Windows.Forms.Win32.
- The types involved
Microsoft.VisualBasic.Windows.Forms.SshClient.LocalShellInterface→Microsoft.VisualBasic.Windows.Forms.Win32.AbstractProcessInterfaceMicrosoft.VisualBasic.Windows.Forms.SshClient.LocalShellInterface→Microsoft.VisualBasic.Windows.Forms.Win32.ConsoleInputModeMicrosoft.VisualBasic.Windows.Forms.SshClient.LocalShellInterface→Microsoft.VisualBasic.Windows.Forms.Win32.IEditableInputLineMicrosoft.VisualBasic.Windows.Forms.SshClient.SshProcessInterface→Microsoft.VisualBasic.Windows.Forms.Win32.AbstractProcessInterfaceMicrosoft.VisualBasic.Windows.Forms.SshClient.SshProcessInterface→Microsoft.VisualBasic.Windows.Forms.Win32.ConsoleInputModeMicrosoft.VisualBasic.Windows.Forms.SshClient.SshWinFormConsole→Microsoft.VisualBasic.Windows.Forms.Win32.ProcessEventArgs
- Direction
- Microsoft.VisualBasic.Windows.Forms.SshClient uses Microsoft.VisualBasic.Windows.Forms.Win32, so a change to Microsoft.VisualBasic.Windows.Forms.Win32 can break Microsoft.VisualBasic.Windows.Forms.SshClient, while a change to Microsoft.VisualBasic.Windows.Forms.SshClient can't break Microsoft.VisualBasic.Windows.Forms.Win32.
- Position
- Below the diagonal: Microsoft.VisualBasic.Windows.Forms.SshClient uses a module listed above it, which is the healthy direction.
13→11 Microsoft.VisualBasic.Windows.Forms.SshClient uses Microsoft.VisualBasic.Windows.Forms✕
- Connections
- 1 pair of types, where a type in Microsoft.VisualBasic.Windows.Forms.SshClient uses a type in Microsoft.VisualBasic.Windows.Forms.
- The types involved
Microsoft.VisualBasic.Windows.Forms.SshClient.SshWinFormConsole→Microsoft.VisualBasic.Windows.Forms.WebViewConsole
- Direction
- Microsoft.VisualBasic.Windows.Forms.SshClient uses Microsoft.VisualBasic.Windows.Forms, so a change to Microsoft.VisualBasic.Windows.Forms can break Microsoft.VisualBasic.Windows.Forms.SshClient, while a change to Microsoft.VisualBasic.Windows.Forms.SshClient can't break Microsoft.VisualBasic.Windows.Forms.
- Position
- Below the diagonal: Microsoft.VisualBasic.Windows.Forms.SshClient uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with SShClient.vbproj; Resolve the 16 EmptyCatchBlock finding(s) in Explicit Debt — start with LocalShellInterface.vb (7), SshProcessInterface.vb (3), WebViewConsole.vb (3).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with SShClient.vbproj. | +6.5 pts | Low | ADR Quality |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +11.7 pts | Medium | CI/CD gates |
| Resolve the 4 redundant comment finding(s) in Comment Value — start with ProcessInterface.vb (2), LocalShellInterface.vb, ConsoleControl.vb. | +2.8 pts | Low | Comment Value |
| Resolve the 16 EmptyCatchBlock finding(s) in Explicit Debt — start with LocalShellInterface.vb (7), SshProcessInterface.vb (3), WebViewConsole.vb (3). | +4.0 pts | Medium | Explicit Debt |
| Resolve the 1 OnErrorResumeSwallow finding(s) in Explicit Debt — start with AbstractProcessInterface.vb. | +2.9 pts | Low | Explicit Debt |
| Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes. | +3.9 pts | Medium | Library API & versioning |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.4 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +2.9 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| SShClient/LocalShellInterface.vb | 1.7 | Slop | Explicit Debt: EmptyCatchBlock |
| console/Win32/AbstractProcessInterface.vb | 2.7 | Slop | Explicit Debt: OnErrorResumeSwallow |
| console/WebView2/WebViewConsole.vb | 2.8 | Slop | Explicit Debt: EmptyCatchBlock |
| SShClient/SshProcessInterface.vb | 3.6 | Slop | Explicit Debt: EmptyCatchBlock |
| console/WinForm/ConsoleControl.vb | 6.7 | Mixed | Cyclomatic Complexity: ConsoleControl.richTextBoxConsole_KeyDown (cyclomatic 42) |
| console/Win32/ProcessInterface.vb | 6.9 | Mixed | Explicit Debt: EmptyCatchBlock |
| console/WebView2/wwwroot/ansi-parser.js | 7.1 | Mixed | Cyclomatic Complexity: ansi-parser.AnsiParser.dispatchCsi (cyclomatic 33) |
| bash/lsd/FileSystemScanner.vb | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| bash/lsd/LsRenderer.vb | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| console/WebView2/wwwroot/terminal-input.js | 7.8 | Mixed | Cyclomatic Complexity: terminal-input.TerminalInput.handleKeyDown (cyclomatic 46) |
| console/WebView2/TerminalMessage.vb | 7.8 | Mixed | Cyclomatic Complexity: TerminalMessage.Parse (cyclomatic 20) |
| console/WinForm/TerminalControl.vb | 7.8 | Mixed | Cyclomatic Complexity: TerminalControl.RenderToRichTextBox (cyclomatic 20) |
| console/WebView2/wwwroot/terminal-renderer.js | 7.8 | Mixed | Cyclomatic Complexity: terminal-renderer.TerminalRenderer.wrapRun (cyclomatic 17) |
| console/WinForm/TerminalBuffer.vb | 7.8 | Mixed | Cognitive Complexity: TerminalBuffer.EraseInDisplay (cognitive 26) |
| console/AnsiEscapeRenderer.vb | 7.8 | Mixed | Cognitive Complexity: AnsiEscapeRenderer.ParseAndApply (cognitive 20) |
| console.sln | 8.5 | Near-clean | Solution Shape: Solution references a project that does not exist |
| bash/bash.slnx | 8.5 | Near-clean | Solution Shape: Solution references 2 projects that do not exist |
| bash/jq/jq.vbproj | 9.5 | Near-clean | Solution Shape: Thin analysable surface across projects: jq |
| test/test.vbproj | 9.5 | Near-clean | Solution Shape: Thin analysable surface across projects: test |
| SShClient/SShClient.vbproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey 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. All 34 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 34 dimensions across the health lenses
- 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, 92 of 99 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 or a scanner, 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 |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ 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 |
Run transparency — what happened this run
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(521,5): error MSB3202: The project file "/GCModeller/src/runtime/sciBASIC#/Microsoft.VisualBasic.Core/src/Core.vbproj" was not found. [console.sln].
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Project file not found: '/GCModeller/src/runtime/sciBASIC#/Microsoft.VisualBasic.Core/src/Core.vbproj'.
- D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X20 Mistyped argument guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for test/test.vbproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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 — an in-process token-stream comparison over sliding windows, with type-aware normalization — so 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
Dimensions
D1 · Cyclomatic Complexity
20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was terminal-input.TerminalInput.handleKeyDown at 46. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being LocalShellInterface.WriteInput at 63 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: console/AnsiEscapeRenderer.vb (AnsiEscapeRenderer.ApplySgr at 30), console/WebView2/WebViewConsole.vb (WebViewConsole.ToDomKey at 22), console/WinForm/TerminalBuffer.vb (TerminalBuffer.HandleCsi at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with terminal-input.TerminalInput.handleKeyDown (cyclomatic 46), LocalShellInterface.CmdFile (cyclomatic 43), ConsoleControl.richTextBoxConsole_KeyDown (cyclomatic 42). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 15 together lifts Cyclomatic Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
29 method(s) exceeded the cognitive complexity threshold of 15; the worst was handleKeyDown at 64.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with handleKeyDown (cognitive 64), ConsoleControl.richTextBoxConsole_KeyDown (cognitive 51), LocalShellInterface.CmdFile (cognitive 37). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 5.0 to about 6.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with LocalShellInterface.vb, WebViewConsole.vb. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with LocalShellInterface.vb, WebViewConsole.vb. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with LocalShellInterface.vb. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
5 duplicated block group(s) detected. 2.7 % of the production lines (207 of 7,539) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with WebViewConsole.vb (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with WebViewConsole.vb. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (39 corresponding lines) finding(s) in Code Duplication — start with LocalShellInterface.vb. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 89 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 2 direct `PackageReference`(s), and 85 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: console/WinForm/ConsoleControl.vb (20×42=840); SShClient/LocalShellInterface.vb (6×22=132)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with ConsoleControl.vb, LocalShellInterface.vb. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
14 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is SShClient/LocalShellInterface.vb. Counted over 21 of the 31 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Small-team knowledge concentration finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
21 deducted debt markers + unmeasured dead symbols across 7539 LoC in the .NET projects (1.8/KLoC) → score 6.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 16 EmptyCatchBlock finding(s) in Explicit Debt — start with LocalShellInterface.vb (7), SshProcessInterface.vb (3), WebViewConsole.vb (3). — One of this dimension's main actionable groups (16 issue-level).
- Resolve the 1 OnErrorResumeSwallow finding(s) in Explicit Debt — start with AbstractProcessInterface.vb. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with AbstractProcessInterface.vb (4). — One of this dimension's main actionable groups (4 warning-level).
D18 · Solution Shape
5 projects, 35 source files, 7615 hand-written lines of code (7539 production / 76 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 411 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 3 inter-project edges (build status unknown — did not finish). Measured across 2 solutions loaded as one workspace: `console.sln`, `bash/bash.slnx`.
What to do
- Resolve the 2 Thin analysable surface across projects finding(s) in Solution Shape — start with jq.vbproj, test.vbproj. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Solution references a project that does not exist finding(s) in Solution Shape — start with console.sln. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Solution references 2 projects that do not exist finding(s) in Solution Shape — start with bash.slnx. — One of this dimension's main actionable groups (1 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with SShClient.vbproj. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
9 of 278 judged comments only repeat the code they sit on (3.2 %). 68 comment(s) in another language or script were not judged.
What to do
- Resolve the 4 redundant comment finding(s) in Comment Value — start with ProcessInterface.vb (2), LocalShellInterface.vb, ConsoleControl.vb. — One of this dimension's main actionable groups (4 recommendation-level).
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D27 · Navigability
72 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 21 of the 31 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
- The root README is 85 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
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.
P10 · Library API & versioning
- No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
- Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — 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 was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `SShClient/SShClient.vbproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — SShClient/SShClient.vbproj:22
What to do
- Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — 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.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 68% | Adequate | Acceptable, with room to improve. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 28% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Checked 3 of 9 | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 6 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — AX6 reached only 22% of this repository's production lines — vbnet (7,539 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~76 lines of test source are present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency does not read Visual Basic yet; not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (7,539 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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"]`.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: 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
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens 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 lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X28 Index access outside its own emptiness guard — X28 reached only 22% of this repository's production lines — vbnet (7,539 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 17 finding(s)
- EmptyCatchBlock SShClient/LocalShellInterface.vb:611
- EmptyCatchBlock SShClient/LocalShellInterface.vb:1197
- EmptyCatchBlock SShClient/LocalShellInterface.vb:1782
- EmptyCatchBlock SShClient/LocalShellInterface.vb:1786
- EmptyCatchBlock SShClient/LocalShellInterface.vb:1789
- EmptyCatchBlock SShClient/LocalShellInterface.vb:1848
- EmptyCatchBlock SShClient/LocalShellInterface.vb:1880
- EmptyCatchBlock SShClient/SshProcessInterface.vb:364
- EmptyCatchBlock SShClient/SshProcessInterface.vb:371
- EmptyCatchBlock SShClient/SshProcessInterface.vb:380
- EmptyCatchBlock bash/lsd/FileSystemScanner.vb:175
- EmptyCatchBlock bash/lsd/LsRenderer.vb:200
- EmptyCatchBlock console/WebView2/WebViewConsole.vb:441
- EmptyCatchBlock console/WebView2/WebViewConsole.vb:547
- EmptyCatchBlock console/WebView2/WebViewConsole.vb:1046
- EmptyCatchBlock console/Win32/ProcessInterface.vb:200
- OnErrorResumeSwallow console/Win32/AbstractProcessInterface.vb:285
Serious — 68 finding(s)
- TodoComment console/Win32/AbstractProcessInterface.vb:274
- TodoComment console/Win32/AbstractProcessInterface.vb:278
- TodoComment console/Win32/AbstractProcessInterface.vb:279
- TodoComment console/Win32/AbstractProcessInterface.vb:309
- Hotspot: console/WinForm/ConsoleControl.vb console/WinForm/ConsoleControl.vb:390
- Hotspot: SShClient/LocalShellInterface.vb SShClient/LocalShellInterface.vb:1379
- FileTooLong: SShClient/LocalShellInterface.vb SShClient/LocalShellInterface.vb
- FileTooLong: WebView2/WebViewConsole.vb console/WebView2/WebViewConsole.vb
- TooManyMethods: LocalShellInterface SShClient/LocalShellInterface.vb
- TooManyMethods: WebViewConsole console/WebView2/WebViewConsole.vb
- Duplicated block (6 lines × 2) console/WebView2/WebViewConsole.vb:914
- Duplicated block (6 lines × 2) console/WebView2/WebViewConsole.vb:909
- terminal-input.TerminalInput.handleKeyDown (cyclomatic 46) console/WebView2/wwwroot/terminal-input.js:230
- LocalShellInterface.CmdFile (cyclomatic 43) SShClient/LocalShellInterface.vb:1206
- ConsoleControl.richTextBoxConsole_KeyDown (cyclomatic 42) console/WinForm/ConsoleControl.vb:390
- ansi-parser.AnsiParser.dispatchCsi (cyclomatic 33) console/WebView2/wwwroot/ansi-parser.js:354
- ansi-parser.AnsiParser.applySgr (cyclomatic 30) console/WebView2/wwwroot/ansi-parser.js:473
- ansi-parser.AnsiParser.handleEscape (cyclomatic 23) console/WebView2/wwwroot/ansi-parser.js:238
- LocalShellInterface.CmdCut (cyclomatic 22) SShClient/LocalShellInterface.vb:1379
- TerminalMessage.Parse (cyclomatic 20) console/WebView2/TerminalMessage.vb:189
- TerminalControl.RenderToRichTextBox (cyclomatic 20) console/WinForm/TerminalControl.vb:216
- LocalShellInterface.CmdGrep (cyclomatic 19) SShClient/LocalShellInterface.vb:999
- LocalShellInterface.CmdWc (cyclomatic 18) SShClient/LocalShellInterface.vb:1086
- LocalShellInterface.CmdCal (cyclomatic 17) SShClient/LocalShellInterface.vb:2181
- terminal-renderer.TerminalRenderer.wrapRun (cyclomatic 17) console/WebView2/wwwroot/terminal-renderer.js:217
- LocalShellInterface.CmdUname (cyclomatic 16) SShClient/LocalShellInterface.vb:1675
- LocalShellInterface.HandleSsh (cyclomatic 16) SShClient/LocalShellInterface.vb:2234
- Solution references a project that does not exist console.sln
- Solution references 2 projects that do not exist bash/bash.slnx
- handleKeyDown (cognitive 64) console/WebView2/wwwroot/terminal-input.js:230
- ConsoleControl.richTextBoxConsole_KeyDown (cognitive 51) console/WinForm/ConsoleControl.vb:390
- LocalShellInterface.CmdFile (cognitive 37) SShClient/LocalShellInterface.vb:1206
- LocalShellInterface.CmdCut (cognitive 36) SShClient/LocalShellInterface.vb:1379
- ansi-parser.AnsiParser.applySgr (cognitive 30) console/WebView2/wwwroot/ansi-parser.js:473
- TerminalControl.RenderToRichTextBox (cognitive 28) console/WinForm/TerminalControl.vb:216
- TerminalBuffer.EraseInDisplay (cognitive 26) console/WinForm/TerminalBuffer.vb:291
- LocalShellInterface.CmdGrep (cognitive 25) SShClient/LocalShellInterface.vb:999
- terminal-renderer.TerminalRenderer.wrapRun (cognitive 25) console/WebView2/wwwroot/terminal-renderer.js:217
- LocalShellInterface.CmdWc (cognitive 23) SShClient/LocalShellInterface.vb:1086
- LocalShellInterface.HandleSsh (cognitive 23) SShClient/LocalShellInterface.vb:2234
- LocalShellInterface.CmdLs (cognitive 22) SShClient/LocalShellInterface.vb:533
- LocalShellInterface.CmdCp (cognitive 22) SShClient/LocalShellInterface.vb:795
- TerminalBuffer.ProcessAnsi (cognitive 21) console/WinForm/TerminalBuffer.vb:353
- LocalShellInterface.ParseTokens (cognitive 21) SShClient/LocalShellInterface.vb:2325
- AnsiEscapeRenderer.ParseAndApply (cognitive 20) console/AnsiEscapeRenderer.vb:71
- AnsiEscapeRenderer.ApplyExtendedColor (cognitive 20) console/AnsiEscapeRenderer.vb:248
- TerminalMessage.Parse (cognitive 19) console/WebView2/TerminalMessage.vb:189
- ansi-parser.findIncompleteTail (cognitive 18) console/WebView2/wwwroot/ansi-parser.js:73
- LocalShellInterface.CmdFind (cognitive 17) SShClient/LocalShellInterface.vb:1142
- SshProcessInterface.ReadLoop (cognitive 17) SShClient/SshProcessInterface.vb:189
- ansi-parser.AnsiParser.handleEscape (cognitive 17) console/WebView2/wwwroot/ansi-parser.js:238
- LocalShellInterface.CmdLn (cognitive 16) SShClient/LocalShellInterface.vb:1254
- LocalShellInterface.CmdPs (cognitive 16) SShClient/LocalShellInterface.vb:1766
- MethodTooLong: LocalShellInterface.WriteInput SShClient/LocalShellInterface.vb:88
- ClassTooLong: ConsoleControl console/WinForm/ConsoleControl.vb
- Members sharing a duplicated core (4 members, 50+ identical tokens) console/WebView2/WebViewConsole.vb:909
- Edited copy of a member (39 corresponding lines) SShClient/LocalShellInterface.vb:911
- Edited copy of a member (15 corresponding lines) SShClient/LocalShellInterface.vb:1925
- Edited copy of a member (13 corresponding lines) console/Win32/AbstractProcessInterface.vb:220
- Edited copy of a member (11 corresponding lines) SShClient/SshProcessInterface.vb:269
- Edited copy of a member (7 corresponding lines) console/WebView2/WebViewConsole.vb:964
- Edited copy of a member (2 corresponding lines) console/WebView2/WebViewConsole.vb:417
- Duplicated block (9 lines × 2) SShClient/LocalShellInterface.vb:1729
- Duplicated block (9–10 lines × 2) console/WebView2/WebViewConsole.vb:938
- Duplicated block (7 lines × 2) console/WinForm/ConsoleControl.vb:760
- Coverage not measured — test suite did not build
- No CI pipeline
- NuGet dependencies are not locked
Minor — 13 finding(s)
- redundant comment SShClient/LocalShellInterface.vb:2289
- redundant comment console/Win32/ProcessInterface.vb:72
- redundant comment console/Win32/ProcessInterface.vb:156
- redundant comment console/WinForm/ConsoleControl.vb:315
- Thin analysable surface across projects: jq bash/jq/jq.vbproj
- Thin analysable surface across projects: test test/test.vbproj
- Small-team knowledge concentration
- No ADRs found SShClient/SShClient.vbproj:6
- Thin README README.md:1
- No ADRs
- No explicit versioning
- No SAST
- No dependency-update automation SShClient/SShClient.vbproj:22
Minor — 1 finding(s)
- doc comments repeat the names console/WebView2/WebViewConsole.vb:408
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8a51e8de91a24d78b5558ee7f35fdb33/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8a51e8de91a24d78b5558ee7f35fdb33/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: 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 | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); 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 | — |
| 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 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-854dc176c2a84317aa92ce845bb60ffd | 0 | artifacts/raw/osv-scanner.json |