Public report of StefanBelo/BetfairAiTrading, published 15 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 10:29 UTC · Survey ID cd_0909eb43c34548049ebae848fbcac092

StefanBelo/BetfairAiTrading

Measured 15 November 2026, 10:28 UTC, at code version ae92657

CAI score 56out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 4 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A small codebase: 8,186 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: under 0.1 person-years · Weakest lens: Production Readiness, 18

Findings by how serious they are

17 critical 57 serious 67 minor

10 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 10:28 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

53of 53 dimensions measured by tools.
106of 141 findings point to an exact file and line, so you can open each one in the code. The other 35 concern the repository as a whole, such as missing documentation.
53dimensions across 6 lenses, read from 8,186 lines of product code in 4 projects.
Chapters

Executive summary

StefanBelo/BetfairAiTrading falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no logging, tracing or health checks in the code. It scores 56 out of 100 and is rated Adequate, and all 17 of its critical findings are security problems.

Production Readiness, at 18, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 12 points. Replacing the five deprecated dependencies comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 80.

Fifteen known security holes in the packages the code depends on can be used by attackers. One password or key is open to anyone who can read the repository, and one setting leaves the servers or containers unsafe. Replacing the exposed password or key, updating the vulnerable packages and correcting the unsafe settings would close these risks.

The product code is 8,186 lines, about €10,000 to rebuild.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 18 · counts for 46%Code Health 83 · counts for 25%Maturity 88 · counts for 14%Architecture 98 · counts for 8%Security and Compliance 99 · counts for 4%Performance 100 · counts for 2%

If Production Readiness rose from 18 to 70, the lowest score rated Strong, the score would rise from 56 to about 80.

Code composition: what the lines of code are
Business logic 53%Supporting code 42%Tests 4%
New since the last survey: 3 findings

These 3 critical or serious findings weren't in the previous survey, on 31 October 2026.

  • Code Duplication · Edited copy of a member (44 corresponding lines) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py
  • Code Duplication · Edited copy of a member (75 corresponding lines) src/RacingStatto/FSharp/AnalyzeResults/Models.fs
  • Dependency Vulnerabilities · REDACTED

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 20 findings

These 20 critical or serious findings were in the previous survey, on 31 October 2026, and are gone from this one.

  • Cyclomatic Complexity · analyse_5oct.main (cyclomatic 60) scripts/analyse_5oct.py
  • Cyclomatic Complexity · validate_trading_report.validate (cyclomatic 50) scripts/validate_trading_report.py
  • Cyclomatic Complexity · maintain_docs_metadata.extract_metadata (cyclomatic 47) scripts/maintain_docs_metadata.py
  • Cyclomatic Complexity · parse_strategy_logs.parse (cyclomatic 25) scripts/parse_strategy_logs.py
  • Cyclomatic Complexity · analyse_dutch.main (cyclomatic 21) scripts/analyse_dutch.py
  • Cyclomatic Complexity · maintain_docs_metadata.process_file (cyclomatic 16) scripts/maintain_docs_metadata.py
  • Cyclomatic Complexity · validate_trading_report.parse (cyclomatic 16) scripts/validate_trading_report.py
  • Cognitive Complexity · analyse_5oct.main (cognitive 100) scripts/analyse_5oct.py
  • Cognitive Complexity · validate_trading_report.validate (cognitive 57) scripts/validate_trading_report.py
  • Cognitive Complexity · parse_strategy_logs.parse (cognitive 42) scripts/parse_strategy_logs.py
  • Cognitive Complexity · analyse_dutch.main (cognitive 38) scripts/analyse_dutch.py
  • Cognitive Complexity · maintain_docs_metadata.extract_metadata (cognitive 38) scripts/maintain_docs_metadata.py
  • Cognitive Complexity · validate_trading_report.parse (cognitive 21) scripts/validate_trading_report.py
  • Cognitive Complexity · maintain_docs_metadata.process_file (cognitive 20) scripts/maintain_docs_metadata.py
  • Code Duplication · Duplicated block (25 lines × 2) src/AiAgentPython/agentBet.py
  • Code Duplication · Duplicated block (6 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py
  • Code Coverage · Coverage not measured — .NET suite
  • Secrets (history) · Secret: generic-api-key .vscode/settings.json
  • Secrets (history) · Secret: aws-access-token src/RacingStatto/Data/Parameters.ows
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Rebuild cost: about €10,000 · Estimate
Cost to rebuild€3,400 to €17,000, for 56 to 179 hours of work, under 0.1 person-years for one engineer
Difficulty of the problemStandard, 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.8 at a score of 56. 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.
SizeSmall: 8,186 lines of product code
Comment linesThe estimate prices 8,052 lines. Comment lines count towards the size of 8,186 lines but aren't priced as work.
What it is notNot 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.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 12 points · Low effort · Secret Scanning
2
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5).
Raises the score by about 5 points · Low effort · Dependency Hygiene
3
Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene.
Raises the score by about 4 points · Low effort · Dependency Hygiene

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €10,000 to build again, under 0.1 person-years of work. Its weakest lens is Production Readiness, at 18 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 12 points for low effort, because it clears the 1 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

