Executive summary
JordanMarr/Agent.NET falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 53 out of 100 and is rated Adequate, and all three of its critical findings are security problems in the build pipeline.
Production Readiness, at 37, 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 a diagnostic log would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 65.
Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 3,450 lines, about €6,600 to rebuild.
If Production Readiness rose from 37 to 70, the lowest score rated Strong, the score would rise from 53 to about 65.
New since the last survey: 8 findings
- Cognitive Complexity · DurableId.tryGetCalledMethodName (cognitive 29) src/AgentNet/DurableId.fs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/StockAdvisorCS/AgentChatSample.cs
- Code Duplication · Duplicated block (41–45 lines × 2) src/AgentNet/WorkflowBuilder.fs
- Code Duplication · Duplicated block (8 lines × 2) src/AgentNet/Workflow.fs
- Code Duplication · Duplicated block (14 lines × 2) src/AgentNet/DurableId.fs
- Code Coverage · No test project references StockAdvisorCS src/StockAdvisorCS/StockAdvisorCS.csproj
- Code Coverage · No test project references StockAdvisorFS src/StockAdvisorFS/StockAdvisorFS.fsproj
- Code Coverage · No test project references Samples.DurableOcr src/Samples.DurableOcr/Samples.DurableOcr.fsproj
Rebuild cost: about €6,600 · Estimate
| Cost to rebuild | €2,200 to €11,000, for 37 to 116 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 53. 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: 3,450 lines of product code |
| Comment lines | The estimate prices 3,347 lines. Comment lines count towards the size of 3,450 lines but aren't priced as work. |
| 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 (global) | 2 AgentNet | 3 AgentNet.ChatOptionsHelpers | 4 AgentNet.InProcess | 5 AgentNet.Interop | 6 AgentNet.Task | 7 AutoGeneratedProgram | 8 Program | 9 Samples.DurableOcr.Program | 10 StockAdvisorCS | 11 StockAdvisorFS.AgentChatSample | 12 StockAdvisorFS.SingleAnalysisSample | 13 StockAdvisorFS.StockTools | 14 StockAdvisorFS.WorkflowSample | 15 AgentNet.ChatAgentExtensions | 16 AgentNet.DurableId | 17 AgentNet.Executor | 18 AgentNet.InProcess.Polly.PollyDecorators | 19 AgentNet.InProcess.Workflow | 20 AgentNet.InProcess.Workflow.Durable | 21 AgentNet.InProcess.Workflow.InProcess | 22 AgentNet.InProcess.WorkflowBuilderExtensions | 23 AgentNet.MAF | 24 AgentNet.PackedTypedStepModule | 25 AgentNet.TypedAgent | 26 AgentNet.Workflow | 27 AgentNet.WorkflowCE | 28 AgentNet.WorkflowContextModule | 29 AgentNet.WorkflowInternal |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||||||
| 2 AgentNet | |||||||||||||||||||||||||||||
| 3 AgentNet.ChatOptionsHelpers | |||||||||||||||||||||||||||||
| 4 AgentNet.InProcess | |||||||||||||||||||||||||||||
| 5 AgentNet.Interop | |||||||||||||||||||||||||||||
| 6 AgentNet.Task | |||||||||||||||||||||||||||||
| 7 AutoGeneratedProgram | |||||||||||||||||||||||||||||
| 8 Program | |||||||||||||||||||||||||||||
| 9 Samples.DurableOcr.Program | |||||||||||||||||||||||||||||
| 10 StockAdvisorCS | |||||||||||||||||||||||||||||
| 11 StockAdvisorFS.AgentChatSample | |||||||||||||||||||||||||||||
| 12 StockAdvisorFS.SingleAnalysisSample | |||||||||||||||||||||||||||||
| 13 StockAdvisorFS.StockTools | |||||||||||||||||||||||||||||
| 14 StockAdvisorFS.WorkflowSample | |||||||||||||||||||||||||||||
| 15 AgentNet.ChatAgentExtensions | 2 | ||||||||||||||||||||||||||||
| 16 AgentNet.DurableId | 2 | ||||||||||||||||||||||||||||
| 17 AgentNet.Executor | 2 | ||||||||||||||||||||||||||||
| 18 AgentNet.InProcess.Polly.PollyDecorators | 1 | ||||||||||||||||||||||||||||
| 19 AgentNet.InProcess.Workflow | 2 | ||||||||||||||||||||||||||||
| 20 AgentNet.InProcess.Workflow.Durable | 1 | 1 | |||||||||||||||||||||||||||
| 21 AgentNet.InProcess.Workflow.InProcess | 2 | ||||||||||||||||||||||||||||
| 22 AgentNet.InProcess.WorkflowBuilderExtensions | 1 | ||||||||||||||||||||||||||||
| 23 AgentNet.MAF | 5 | ||||||||||||||||||||||||||||
| 24 AgentNet.PackedTypedStepModule | 3 | ||||||||||||||||||||||||||||
| 25 AgentNet.TypedAgent | 2 | ||||||||||||||||||||||||||||
| 26 AgentNet.Workflow | 1 | ||||||||||||||||||||||||||||
| 27 AgentNet.WorkflowCE | 2 | ||||||||||||||||||||||||||||
| 28 AgentNet.WorkflowContextModule | 1 | ||||||||||||||||||||||||||||
| 29 AgentNet.WorkflowInternal | 5 |
15→2 AgentNet.ChatAgentExtensions uses AgentNet✕
- Connections
- 2 pairs of types, where a type in AgentNet.ChatAgentExtensions uses a type in AgentNet.
- The types involved
AgentNet.ChatAgentExtensions.ChatAgentExtensions→AgentNet.ChatAgentAgentNet.ChatAgentExtensions.ChatAgentExtensions→AgentNet.ChatAgentConfig
- Direction
- AgentNet.ChatAgentExtensions uses AgentNet, so a change to AgentNet can break AgentNet.ChatAgentExtensions, while a change to AgentNet.ChatAgentExtensions can't break AgentNet.
- Position
- Below the diagonal: AgentNet.ChatAgentExtensions uses a module listed above it, which is the healthy direction.
16→2 AgentNet.DurableId uses AgentNet✕
- Connections
- 2 pairs of types, where a type in AgentNet.DurableId uses a type in AgentNet.
- The types involved
AgentNet.DurableId.DurableId→AgentNet.Executor`2AgentNet.DurableId.DurableId→AgentNet.TypedAgent`2
- Direction
- AgentNet.DurableId uses AgentNet, so a change to AgentNet can break AgentNet.DurableId, while a change to AgentNet.DurableId can't break AgentNet.
- Position
- Below the diagonal: AgentNet.DurableId uses a module listed above it, which is the healthy direction.
17→2 AgentNet.Executor uses AgentNet✕
- Connections
- 2 pairs of types, where a type in AgentNet.Executor uses a type in AgentNet.
- The types involved
AgentNet.Executor.Executor→AgentNet.Executor`2AgentNet.Executor.Executor→AgentNet.TypedAgent`2
- Direction
- AgentNet.Executor uses AgentNet, so a change to AgentNet can break AgentNet.Executor, while a change to AgentNet.Executor can't break AgentNet.
- Position
- Below the diagonal: AgentNet.Executor uses a module listed above it, which is the healthy direction.
18→2 AgentNet.InProcess.Polly.PollyDecorators uses AgentNet✕
- Connections
- 1 pair of types, where a type in AgentNet.InProcess.Polly.PollyDecorators uses a type in AgentNet.
- The types involved
AgentNet.InProcess.Polly.PollyDecorators.PollyDecorators→AgentNet.WorkflowContext
- Direction
- AgentNet.InProcess.Polly.PollyDecorators uses AgentNet, so a change to AgentNet can break AgentNet.InProcess.Polly.PollyDecorators, while a change to AgentNet.InProcess.Polly.PollyDecorators can't break AgentNet.
- Position
- Below the diagonal: AgentNet.InProcess.Polly.PollyDecorators uses a module listed above it, which is the healthy direction.
19→2 AgentNet.InProcess.Workflow uses AgentNet✕
- Connections
- 2 pairs of types, where a type in AgentNet.InProcess.Workflow uses a type in AgentNet.
- The types involved
AgentNet.InProcess.Workflow.Workflow→AgentNet.PackedTypedStepAgentNet.InProcess.Workflow.Workflow→AgentNet.WorkflowDef`3
- Direction
- AgentNet.InProcess.Workflow uses AgentNet, so a change to AgentNet can break AgentNet.InProcess.Workflow, while a change to AgentNet.InProcess.Workflow can't break AgentNet.
- Position
- Below the diagonal: AgentNet.InProcess.Workflow uses a module listed above it, which is the healthy direction.
20→2 AgentNet.InProcess.Workflow.Durable uses AgentNet✕
- Connections
- 1 pair of types, where a type in AgentNet.InProcess.Workflow.Durable uses a type in AgentNet.
- The types involved
AgentNet.InProcess.Workflow.Durable.Durable→AgentNet.WorkflowDef`3
- Direction
- AgentNet.InProcess.Workflow.Durable uses AgentNet, so a change to AgentNet can break AgentNet.InProcess.Workflow.Durable, while a change to AgentNet.InProcess.Workflow.Durable can't break AgentNet.
- Position
- Below the diagonal: AgentNet.InProcess.Workflow.Durable uses a module listed above it, which is the healthy direction.
20→4 AgentNet.InProcess.Workflow.Durable uses AgentNet.InProcess✕
- Connections
- 1 pair of types, where a type in AgentNet.InProcess.Workflow.Durable uses a type in AgentNet.InProcess.
- The types involved
AgentNet.InProcess.Workflow.Durable.DurableRunResult`1→AgentNet.InProcess.PendingRequest
- Direction
- AgentNet.InProcess.Workflow.Durable uses AgentNet.InProcess, so a change to AgentNet.InProcess can break AgentNet.InProcess.Workflow.Durable, while a change to AgentNet.InProcess.Workflow.Durable can't break AgentNet.InProcess.
- Position
- Below the diagonal: AgentNet.InProcess.Workflow.Durable uses a module listed above it, which is the healthy direction.
21→2 AgentNet.InProcess.Workflow.InProcess uses AgentNet✕
- Connections
- 2 pairs of types, where a type in AgentNet.InProcess.Workflow.InProcess uses a type in AgentNet.
- The types involved
AgentNet.InProcess.Workflow.InProcess.InProcess→AgentNet.Executor`2AgentNet.InProcess.Workflow.InProcess.InProcess→AgentNet.WorkflowDef`3
- Direction
- AgentNet.InProcess.Workflow.InProcess uses AgentNet, so a change to AgentNet can break AgentNet.InProcess.Workflow.InProcess, while a change to AgentNet.InProcess.Workflow.InProcess can't break AgentNet.
- Position
- Below the diagonal: AgentNet.InProcess.Workflow.InProcess uses a module listed above it, which is the healthy direction.
22→2 AgentNet.InProcess.WorkflowBuilderExtensions uses AgentNet✕
- Connections
- 1 pair of types, where a type in AgentNet.InProcess.WorkflowBuilderExtensions uses a type in AgentNet.
- The types involved
AgentNet.InProcess.WorkflowBuilderExtensions.WorkflowBuilderExtensions→AgentNet.WorkflowState`3
- Direction
- AgentNet.InProcess.WorkflowBuilderExtensions uses AgentNet, so a change to AgentNet can break AgentNet.InProcess.WorkflowBuilderExtensions, while a change to AgentNet.InProcess.WorkflowBuilderExtensions can't break AgentNet.
- Position
- Below the diagonal: AgentNet.InProcess.WorkflowBuilderExtensions uses a module listed above it, which is the healthy direction.
23→2 AgentNet.MAF uses AgentNet✕
- Connections
- 5 pairs of types, where a type in AgentNet.MAF uses a type in AgentNet.
- The types involved
AgentNet.MAF.MAF→AgentNet.ChatAgentAgentNet.MAF.MAF→AgentNet.ChatAgentConfigAgentNet.MAF.MAF→AgentNet.ChatStreamEventAgentNet.MAF.MAF→AgentNet.ToolBindingsAgentNet.MAF.MAF→AgentNet.ToolDef
- Direction
- AgentNet.MAF uses AgentNet, so a change to AgentNet can break AgentNet.MAF, while a change to AgentNet.MAF can't break AgentNet.
- Position
- Below the diagonal: AgentNet.MAF uses a module listed above it, which is the healthy direction.
24→2 AgentNet.PackedTypedStepModule uses AgentNet✕
- Connections
- 3 pairs of types, where a type in AgentNet.PackedTypedStepModule uses a type in AgentNet.
- The types involved
AgentNet.PackedTypedStepModule.PackedTypedStepModule→AgentNet.PackedTypedStepAgentNet.PackedTypedStepModule.PackedTypedStepModule→AgentNet.TypedWorkflowStep`2AgentNet.PackedTypedStepModule.PackedTypedStepModule→AgentNet.WorkflowContext
- Direction
- AgentNet.PackedTypedStepModule uses AgentNet, so a change to AgentNet can break AgentNet.PackedTypedStepModule, while a change to AgentNet.PackedTypedStepModule can't break AgentNet.
- Position
- Below the diagonal: AgentNet.PackedTypedStepModule uses a module listed above it, which is the healthy direction.
25→2 AgentNet.TypedAgent uses AgentNet✕
- Connections
- 2 pairs of types, where a type in AgentNet.TypedAgent uses a type in AgentNet.
- The types involved
AgentNet.TypedAgent.TypedAgent→AgentNet.ChatAgentAgentNet.TypedAgent.TypedAgent→AgentNet.TypedAgent`2
- Direction
- AgentNet.TypedAgent uses AgentNet, so a change to AgentNet can break AgentNet.TypedAgent, while a change to AgentNet.TypedAgent can't break AgentNet.
- Position
- Below the diagonal: AgentNet.TypedAgent uses a module listed above it, which is the healthy direction.
26→2 AgentNet.Workflow uses AgentNet✕
- Connections
- 1 pair of types, where a type in AgentNet.Workflow uses a type in AgentNet.
- The types involved
AgentNet.Workflow.Workflow→AgentNet.WorkflowDef`3
- Direction
- AgentNet.Workflow uses AgentNet, so a change to AgentNet can break AgentNet.Workflow, while a change to AgentNet.Workflow can't break AgentNet.
- Position
- Below the diagonal: AgentNet.Workflow uses a module listed above it, which is the healthy direction.
27→2 AgentNet.WorkflowCE uses AgentNet✕
- Connections
- 2 pairs of types, where a type in AgentNet.WorkflowCE uses a type in AgentNet.
- The types involved
AgentNet.WorkflowCE.WorkflowCE→AgentNet.Step`2AgentNet.WorkflowCE.WorkflowCE→AgentNet.WorkflowBuilder
- Direction
- AgentNet.WorkflowCE uses AgentNet, so a change to AgentNet can break AgentNet.WorkflowCE, while a change to AgentNet.WorkflowCE can't break AgentNet.
- Position
- Below the diagonal: AgentNet.WorkflowCE uses a module listed above it, which is the healthy direction.
28→2 AgentNet.WorkflowContextModule uses AgentNet✕
- Connections
- 1 pair of types, where a type in AgentNet.WorkflowContextModule uses a type in AgentNet.
- The types involved
AgentNet.WorkflowContextModule.WorkflowContextModule→AgentNet.WorkflowContext
- Direction
- AgentNet.WorkflowContextModule uses AgentNet, so a change to AgentNet can break AgentNet.WorkflowContextModule, while a change to AgentNet.WorkflowContextModule can't break AgentNet.
- Position
- Below the diagonal: AgentNet.WorkflowContextModule uses a module listed above it, which is the healthy direction.
29→2 AgentNet.WorkflowInternal uses AgentNet✕
- Connections
- 5 pairs of types, where a type in AgentNet.WorkflowInternal uses a type in AgentNet.
- The types involved
AgentNet.WorkflowInternal.WorkflowInternal→AgentNet.Executor`2AgentNet.WorkflowInternal.WorkflowInternal→AgentNet.PackedTypedStepAgentNet.WorkflowInternal.WorkflowInternal→AgentNet.Step`2AgentNet.WorkflowInternal.WorkflowInternal→AgentNet.TypedWorkflowStep`2AgentNet.WorkflowInternal.WorkflowInternal→AgentNet.WorkflowContext
- Direction
- AgentNet.WorkflowInternal uses AgentNet, so a change to AgentNet can break AgentNet.WorkflowInternal, while a change to AgentNet.WorkflowInternal can't break AgentNet.
- Position
- Below the diagonal: AgentNet.WorkflowInternal 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
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A05:2025 — Injection | 3 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with StockAdvisorCS.csproj; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with StockAdvisorCS.csproj. | +5.8 pts | Low | ADR Quality |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.1 pts | Medium | Observability |
| 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. | +5.4 pts | Medium | Architecture documentation |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.1 pts | Medium | Release Hygiene |
| 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. | +1.9 pts | Medium | Documentation (README) |
| A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does. | +1.8 pts | Medium | Stateful singletons |
| Resolve the 1 No test project references Samples.DurableOcr finding(s) in Code Coverage — start with Samples.DurableOcr.fsproj. | +0.8 pts | Low | Code Coverage |
| Resolve the 1 No test project references StockAdvisorCS finding(s) in Code Coverage — start with StockAdvisorCS.csproj. | +0.8 pts | Low | Code Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/AgentNet/ChatAgent.fs | 7.8 | Mixed | Cyclomatic Complexity: ChatOptionsHelpers.merge (cyclomatic 20) |
| src/AgentNet/Workflow.fs | 7.8 | Mixed | Cyclomatic Complexity: PackedTypedStepModule.pack (cyclomatic 18) |
| src/AgentNet/DurableId.fs | 7.8 | Mixed | Cognitive Complexity: DurableId.tryGetCalledMethodName (cognitive 29) |
| src/StockAdvisorFS/AgentChatSample.fs | 7.8 | Mixed | Cognitive Complexity: AgentChatSample.chatLoop (cognitive 18) |
| src/StockAdvisorCS/AgentChatSample.cs | 7.8 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| src/StockAdvisorCS/StockAdvisorCS.csproj | 8.0 | Near-clean | Code Coverage: No test project references StockAdvisorCS |
| src/AgentNet/AgentFramework.fs | 8.5 | Near-clean | Cognitive Complexity: MAF.build (cognitive 25) |
| src/AgentNet/WorkflowBuilder.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (41–45 lines × 2) |
| src/AgentNet.Interop/Executors.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (16 lines × 2) |
| src/StockAdvisorCS/StockTools.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| src/StockAdvisorFS/StockAdvisorFS.fsproj | 8.5 | Near-clean | Code Coverage: No test project references StockAdvisorFS |
| src/Samples.DurableOcr/Samples.DurableOcr.fsproj | 8.5 | Near-clean | Code Coverage: No test project references Samples.DurableOcr |
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 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 42 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, 24 of 37 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
- 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: `dotnet list package` exited 1 with no output.
- D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 246 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 1 hold 3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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: Cannot open project 'src/AgentNet/AgentNet.fsproj' because the file extension '.fsproj' is not associated with a language.
- 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 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (2,878 lines, 83% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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.
- D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — 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. `src/AgentNet.Interop/Executors.cs`, `src/StockAdvisorCS/WorkflowSample.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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'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.
- 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.
- 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'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.
- 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'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.
- 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'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.
- 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'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.
- 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'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.
- 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'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.
- 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'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.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ChatOptionsHelpers.merge at 20.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ChatOptionsHelpers.merge (cyclomatic 20), PackedTypedStepModule.pack (cyclomatic 18). — 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 2 together lifts Cyclomatic Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was ChatOptionsHelpers.merge at 32.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with ChatOptionsHelpers.merge (cognitive 32), DurableId.tryGetCalledMethodName (cognitive 29), MAF.build (cognitive 25). — 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 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
7 duplicated block group(s) detected. 5.2 % of the production lines (180 of 3,450) are in a reported copy. One further row reports members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with AgentChatSample.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (41–45 lines × 2) finding(s) in Code Duplication — start with WorkflowBuilder.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with Executors.cs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 4 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 54.7%.
What to do
- Resolve the 1 No test project references StockAdvisorCS finding(s) in Code Coverage — start with StockAdvisorCS.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references StockAdvisorFS finding(s) in Code Coverage — start with StockAdvisorFS.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references Samples.DurableOcr finding(s) in Code Coverage — start with Samples.DurableOcr.fsproj. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 118 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 13 direct `PackageReference`(s), and 108 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
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 572 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (83% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 3 unit(s).
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 StockAdvisorCS.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 2 projects flagged as possibly oversized/incoherent.
D27 · Navigability
95 % of calls cross a namespace and 1 % go through an interface, but 54 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `src/AgentNet.Interop/Executors.cs` (line 16, line 28, line 43, …), `src/StockAdvisorCS/WorkflowSample.cs` (line 27, line 51, line 78) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 2 of those file(s) — `src/AgentNet.Interop/Executors.cs`, `src/StockAdvisorCS/WorkflowSample.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 17 of the 25 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.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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 7 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
AX2 · Stateful singletons
- `AgentChatSample` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_cachedAgent; e.g. `_cachedAgent` at line 92). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/StockAdvisorCS/AgentChatSample.cs:13
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX8 · Test isolation
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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.
- `src/AgentNet.InProcess.Polly/AgentNet.InProcess.Polly.fsproj` 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`. — src/AgentNet.InProcess.Polly/AgentNet.InProcess.Polly.fsproj:31
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — 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.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `chatLoop` is async and calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. — src/StockAdvisorFS/AgentChatSample.fs:80
What to do
- F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
X20 · Mistyped argument guard
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 96% | Exemplary | Strongest area. |
| Architecture | 72% | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 37% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- 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 — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~2680 lines of test source are present (.fs) 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.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1086 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (3,450 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"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- 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) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 43 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 CQRS handler(s))
- ED5 Idempotency — 2 mutating command handler(s)/consumer(s) detected and 2 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 17% of this repository's production lines — fsharp (2,878 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- 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 data present for 12 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — 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.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — X1 reached only 17% of this repository's production lines — fsharp (2,878 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 17% of this repository's production lines — fsharp (2,878 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 17% of this repository's production lines — fsharp (2,878 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 17% of this repository's production lines — fsharp (2,878 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — X2 reached only 17% of this repository's production lines — fsharp (2,878 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 17% of this repository's production lines — fsharp (2,878 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 17% of this repository's production lines — fsharp (2,878 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 3 finding(s)
- REDACTED
- REDACTED
- REDACTED
Serious — 23 finding(s)
- Process-global static state: AgentChatSample src/StockAdvisorCS/AgentChatSample.cs:13
- ChatOptionsHelpers.merge (cyclomatic 20) src/AgentNet/ChatAgent.fs:53
- PackedTypedStepModule.pack (cyclomatic 18) src/AgentNet/Workflow.fs:136
- ChatOptionsHelpers.merge (cognitive 32) src/AgentNet/ChatAgent.fs:53
- DurableId.tryGetCalledMethodName (cognitive 29) src/AgentNet/DurableId.fs:133
- MAF.build (cognitive 25) src/AgentNet/AgentFramework.fs:136
- AgentChatSample.chatLoop (cognitive 18) src/StockAdvisorFS/AgentChatSample.fs:49
- REDACTED
- Edited copy of a member (8 corresponding lines) src/StockAdvisorCS/AgentChatSample.cs:18
- Duplicated block (41–45 lines × 2) src/AgentNet/WorkflowBuilder.fs:56
- Duplicated block (16 lines × 2) src/AgentNet.Interop/Executors.cs:64
- Duplicated block (9–10 lines × 2) src/StockAdvisorFS/AgentChatSample.fs:16
- Duplicated block (8 lines × 2) src/AgentNet/Workflow.fs:265
- Duplicated block (5 lines × 2) src/StockAdvisorCS/StockTools.cs:116
- Duplicated block (7 lines × 2) src/StockAdvisorCS/AgentChatSample.cs:19
- Duplicated block (14 lines × 2) src/AgentNet/DurableId.fs:44
- No test project references StockAdvisorCS src/StockAdvisorCS/StockAdvisorCS.csproj
- No test project references StockAdvisorFS src/StockAdvisorFS/StockAdvisorFS.fsproj
- No test project references Samples.DurableOcr src/Samples.DurableOcr/Samples.DurableOcr.fsproj
- Test suite runs only after the merge
- No structured logging
- Sync-over-async blocking src/StockAdvisorFS/AgentChatSample.fs:80
- NuGet dependencies are not locked
Minor — 11 finding(s)
- No ADRs found src/StockAdvisorCS/StockAdvisorCS.csproj:4
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation src/AgentNet.InProcess.Polly/AgentNet.InProcess.Polly.fsproj:31
- No changelog
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-a22ad8cda2714e74aa167197d619503e/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-a22ad8cda2714e74aa167197d619503e/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 . | 3 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/AgentNet.sln package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| 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. semgrep could not parse 2 file(s) — `src/AgentNet.Interop/Executors.cs`, `src/StockAdvisorCS/WorkflowSample.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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-cf4b2ff3e70b4be283f65c49610f3307 | 0 | artifacts/raw/osv-scanner.json |