40 modules, with 20 dependencies between them. Every module uses only modules listed above it, so there are no loops.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 (global)2 AiAgentCSharp3 BeloSoft.AnalyzeResults.App4 BeloSoft.AnalyzeResults.Domain5 BeloSoft.Bfexplorer.HorseRacingStatto.API.Models6 BeloSoft.ExportResultsToCSV.App7 BetfairMarketAnalyzer.Models8 BetfairMarketAnalyzerFSharp.Models9 Microsoft.VisualBasic10 MyStrategyBotTrigger11 MyStrategyBotTrigger.My12 docs.Analysis13 scripts.validate_trading_report14 src.AiAgentPython15 src.BetfairMarketAnalyzerPython.models.analysis_models16 src.BetfairMarketAnalyzerPython.models.betfair_models17 src.MarketDataBrowser.src18 src.MarketDataBrowser.src.components19 src.MarketDataBrowser.src.components.layout20 src.MarketDataBrowser.src.components.layout.MainLayout21 src.MarketDataBrowser.src.components.layout.Sidebar22 src.MarketDataBrowser.src.services23 src.MarketDataBrowser.src.store24 src.MarketDataBrowser.src.store.useStore25 src.MarketDataBrowser.src.types26 src.RacingStatto.Python27 BeloSoft.AnalyzeResults.QuipuAnalyze28 BeloSoft.AnalyzeResults.RulesOperations29 BeloSoft.AnalyzeResults.WinnerRulesOperations30 BeloSoft.ExportResultsToCSV31 BetfairMarketAnalyzer32 BetfairMarketAnalyzer.Services33 BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService34 BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService35 Program36 scripts37 src.BetfairMarketAnalyzerPython38 src.BetfairMarketAnalyzerPython.services.report_generator_service39 src.BetfairMarketAnalyzerPython.services.technical_analysis_service40 src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic
1 (global)
2 AiAgentCSharp
3 BeloSoft.AnalyzeResults.App
4 BeloSoft.AnalyzeResults.Domain
5 BeloSoft.Bfexplorer.HorseRacingStatto.API.Models
6 BeloSoft.ExportResultsToCSV.App
7 BetfairMarketAnalyzer.Models
8 BetfairMarketAnalyzerFSharp.Models
9 Microsoft.VisualBasic
10 MyStrategyBotTrigger
11 MyStrategyBotTrigger.My
12 docs.Analysis
13 scripts.validate_trading_report
14 src.AiAgentPython
15 src.BetfairMarketAnalyzerPython.models.analysis_models
16 src.BetfairMarketAnalyzerPython.models.betfair_models
17 src.MarketDataBrowser.src
18 src.MarketDataBrowser.src.components
19 src.MarketDataBrowser.src.components.layout
20 src.MarketDataBrowser.src.components.layout.MainLayout
21 src.MarketDataBrowser.src.components.layout.Sidebar
22 src.MarketDataBrowser.src.services
23 src.MarketDataBrowser.src.store
24 src.MarketDataBrowser.src.store.useStore
25 src.MarketDataBrowser.src.types
26 src.RacingStatto.Python
27 BeloSoft.AnalyzeResults.QuipuAnalyze42
28 BeloSoft.AnalyzeResults.RulesOperations32
29 BeloSoft.AnalyzeResults.WinnerRulesOperations42
30 BeloSoft.ExportResultsToCSV2
31 BetfairMarketAnalyzer3
32 BetfairMarketAnalyzer.Services11
33 BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService2
34 BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService9
35 Program3
36 scripts1
37 src.BetfairMarketAnalyzerPython1
38 src.BetfairMarketAnalyzerPython.services.report_generator_service11
39 src.BetfairMarketAnalyzerPython.services.technical_analysis_service31
40 src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic31
Uses a module listed above itPart of a loopThe module itself
1 (global)2 AiAgentCSharp3 BeloSoft.AnalyzeResults.App4 BeloSoft.AnalyzeResults.Domain5 BeloSoft.Bfexplorer.HorseRacingStatto.API.Models6 BeloSoft.ExportResultsToCSV.App7 BetfairMarketAnalyzer.Models8 BetfairMarketAnalyzerFSharp.Models9 Microsoft.VisualBasic10 MyStrategyBotTrigger11 MyStrategyBotTrigger.My12 docs.Analysis13 scripts.validate_trading_report14 src.AiAgentPython15 src.BetfairMarketAnalyzerPython.models.analysis_models16 src.BetfairMarketAnalyzerPython.models.betfair_models17 src.MarketDataBrowser.src18 src.MarketDataBrowser.src.components19 src.MarketDataBrowser.src.components.layout20 src.MarketDataBrowser.src.components.layout.MainLayout21 src.MarketDataBrowser.src.components.layout.Sidebar22 src.MarketDataBrowser.src.services23 src.MarketDataBrowser.src.store24 src.MarketDataBrowser.src.store.useStore25 src.MarketDataBrowser.src.types26 src.RacingStatto.Python27 BeloSoft.AnalyzeResults.QuipuAnalyze28 BeloSoft.AnalyzeResults.RulesOperations29 BeloSoft.AnalyzeResults.WinnerRulesOperations30 BeloSoft.ExportResultsToCSV31 BetfairMarketAnalyzer32 BetfairMarketAnalyzer.Services33 BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService34 BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService35 Program36 scripts37 src.BetfairMarketAnalyzerPython38 src.BetfairMarketAnalyzerPython.services.report_generator_service39 src.BetfairMarketAnalyzerPython.services.technical_analysis_service40 src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic(global)1AiAgentCSharp2BeloSoft.AnalyzeResults.App3BeloSoft.AnalyzeResults.Domain4BeloSoft.Bfexplorer.HorseRacingStatto.API.Models5BeloSoft.ExportResultsToCSV.App6BetfairMarketAnalyzer.Models7BetfairMarketAnalyzerFSharp.Models8Microsoft.VisualBasic9MyStrategyBotTrigger10MyStrategyBotTrigger.My11docs.Analysis12scripts.validate_trading_report13src.AiAgentPython14src.BetfairMarketAnalyzerPython.models.analysis_models15src.BetfairMarketAnalyzerPython.models.betfair_models16src.MarketDataBrowser.src17src.MarketDataBrowser.src.components18src.MarketDataBrowser.src.components.layout19src.MarketDataBrowser.src.components.layout.MainLayout20src.MarketDataBrowser.src.components.layout.Sidebar21src.MarketDataBrowser.src.services22src.MarketDataBrowser.src.store23src.MarketDataBrowser.src.store.useStore24src.MarketDataBrowser.src.types25src.RacingStatto.Python26BeloSoft.AnalyzeResults.QuipuAnalyze27BeloSoft.AnalyzeResults.RulesOperations28BeloSoft.AnalyzeResults.WinnerRulesOperations29BeloSoft.ExportResultsToCSV30BetfairMarketAnalyzer31BetfairMarketAnalyzer.Services32BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService33BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService34Program35scripts36src.BetfairMarketAnalyzerPython37src.BetfairMarketAnalyzerPython.services.report_generator_service38src.BetfairMarketAnalyzerPython.services.technical_analysis_service39src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic40423242231129311113131

At a glance — Code Health · 83% · Strong ·

At a glance — Architecture · 98% · Exemplary ·

At a glance — Maturity · 88% · Strong ·

At a glance — Readiness · 18% · Critical · gated by R4, P1, P2, P3 ·

At a glance — Security · 99% · Exemplary ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures20High / Critical
A07:2025 — Authentication Failures1High / Critical
A02:2025 — Security Misconfiguration1High / Critical

Roadmap

Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5); Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene.

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+11.6 ptsLowSecret Scanning
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5).+4.6 ptsLowDependency Hygiene
Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene.+3.7 ptsLowDependency Hygiene
Add a CI workflow that builds and runs the test suite on every push/PR.+3.2 ptsMediumCI/CD gates
Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.+3.2 ptsMediumObservability
Add tests that import the unreached modules (directly or through their public entry).+3.2 ptsMediumTest Coverage
Resolve the 8 redundant comment finding(s) in Comment Value — start with Program.cs (2), TechnicalAnalysisService.cs (2), ChartDisplay.tsx (2).+1.5 ptsLowComment Value
Resolve the 2 BareSuppressMessage finding(s) in Explicit Debt — start with GlobalSuppressions.cs (2).+1.2 ptsLowExplicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 24 files carrying findings, judged against the Production bar: 4% slop · 50% mixed · 46% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
src/MarketDataBrowser/src/components/ChartDisplay.tsx6.6MixedCyclomatic Complexity: ChartDisplay.ChartDisplay (cyclomatic 23)
src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py7.0MixedCyclomatic Complexity: TechnicalAnalysisService._generate_trading_recommendations (cyclomatic 17)
src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs7.2MixedCyclomatic Complexity: TechnicalAnalysisService.calculateTechnicalIndicators (cyclomatic 23)
REDACTED7.2MixedSecret Scanning: Leaked secret: REDACTED
REDACTED7.2MixedIaC & Container Security: High IaC: REDACTED
src/AiAgentCSharp/Program.cs7.3MixedExplicit Debt: CommentedOutCode
src/HelloBetfair/CSharp/MyStrategyBotTrigger/GlobalSuppressions.cs7.3MixedExplicit Debt: BareSuppressMessage
src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs7.4MixedCognitive Complexity: QuipuAnalyze.deriveRuleExpression (cognitive 27)
src/MarketDataBrowser/src/components/TableDisplay.tsx7.8MixedCyclomatic Complexity: TableDisplay.TableDisplay (cyclomatic 18)
src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py7.8MixedCyclomatic Complexity: TechnicalAnalysisServiceBasic._generate_trading_recommendations (cyclomatic 17)
src/RacingStatto/FSharp/AnalyzeResults/Models.fs7.8MixedCode Duplication: Edited copy of a member (75 corresponding lines)
src/MarketDataBrowser/package.json7.8MixedDependency Hygiene: Deprecated: eslint
src/MarketDataBrowser/src/store/useStore.ts8.5Near-cleanCyclomatic Complexity: useStore.transformRacingpostData (cyclomatic 18)
src/BetfairMarketAnalyzerPython/services/report_generator_service.py8.5Near-cleanCognitive Complexity: ReportGeneratorService._generate_technical_analysis (cognitive 18)
src/RacingStatto/FSharp/ExportResultsToCSV/Program.fs8.5Near-cleanCognitive Complexity: App.main (cognitive 17)
src/AiAgentPython/agentBet.py8.5Near-cleanCode Duplication: Duplicated block (44 lines × 2)
src/BetfairMarketAnalyzer/Models/BetfairModels.cs8.5Near-cleanCode Duplication: Duplicated block (17 lines × 2)
src/RacingStatto/FSharp/AnalyzeResults/RulesOperations.fs8.5Near-cleanCode Duplication: Duplicated block (15 lines × 2)
scripts/parse_strategy_logs.py8.5Near-cleanCode Duplication: Duplicated block (6 lines × 2)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 17

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.

Serious — 57

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.

Minor — 67

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 10

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

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

What we checked — 53 dimensions across the health lenses
D1D2D3D4D5D6D7D12D13D14D15D17D19D20D24D26D27D28D29D30D31D34D35D43D44AX10AX3AX4AX5GD1M1M2M3M4P1P10P2P3P4P5P6PF3R1R10R2R3R4R5R6R7R8R9X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 106 of 141 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1dec0-9467-7ac6-a215-4bd007b69b65.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — 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. Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half measured 100.0% (mocha + nyc via `npm install --ignore-scripts` (no lockfile) in docs/.obsidian/plugins/marp-slides/lib3/markdown-it/@kazumatu981/markdown-it-kroki/). This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • 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 SCORED: this repository's production source includes .py, and the python executor ran against the .py half and ran and surfaced no cases to re-run — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (mocha via `npm install --ignore-scripts` (no lockfile) in docs/.obsidian/plugins/marp-slides/lib3/markdown-it/@kazumatu981/markdown-it-kroki/ (133 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
  • 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-contributor repository — bus factor is not applicable (1 contributor(s) across 167 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so 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/RacingStatto/FSharp/AnalyzeResults/AnalyzeResults.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 4 deducted marker(s) and the 0.5/KLoC density on this row were taken over this repository's .NET projects ALONE: .py (2,567 lines, 38% of production source), .fs (1,476 lines, 22% 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • 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.
  • 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.
  • 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.
  • D24 Comment Value — 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. 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.
  • D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 119 sampled here came from .py files. This repository's .fs source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • 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. `docs/.obsidian/plugins/marp-slides/lib3/pdf-lib.min-fe8dcbc2.js`, `src/HelloBetfair/CSharp/MyStrategyBotTrigger/MyStrategyBotTrigger.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.
  • AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • 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.
  • M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
  • M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • 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.
  • 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.
  • 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'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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — 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.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • 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").
  • 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.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • 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.
  • 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".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • 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 Complexity8.9 / 10Strong✓ Tool-verified

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

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

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

6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TechnicalAnalysisService.calculateTechnicalIndicators at 23.

TechnicalAnalysisService.calculateTechnicalIndicators (cyclomatic 23)src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs:41
ChartDisplay.ChartDisplay (cyclomatic 23)src/MarketDataBrowser/src/components/ChartDisplay.tsx:6
useStore.transformRacingpostData (cyclomatic 18)src/MarketDataBrowser/src/store/useStore.ts:17
TableDisplay.TableDisplay (cyclomatic 18)src/MarketDataBrowser/src/components/TableDisplay.tsx:24
TechnicalAnalysisService._generate_trading_recommendations (cyclomatic 17)src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:318

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

What to do

  1. Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TechnicalAnalysisService.calculateTechnicalIndicators (cyclomatic 23), ChartDisplay.ChartDisplay (cyclomatic 23), useStore.transformRacingpostData (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 6 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

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

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

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

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

10 method(s) exceeded the cognitive complexity threshold of 15; the worst was TechnicalAnalysisService.calculateTechnicalIndicators at 44.

TechnicalAnalysisService.calculateTechnicalIndicators (cognitive 44)src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs:41
QuipuAnalyze.deriveRuleExpression (cognitive 27)src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:187
ChartDisplay.ChartDisplay (cognitive 24)src/MarketDataBrowser/src/components/ChartDisplay.tsx:6
TechnicalAnalysisService._generate_trading_recommendations (cognitive 22)src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:318
TechnicalAnalysisServiceBasic._generate_trading_recommendations (cognitive 22)src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:405

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

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with TechnicalAnalysisService.calculateTechnicalIndicators (cognitive 44). — Refactoring it lifts Cognitive Complexity from 6.5 to about 7.5/10.

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

D3 · God Classes9.4 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

1 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: ChartDisplay.ChartDisplaysrc/MarketDataBrowser/src/components/ChartDisplay.tsx:6

What to do

  1. Resolve the 1 FunctionTooLong finding(s) in God Classes — start with ChartDisplay.tsx. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication4.7 / 10Weak✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

15 duplicated block group(s) detected. 13.1 % of the production lines (920 of 6,997) are in a reported copy. A further 3 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 18 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Members sharing a duplicated core (4 members, 50+ identical tokens)src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:153
Edited copy of a member (44 corresponding lines)src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:105
Edited copy of a member (75 corresponding lines)src/RacingStatto/FSharp/AnalyzeResults/Models.fs:1
Duplicated block (85 lines × 2)src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:326
Duplicated block (55 lines × 2)src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:18

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

What to do

  1. Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with technical_analysis_service.py. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Edited copy of a member (44 corresponding lines) finding(s) in Code Duplication — start with technical_analysis_service.py. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Edited copy of a member (75 corresponding lines) finding(s) in Code Duplication — start with Models.fs. — One of this dimension's main actionable groups (1 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

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

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

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

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

0 of 1 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.

Detailed fixes: d7_recommendation.md.

D12 · Dependency Hygiene7.2 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

6 outdated, 0 vulnerable, 0 deprecated, 4 prerelease packages. Those are the NuGet packages; this repository's npm dependencies were read too — 20 outdated of 40 package(s) across 1 lockfile(s).

Prerelease dependency: Azure.AI.Inference · ×4
Deprecated: eslintsrc/MarketDataBrowser/package.json:27
Deprecated: @humanwhocodes/config-array · ×5REDACTED:812
Outdated (npm): ag-grid-community · ×4src/MarketDataBrowser/package.json:18
Outdated (npm): @types/react · ×16

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

What to do

  1. Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
  2. Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).

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

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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

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

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

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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

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

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

0 of 130 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 115 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt9.1 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

4 deducted debt markers + unmeasured dead symbols across 1170 LoC in the .NET projects (0.5/KLoC) → score 9.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .py, .fs (60% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

BareSuppressMessage · ×2src/HelloBetfair/CSharp/MyStrategyBotTrigger/GlobalSuppressions.cs:8
CommentedOutCodesrc/AiAgentCSharp/Program.cs:36
DeadPreprocessorBranchsrc/AiAgentCSharp/Program.cs:24

What to do

  1. Resolve the 2 BareSuppressMessage finding(s) in Explicit Debt — start with GlobalSuppressions.cs (2). — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 DeadPreprocessorBranch finding(s) in Explicit Debt — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

2 of 2 documentation facets pass in full. 445 document(s) read across 6 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D24 · Comment Value0.0 / 10Critical✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

8 of 71 judged comments only repeat the code they sit on (11.3 %).

redundant comment · ×8src/BetfairMarketAnalyzer/Program.cs:24
doc comments repeat the namessrc/AiAgentCSharp/AiAgentHelpers.cs:8

What to do

  1. Resolve the 8 redundant comment finding(s) in Comment Value — start with Program.cs (2), TechnicalAnalysisService.cs (2), ChartDisplay.tsx (2). — One of this dimension's main actionable groups (8 recommendation-level).

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

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

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

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

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

0 of 4 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

66 % of calls cross a namespace and 0 % go through an interface, but 91 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .py source only — this repository's .fs was not sampled for call sites, so this score covers part of the tree, not all of it.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

semgrep found no security issues. semgrep hit a parse error in 9 file(s) — `docs/.obsidian/plugins/marp-slides/lib3/index-57f568fe.js`, `docs/.obsidian/plugins/marp-slides/lib3/marp-cli-9fe562c5.js`, `docs/.obsidian/plugins/marp-slides/lib3/pdf-lib.min-fe8dcbc2.js`, `docs/.obsidian/plugins/marp-slides/lib3/pptxgen.es-7d0ab100.js`, `docs/.obsidian/plugins/obsidian-front-matter-title-plugin/main.js`, … (+4 more) — 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 1 of those file(s) — `src/HelloBetfair/CSharp/MyStrategyBotTrigger/MyStrategyBotTrigger.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.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

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

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

20 finding(s): 0 critical, 15 high, 4 medium, 1 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 15 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-level).
  2. Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D31 · IaC & Container Security9.7 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

  1. Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 15 of the 24 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 platform declaration(s) and 5 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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

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

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

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

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

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

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

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

M1 · Documentation (README)9.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

M2 · Architecture documentation10.0 / 10Exemplary✓ Tool-verified

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

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

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

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy7.1 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • docs/README.md links to `Posts/LLM_Strategy_Reflections_2026.md`, but `docs/Posts/LLM_Strategy_Reflections_2026.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/README.md:61
  • docs/Prompts/README.md links to `Football/Football_PreKick_MarketAnalysis_Prompt.md`, but `docs/Prompts/Football/Football_PreKick_MarketAnalysis_Prompt.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Prompts/README.md:30
  • docs/Research/README.md links to `AdvancedBetfairHorseRacing/HorseRacingMarketAnalysisPrompt.md`, but `docs/Research/AdvancedBetfairHorseRacing/HorseRacingMarketAnalysisPrompt.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:15
  • docs/Research/README.md links to `General/Back-Lay-Strategy-PriceHistory.md`, but `docs/Research/General/Back-Lay-Strategy-PriceHistory.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:17
  • docs/Research/README.md links to `General/Back-Lay-Strategy-PriceHistory-Correlation.md`, but `docs/Research/General/Back-Lay-Strategy-PriceHistory-Correlation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:18
  • docs/Research/README.md links to `General/Back-Lay-Strategy-CandleStick-AllSelections.md`, but `docs/Research/General/Back-Lay-Strategy-CandleStick-AllSelections.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:19
  • docs/Research/README.md links to `General/Back-Lay-Strategy-CandleStick-AllSelections_V1.md`, but `docs/Research/General/Back-Lay-Strategy-CandleStick-AllSelections_V1.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:20
  • docs/Research/README.md links to `General/Back-Lay-Strategy-CandleStick-Correlation.md`, but `docs/Research/General/Back-Lay-Strategy-CandleStick-Correlation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:21
  • docs/Research/README.md links to `General/Back-Lay-Strategy-CandleStick-Top3.md`, but `docs/Research/General/Back-Lay-Strategy-CandleStick-Top3.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:22
  • docs/Research/README.md links to `General/BetfairSP.md`, but `docs/Research/General/BetfairSP.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:23
  • docs/Research/README.md links to `General/CLIToolsForAICoding.md`, but `docs/Research/General/CLIToolsForAICoding.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:24
  • docs/Research/README.md links to `HorseRacing.md`, but `docs/Research/HorseRacing.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:26
  • docs/Research/README.md links to `General/Prompts.md`, but `docs/Research/General/Prompts.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:36
  • docs/Research/README.md links to `General/3-Tick-Back-Lay-Strategy.md`, but `docs/Research/General/3-Tick-Back-Lay-Strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:37
  • docs/Research/README.md links to `General/3-Tick-General/Back-Lay-Strategy-TradedPrices.md`, but `docs/Research/General/3-Tick-General/Back-Lay-Strategy-TradedPrices.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Research/README.md:38
  • src/AiAgentCSharp/README.md names .NET 9, but the projects target .NET 8, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/AiAgentCSharp/README.md:159

What to do

  • Reconcile the README with reality: docs/README.md links to `Posts/LLM_Strategy_Reflections_2026.md`, but `docs/Posts/LLM_Strategy_Reflections_2026.md` does not exist; docs/Prompts/README.md links to `Football/Football_PreKick_MarketAnalysis_Prompt.md`, but `docs/Prompts/Football/Football_PreKick_MarketAnalysis_Prompt.md` does not exist; docs/Research/README.md links to `AdvancedBetfairHorseRacing/HorseRacingMarketAnalysisPrompt.md`, but `docs/Research/AdvancedBetfairHorseRacing/HorseRacingMarketAnalysisPrompt.md` does not exist; docs/Research/README.md links to `General/Back-Lay-Strategy-PriceHistory.md`, but `docs/Research/General/Back-Lay-Strategy-PriceHistory.md` does not exist; docs/Research/README.md links to `General/Back-Lay-Strategy-PriceHistory-Correlation.md`, but `docs/Research/General/Back-Lay-Strategy-PriceHistory-Correlation.md` does not exist.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

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

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability0.0 / 10Critical✓ Tool-verified

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

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

  • No logging call was found in the 43 Python, F#, JavaScript/TypeScript production file(s) this check read across 7 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; F#: Microsoft.Extensions.Logging (ILogger), Serilog, NLog, log4net, Logary) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

  • Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.
  • Add a health-check endpoint (a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack — 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.
  • `src/AiAgentCSharp/AiAgentCSharp.csproj` 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/AiAgentCSharp/AiAgentCSharp.csproj:18

What to do

  • Run what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — 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.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

  • The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

R10 · Code Duplication8.0 / 10Strong✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • src/MarketDataBrowser/src/components/ChartDisplay.tsx:164 · src/MarketDataBrowser/src/components/TableDisplay.tsx:73 — the two spans are one implementation copied and then locally edited — 116 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/MarketDataBrowser/src/components/ChartDisplay.tsx:164

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • (anonymous) has cyclomatic complexity 16 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/MarketDataBrowser/src/store/useStore.ts:18
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

R4 · Test Coverage0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 0% of 12 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness9.3 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling6.6 / 10Adequate✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add a test runner (vitest / jest / playwright) as package.json scripts and run them in CI.
R7 · Dead Code8.4 / 10Strong✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 2 application, 2 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (2 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — src/MarketDataBrowser/src/components/layout/Topbar.tsx
  • Nothing imports this binding — it is safe to review for removal. — src/MarketDataBrowser/src/types/index.ts:31

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

X5 · Nullable reference types10.0 / 10Exemplary○ Nothing flagged

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

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

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health83%StrongSolid.
Architecture98%ExemplarySolid.
Maturity88%StrongSolid.
Readiness18%Critical — gated by R4, P1, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security99%ExemplarySolid.
Performance100%ExemplaryStrongest area.
Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 73 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No 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 — no public interfaces
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • 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 — ~62 lines of test source are present (.py) 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 scored — polyglot repository, one half's runner produced no measurement
  • D16 Bus Factor — single-contributor 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, .py, .ts, .tsx, 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 — Naming consistency does not read Visual Basic, html yet; not measured.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (6,997 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 — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • D8 Code Coverage — Coverage not measured — .NET suite
  • DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 33 value object(s); a Domain/Aggregates/ValueObjects layer
  • 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 — IC1 reached only 18% of this repository's production lines — python (2,842 lines), fsharp (1,476 lines), javascript (1,189 lines), typescript (1,179 lines), vbnet (39 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • P12 CI test-gate honesty — no CI workflow found
  • 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 — 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.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X12 Unreachable branch — X12 reached only 18% of this repository's production lines — python (2,842 lines), fsharp (1,476 lines), javascript (1,189 lines), typescript (1,179 lines), vbnet (39 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 18% of this repository's production lines — python (2,842 lines), fsharp (1,476 lines), javascript (1,189 lines), typescript (1,179 lines), vbnet (39 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — no async method does work a token could cancel
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 18% of this repository's production lines — python (2,842 lines), fsharp (1,476 lines), javascript (1,189 lines), typescript (1,179 lines), vbnet (39 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 — X29 reached only 18% of this repository's production lines — python (2,842 lines), fsharp (1,476 lines), javascript (1,189 lines), typescript (1,179 lines), vbnet (39 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X3 Exception handling — X3 reached only 18% of this repository's production lines — python (2,842 lines), fsharp (1,476 lines), javascript (1,189 lines), typescript (1,179 lines), vbnet (39 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.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 17 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
Serious — 57 finding(s)
D12 · Dependency Hygiene · Prerelease dependency · ×4
  • Prerelease dependency: Azure.AI.Inference — Azure.AI.Inference resolves to 1.0.0-beta.5, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: Azure.AI.OpenAI — Azure.AI.OpenAI resolves to 2.8.0-beta.1, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: Microsoft.Extensions.AI.AzureAIInference — Microsoft.Extensions.AI.AzureAIInference resolves to 10.0.0-preview.1.25559.3, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: Quipu — Quipu resolves to 1.1.0-beta1, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
D30 · Dependency Vulnerabilities · Medium CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · BareSuppressMessage · ×2
  • BareSuppressMessage src/HelloBetfair/CSharp/MyStrategyBotTrigger/GlobalSuppressions.cs:8 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage src/HelloBetfair/CSharp/MyStrategyBotTrigger/GlobalSuppressions.cs:9 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
D1 · Cyclomatic Complexity · TechnicalAnalysisService.calculateTechnicalIndicators (cyclomatic 23) · ×1
  • TechnicalAnalysisService.calculateTechnicalIndicators (cyclomatic 23) src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs:41 — TechnicalAnalysisService.calculateTechnicalIndicators has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ChartDisplay.ChartDisplay (cyclomatic 23) · ×1
  • ChartDisplay.ChartDisplay (cyclomatic 23) src/MarketDataBrowser/src/components/ChartDisplay.tsx:6 — ChartDisplay.ChartDisplay has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 11, 37, 49, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · useStore.transformRacingpostData (cyclomatic 18) · ×1
  • useStore.transformRacingpostData (cyclomatic 18) src/MarketDataBrowser/src/store/useStore.ts:17 — useStore.transformRacingpostData has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 18). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · TableDisplay.TableDisplay (cyclomatic 18) · ×1
  • TableDisplay.TableDisplay (cyclomatic 18) src/MarketDataBrowser/src/components/TableDisplay.tsx:24 — TableDisplay.TableDisplay has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 34, 27, 59). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · TechnicalAnalysisService._generate_trading_recommendations (cyclomatic 17) · ×1
  • TechnicalAnalysisService._generate_trading_recommendations (cyclomatic 17) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:318 — TechnicalAnalysisService._generate_trading_recommendations has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TechnicalAnalysisServiceBasic._generate_trading_recommendations (cyclomatic 17) · ×1
  • TechnicalAnalysisServiceBasic._generate_trading_recommendations (cyclomatic 17) src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:405 — TechnicalAnalysisServiceBasic._generate_trading_recommendations has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: eslint src/MarketDataBrowser/package.json:27 — eslint 8.57.1, declared in src/MarketDataBrowser/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
D17 · Explicit Debt · CommentedOutCode · ×1
  • CommentedOutCode src/AiAgentCSharp/Program.cs:36 — 10 consecutive commented-code lines
D17 · Explicit Debt · DeadPreprocessorBranch · ×1
  • DeadPreprocessorBranch src/AiAgentCSharp/Program.cs:24 — #if UseShowTools — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
D2 · Cognitive Complexity · TechnicalAnalysisService.calculateTechnicalIndicators (cognitive 44) · ×1
  • TechnicalAnalysisService.calculateTechnicalIndicators (cognitive 44) src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs:41 — TechnicalAnalysisService.calculateTechnicalIndicators has cognitive complexity 44 (threshold 15). Drivers by points: if/else 22 (32 pts), boolean chains 10, error handling 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs holds 3 of the 10 methods over the threshold — including the worst — and 39 of the 80 points over it (49%), 3.3× the next-largest file (src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs at 12). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · QuipuAnalyze.deriveRuleExpression (cognitive 27) · ×1
  • QuipuAnalyze.deriveRuleExpression (cognitive 27) src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:187 — QuipuAnalyze.deriveRuleExpression has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 2 (4 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · ChartDisplay.ChartDisplay (cognitive 24) · ×1
  • ChartDisplay.ChartDisplay (cognitive 24) src/MarketDataBrowser/src/components/ChartDisplay.tsx:6 — ChartDisplay.ChartDisplay has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 8, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 11, 49, 37, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · TechnicalAnalysisService._generate_trading_recommendations (cognitive 22) · ×1
  • TechnicalAnalysisService._generate_trading_recommendations (cognitive 22) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:318 — TechnicalAnalysisService._generate_trading_recommendations has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 5, if/else 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TechnicalAnalysisServiceBasic._generate_trading_recommendations (cognitive 22) · ×1
  • TechnicalAnalysisServiceBasic._generate_trading_recommendations (cognitive 22) src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:405 — TechnicalAnalysisServiceBasic._generate_trading_recommendations has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 5, if/else 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TechnicalAnalysisService.analyzeMarketFlow (cognitive 22) · ×1
  • TechnicalAnalysisService.analyzeMarketFlow (cognitive 22) src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs:167 — TechnicalAnalysisService.analyzeMarketFlow has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (20 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs holds 3 of the 10 methods over the threshold — including the worst — and 39 of the 80 points over it (49%), 3.3× the next-largest file (src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs at 12). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · ReportGeneratorService._generate_technical_analysis (cognitive 18) · ×1
  • ReportGeneratorService._generate_technical_analysis (cognitive 18) src/BetfairMarketAnalyzerPython/services/report_generator_service.py:97 — ReportGeneratorService._generate_technical_analysis has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10 (15 pts), if/else 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TechnicalAnalysisService.generateTradingRecommendations (cognitive 18) · ×1
  • TechnicalAnalysisService.generateTradingRecommendations (cognitive 18) src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs:236 — TechnicalAnalysisService.generateTradingRecommendations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, match/switch 2 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs holds 3 of the 10 methods over the threshold — including the worst — and 39 of the 80 points over it (49%), 3.3× the next-largest file (src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs at 12). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · App.main (cognitive 17) · ×1
  • App.main (cognitive 17) src/RacingStatto/FSharp/ExportResultsToCSV/Program.fs:89 — App.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 1 (3 pts), loops 1 (3 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TableDisplay.TableDisplay (cognitive 16) · ×1
  • TableDisplay.TableDisplay (cognitive 16) src/MarketDataBrowser/src/components/TableDisplay.tsx:24 — TableDisplay.TableDisplay has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, ternaries 5 (6 pts), if/else 4 (nesting depth added 1). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 34, 27, 59). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D3 · God Classes · FunctionTooLong · ×1
  • FunctionTooLong: ChartDisplay.ChartDisplay src/MarketDataBrowser/src/components/ChartDisplay.tsx:6 — FunctionTooLong — ChartDisplay runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:153 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:153-167 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:170-184 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:240-254 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:257-271 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:105 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:105-150 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:194-237 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (75 corresponding lines) · ×1
  • Edited copy of a member (75 corresponding lines) src/RacingStatto/FSharp/AnalyzeResults/Models.fs:1 — src/RacingStatto/FSharp/AnalyzeResults/Models.fs:1-85 | src/RacingStatto/FSharp/ExportResultsToCSV/Models.fs:1-75 — These two members are one piece of code written twice and then edited apart: 75 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (85 lines × 2) · ×1
  • Duplicated block (85 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:326 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:326-410 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:413-497 — before extracting anything, compare `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py` and `src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 327 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (55 lines × 2) · ×1
  • Duplicated block (55 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:18 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:18-72 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:21-75 — before extracting anything, compare `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py` and `src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 327 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (54 lines × 2) · ×1
  • Duplicated block (54 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:263 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:263-316 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:350-403 — before extracting anything, compare `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py` and `src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 327 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (46 lines × 2) · ×1
  • Duplicated block (46 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:187 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:187-232 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:274-319 — before extracting anything, compare `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py` and `src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 327 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:75 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:75-102 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:78-105 — before extracting anything, compare `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py` and `src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 327 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:235 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:235-260 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:322-347 — before extracting anything, compare `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py` and `src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 327 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (44 lines × 2) · ×1
  • Duplicated block (44 lines × 2) src/AiAgentPython/agentBet.py:18 — src/AiAgentPython/agentBet.py:18-61 | src/AiAgentPython/agentBetPriceData.py:18-61 — before extracting anything, compare `src/AiAgentPython/agentBet.py` and `src/AiAgentPython/agentBetPriceData.py` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/AiAgentPython/agentBet.py:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) src/BetfairMarketAnalyzer/Models/BetfairModels.cs:7 — src/BetfairMarketAnalyzer/Models/BetfairModels.cs:7-23 | src/BetfairMarketAnalyzer/Models/BetfairModels.cs:79-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:153 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:153-167 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:170-184 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:240-254 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:257-271 — before extracting anything, compare `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py` and `src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 327 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:133 — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:133-150 | src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:220-237 — before extracting anything, compare `src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py` and `src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 327 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (56 lines × 2) · ×1
  • Duplicated block (56 lines × 2) src/RacingStatto/FSharp/AnalyzeResults/Models.fs:1 — src/RacingStatto/FSharp/AnalyzeResults/Models.fs:1-56 | src/RacingStatto/FSharp/ExportResultsToCSV/Models.fs:1-56 — `src/RacingStatto/FSharp/AnalyzeResults/Models.fs` and `src/RacingStatto/FSharp/ExportResultsToCSV/Models.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 56 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) src/RacingStatto/FSharp/AnalyzeResults/RulesOperations.fs:9 — src/RacingStatto/FSharp/AnalyzeResults/RulesOperations.fs:9-23 | src/RacingStatto/FSharp/AnalyzeResults/WinnerRulesOperations.fs:39-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×1
  • Duplicated block (11–12 lines × 3) src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:170 — src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:170-180 | src/RacingStatto/FSharp/AnalyzeResults/RulesOperations.fs:11-22 | src/RacingStatto/FSharp/AnalyzeResults/WinnerRulesOperations.fs:41-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:108 — src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:108-118 | src/RacingStatto/FSharp/AnalyzeResults/RulesOperations.fs:59-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) scripts/parse_strategy_logs.py:72 — scripts/parse_strategy_logs.py:72-77 | scripts/validate_trading_report.py:111-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 43 Python, F#, JavaScript/TypeScript production file(s) this check read across 7 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; F#: Microsoft.Extensions.Logging (ILogger), Serilog, NLog, log4net, Logary) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
R10 · Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (24 matched lines × 2 locations) src/MarketDataBrowser/src/components/ChartDisplay.tsx:164 — src/MarketDataBrowser/src/components/ChartDisplay.tsx:164 · src/MarketDataBrowser/src/components/TableDisplay.tsx:73 — the two spans are one implementation copied and then locally edited — 116 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 16, cognitive 13) src/MarketDataBrowser/src/store/useStore.ts:18 — (anonymous) has cyclomatic complexity 16 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R4 · Test Coverage · Test Coverage · ×1
  • Test Coverage — 0% of 12 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
R6 · Tooling · No test script · ×1
  • No test script — test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~101 LoC) · ×1
  • Dead file (~101 LoC) src/MarketDataBrowser/src/components/layout/Topbar.tsx — no import path from any entry point (2 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×1
  • JavaScript dependencies are not locked docs/.obsidian/plugins/marp-slides/lib3/markdown-it/@kazumatu981/markdown-it-kroki/package.json:28 — docs/.obsidian/plugins/marp-slides/lib3/markdown-it/@kazumatu981/markdown-it-kroki/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Minor — 44 finding(s)
M4 · Documentation accuracy · README/code drift · ×16
  • README/code drift docs/README.md:61 — docs/README.md links to `Posts/LLM_Strategy_Reflections_2026.md`, but `docs/Posts/LLM_Strategy_Reflections_2026.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Prompts/README.md:30 — docs/Prompts/README.md links to `Football/Football_PreKick_MarketAnalysis_Prompt.md`, but `docs/Prompts/Football/Football_PreKick_MarketAnalysis_Prompt.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:15 — docs/Research/README.md links to `AdvancedBetfairHorseRacing/HorseRacingMarketAnalysisPrompt.md`, but `docs/Research/AdvancedBetfairHorseRacing/HorseRacingMarketAnalysisPrompt.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:17 — docs/Research/README.md links to `General/Back-Lay-Strategy-PriceHistory.md`, but `docs/Research/General/Back-Lay-Strategy-PriceHistory.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:18 — docs/Research/README.md links to `General/Back-Lay-Strategy-PriceHistory-Correlation.md`, but `docs/Research/General/Back-Lay-Strategy-PriceHistory-Correlation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:19 — docs/Research/README.md links to `General/Back-Lay-Strategy-CandleStick-AllSelections.md`, but `docs/Research/General/Back-Lay-Strategy-CandleStick-AllSelections.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:20 — docs/Research/README.md links to `General/Back-Lay-Strategy-CandleStick-AllSelections_V1.md`, but `docs/Research/General/Back-Lay-Strategy-CandleStick-AllSelections_V1.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:21 — docs/Research/README.md links to `General/Back-Lay-Strategy-CandleStick-Correlation.md`, but `docs/Research/General/Back-Lay-Strategy-CandleStick-Correlation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:22 — docs/Research/README.md links to `General/Back-Lay-Strategy-CandleStick-Top3.md`, but `docs/Research/General/Back-Lay-Strategy-CandleStick-Top3.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:23 — docs/Research/README.md links to `General/BetfairSP.md`, but `docs/Research/General/BetfairSP.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:24 — docs/Research/README.md links to `General/CLIToolsForAICoding.md`, but `docs/Research/General/CLIToolsForAICoding.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:26 — docs/Research/README.md links to `HorseRacing.md`, but `docs/Research/HorseRacing.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:36 — docs/Research/README.md links to `General/Prompts.md`, but `docs/Research/General/Prompts.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:37 — docs/Research/README.md links to `General/3-Tick-Back-Lay-Strategy.md`, but `docs/Research/General/3-Tick-Back-Lay-Strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/Research/README.md:38 — docs/Research/README.md links to `General/3-Tick-General/Back-Lay-Strategy-TradedPrices.md`, but `docs/Research/General/3-Tick-General/Back-Lay-Strategy-TradedPrices.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift src/AiAgentCSharp/README.md:159 — src/AiAgentCSharp/README.md names .NET 9, but the projects target .NET 8, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D24 · Comment Value · redundant comment · ×8
  • redundant comment src/BetfairMarketAnalyzer/Program.cs:24 — "Perform technical analysis" repeats the code it sits on: 3 of its 3 words (perform, technical, analysis) are already in `Console.WriteLine("Performing technical analysis...");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/BetfairMarketAnalyzer/Program.cs:78 — "Generate realistic price history data" repeats the code it sits on: 4 of its 5 words (generate, realistic, price, history) are already in `var priceHistory = GenerateRealisticPriceHistory();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/BetfairMarketAnalyzer/Services/ReportGeneratorService.cs:27 — "Support/Resistance Analysis" repeats the code it sits on: 3 of its 3 words (support, resistance, analysis) are already in `GenerateSupportResistanceAnalysis(report, analysis);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/BetfairMarketAnalyzer/Services/TechnicalAnalysisService.cs:22 — "Calculate technical indicators" repeats the code it sits on: 3 of its 3 words (calculate, technical, indicators) are already in `var indicators = CalculateTechnicalIndicators(quotes);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/BetfairMarketAnalyzer/Services/TechnicalAnalysisService.cs:34 — "Generate trading recommendations" repeats the code it sits on: 3 of its 3 words (generate, trading, recommendations) are already in `var recommendations = GenerateTradingRecommendations(priceData, indicators, supportResistance, marketFlow);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/MarketDataBrowser/src/components/ChartDisplay.tsx:103 — "Add price line series" repeats the code it sits on: 4 of its 4 words (add, price, line, series) are already in `const lineSeries = chart.addLineSeries({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/MarketDataBrowser/src/components/ChartDisplay.tsx:113 — "Add volume histogram series" repeats the code it sits on: 4 of its 4 words (add, volume, histogram, series) are already in `const volumeSeries = chart.addHistogramSeries({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/MarketDataBrowser/src/types/index.ts:20 — "Data Context types" repeats the code it sits on: 3 of its 3 words (data, context, types) are already in `export type DataContextType = 'table' | 'chart';`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D12 · Dependency Hygiene · Deprecated · ×5
  • Deprecated: @humanwhocodes/config-array REDACTED:812 — @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @humanwhocodes/object-schema REDACTED:866 — @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:2552 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: inflight REDACTED:2753 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: rimraf REDACTED:3367 — rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D12 · Dependency Hygiene · Outdated (npm) · ×4
  • Outdated (npm): ag-grid-community src/MarketDataBrowser/package.json:18 — ag-grid-community 31.3.4 → 36.3.0 available.
  • Outdated (npm): ag-grid-react src/MarketDataBrowser/package.json:17 — ag-grid-react 31.3.4 → 36.3.0 available.
  • Outdated (npm): js-tokens — js-tokens 4.0.0 → 10.0.0 available.
  • Outdated (npm): react-is — react-is 16.13.1 → 19.3.1 available.
X10 · Duplicated predicate · Duplicated predicate · ×4
  • Duplicated predicate src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:355 — `indicators.rsi is None or indicators.rsi < 70` appears character-identically in 2 files — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py, src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:392 — `len(recent_trend) > 5 and indicators.volume_moving_average > 10` appears character-identically in 2 files — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py, src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:335 — `market_flow.dominant_direction == "Backing" and price_direction < 0` appears character-identically in 2 files — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py, src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:372 — `market_flow.dominant_direction == "Laying" and price_direction > 0` appears character-identically in 2 files — src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py, src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack — 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation src/AiAgentCSharp/AiAgentCSharp.csproj:18 — `src/AiAgentCSharp/AiAgentCSharp.csproj` 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`.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R7 · Dead Code · Unused export 'ApiResponse' · ×1
  • Unused export 'ApiResponse' src/MarketDataBrowser/src/types/index.ts:31 — Nothing imports this binding — it is safe to review for removal.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch src/BetfairMarketAnalyzer/Services/TechnicalAnalysisService.cs:125 — `CalculateTechnicalIndicators` swallows every exception into `return new TechnicalIndicators();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
X7 · Silent fallback defaults · Pending state with no failure state · ×1
  • Pending state with no failure state src/MarketDataBrowser/src/components/ChartDisplay.tsx:168 — The view draws `Loading... Loading chart data...` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Minor — 23 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×16
  • Outdated (npm): @types/react — @types/react 18.3.27 → 19.3.0 available.
  • Outdated (npm): asynckit — asynckit 0.4.0 → 0.5.0 available.
  • Outdated (npm): axios — axios 1.13.2 → 1.21.1 available.
  • Outdated (npm): es-object-atoms — es-object-atoms 1.1.1 → 1.1.2 available.
  • Outdated (npm): follow-redirects — follow-redirects 1.15.11 → 1.16.3 available.
  • Outdated (npm): form-data — form-data 4.0.5 → 4.0.6 available.
  • Outdated (npm): hasown — hasown 2.0.2 → 2.0.4 available.
  • Outdated (npm): lightweight-charts — lightweight-charts 4.2.3 → 5.3.0 available.
  • Outdated (npm): mime-db — mime-db 1.52.0 → 1.54.0 available.
  • Outdated (npm): mime-types — mime-types 2.1.35 → 3.0.2 available.
  • Outdated (npm): proxy-from-env — proxy-from-env 1.1.0 → 2.1.0 available.
  • Outdated (npm): react — react 18.3.1 → 19.3.1 available.
  • Outdated (npm): react-dom — react-dom 18.3.1 → 19.3.1 available.
  • Outdated (npm): scheduler — scheduler 0.23.2 → 0.28.0 available.
  • Outdated (npm): use-sync-external-store — use-sync-external-store 1.6.0 → 1.7.0 available.
  • Outdated (npm): zustand — zustand 4.5.7 → 5.1.0 available.
D12 · Dependency Hygiene · Outdated · ×6
  • Outdated: Microsoft.Extensions.AI — Microsoft.Extensions.AI 10.5.0 → 11.0.0 available (referenced by AiAgentCSharp).
  • Outdated: Microsoft.Extensions.AI.OpenAI — Microsoft.Extensions.AI.OpenAI 10.5.0 → 11.0.0 available (referenced by AiAgentCSharp).
  • Outdated: Microsoft.Extensions.Configuration.UserSecrets — Microsoft.Extensions.Configuration.UserSecrets 10.0.6 → 11.0.0 available (referenced by AiAgentCSharp).
  • Outdated: ModelContextProtocol.Core — ModelContextProtocol.Core 1.2.0 → 2.4.0 available (referenced by AiAgentCSharp).
  • Outdated: FSharp.Core — FSharp.Core 10.1.400 → 11.0.101 available (referenced by AnalyzeResults).
  • Outdated: CsvHelper — CsvHelper 33.1.0 → 34.0.0 available (referenced by ExportResultsToCSV).
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names src/AiAgentCSharp/AiAgentHelpers.cs:8 — 0 of 8 documented parameters and 13 of 13 summaries in `AiAgentCSharp` only repeat the member or parameter name (e.g. "AiAgentHelpers" for `AiAgentHelpers`). 8 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-336d5b3c798b45d2a88af8b9c787588d/history.json --exit-code 0 --source .4artifacts/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-336d5b3c798b45d2a88af8b9c787588d/tree.json --exit-code 0 --source .1artifacts/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 .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list BetfairAiTrading.slnx package --vulnerable --include-transitive --format json20artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .1artifacts/raw/trivy-config.json
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) — `docs/.obsidian/plugins/marp-slides/lib3/pdf-lib.min-fe8dcbc2.js`, `src/HelloBetfair/CSharp/MyStrategyBotTrigger/MyStrategyBotTrigger.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D36 · Supply-chain Provenance & Signingprovenance—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 Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1dec0-9467-7ac6-a215-4bd007b69b65 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md