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.
If Production Readiness rose from 18 to 70, the lowest score rated Strong, the score would rise from 56 to about 80.
New since the last survey: 3 findings
- 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
Fixed since the last survey: 20 findings
- 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 problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.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. |
| Size | Small: 8,186 lines of product code |
| Comment lines | The estimate prices 8,052 lines. Comment lines count towards the size of 8,186 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 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.QuipuAnalyze | 28 BeloSoft.AnalyzeResults.RulesOperations | 29 BeloSoft.AnalyzeResults.WinnerRulesOperations | 30 BeloSoft.ExportResultsToCSV | 31 BetfairMarketAnalyzer | 32 BetfairMarketAnalyzer.Services | 33 BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService | 34 BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService | 35 Program | 36 scripts | 37 src.BetfairMarketAnalyzerPython | 38 src.BetfairMarketAnalyzerPython.services.report_generator_service | 39 src.BetfairMarketAnalyzerPython.services.technical_analysis_service | 40 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.QuipuAnalyze | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 BeloSoft.AnalyzeResults.RulesOperations | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 BeloSoft.AnalyzeResults.WinnerRulesOperations | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 BeloSoft.ExportResultsToCSV | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 BetfairMarketAnalyzer | 3 | |||||||||||||||||||||||||||||||||||||||
| 32 BetfairMarketAnalyzer.Services | 11 | |||||||||||||||||||||||||||||||||||||||
| 33 BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService | 9 | |||||||||||||||||||||||||||||||||||||||
| 35 Program | 3 | |||||||||||||||||||||||||||||||||||||||
| 36 scripts | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 src.BetfairMarketAnalyzerPython | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 src.BetfairMarketAnalyzerPython.services.report_generator_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 src.BetfairMarketAnalyzerPython.services.technical_analysis_service | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic | 3 | 1 |
27→4 BeloSoft.AnalyzeResults.QuipuAnalyze uses BeloSoft.AnalyzeResults.Domain✕
- Connections
- 4 pairs of types, where a type in BeloSoft.AnalyzeResults.QuipuAnalyze uses a type in BeloSoft.AnalyzeResults.Domain.
- The types involved
BeloSoft.AnalyzeResults.QuipuAnalyze.QuipuAnalyze→BeloSoft.AnalyzeResults.Domain.BettingStrategyBeloSoft.AnalyzeResults.QuipuAnalyze.QuipuAnalyze→BeloSoft.AnalyzeResults.Domain.FeatureBeloSoft.AnalyzeResults.QuipuAnalyze.QuipuAnalyze→BeloSoft.AnalyzeResults.Domain.FeatureStatsBeloSoft.AnalyzeResults.QuipuAnalyze.QuipuAnalyze→BeloSoft.AnalyzeResults.Domain.StrategyResult
- Direction
- BeloSoft.AnalyzeResults.QuipuAnalyze uses BeloSoft.AnalyzeResults.Domain, so a change to BeloSoft.AnalyzeResults.Domain can break BeloSoft.AnalyzeResults.QuipuAnalyze, while a change to BeloSoft.AnalyzeResults.QuipuAnalyze can't break BeloSoft.AnalyzeResults.Domain.
- Position
- Below the diagonal: BeloSoft.AnalyzeResults.QuipuAnalyze uses a module listed above it, which is the healthy direction.
27→5 BeloSoft.AnalyzeResults.QuipuAnalyze uses BeloSoft.Bfexplorer.HorseRacingStatto.API.Models✕
- Connections
- 2 pairs of types, where a type in BeloSoft.AnalyzeResults.QuipuAnalyze uses a type in BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.
- The types involved
BeloSoft.AnalyzeResults.QuipuAnalyze.QuipuAnalyze→BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.RaceResultDataBeloSoft.AnalyzeResults.QuipuAnalyze.QuipuAnalyze→BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.RaceRunnerData
- Direction
- BeloSoft.AnalyzeResults.QuipuAnalyze uses BeloSoft.Bfexplorer.HorseRacingStatto.API.Models, so a change to BeloSoft.Bfexplorer.HorseRacingStatto.API.Models can break BeloSoft.AnalyzeResults.QuipuAnalyze, while a change to BeloSoft.AnalyzeResults.QuipuAnalyze can't break BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.
- Position
- Below the diagonal: BeloSoft.AnalyzeResults.QuipuAnalyze uses a module listed above it, which is the healthy direction.
28→4 BeloSoft.AnalyzeResults.RulesOperations uses BeloSoft.AnalyzeResults.Domain✕
- Connections
- 3 pairs of types, where a type in BeloSoft.AnalyzeResults.RulesOperations uses a type in BeloSoft.AnalyzeResults.Domain.
- The types involved
BeloSoft.AnalyzeResults.RulesOperations.RulesOperations→BeloSoft.AnalyzeResults.Domain.FeatureBeloSoft.AnalyzeResults.RulesOperations.RulesOperations→BeloSoft.AnalyzeResults.Domain.RuleBeloSoft.AnalyzeResults.RulesOperations.RulesOperations→BeloSoft.AnalyzeResults.Domain.StrategyResult
- Direction
- BeloSoft.AnalyzeResults.RulesOperations uses BeloSoft.AnalyzeResults.Domain, so a change to BeloSoft.AnalyzeResults.Domain can break BeloSoft.AnalyzeResults.RulesOperations, while a change to BeloSoft.AnalyzeResults.RulesOperations can't break BeloSoft.AnalyzeResults.Domain.
- Position
- Below the diagonal: BeloSoft.AnalyzeResults.RulesOperations uses a module listed above it, which is the healthy direction.
28→5 BeloSoft.AnalyzeResults.RulesOperations uses BeloSoft.Bfexplorer.HorseRacingStatto.API.Models✕
- Connections
- 2 pairs of types, where a type in BeloSoft.AnalyzeResults.RulesOperations uses a type in BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.
- The types involved
BeloSoft.AnalyzeResults.RulesOperations.RulesOperations→BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.RaceResultDataBeloSoft.AnalyzeResults.RulesOperations.RulesOperations→BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.RaceRunnerData
- Direction
- BeloSoft.AnalyzeResults.RulesOperations uses BeloSoft.Bfexplorer.HorseRacingStatto.API.Models, so a change to BeloSoft.Bfexplorer.HorseRacingStatto.API.Models can break BeloSoft.AnalyzeResults.RulesOperations, while a change to BeloSoft.AnalyzeResults.RulesOperations can't break BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.
- Position
- Below the diagonal: BeloSoft.AnalyzeResults.RulesOperations uses a module listed above it, which is the healthy direction.
29→4 BeloSoft.AnalyzeResults.WinnerRulesOperations uses BeloSoft.AnalyzeResults.Domain✕
- Connections
- 4 pairs of types, where a type in BeloSoft.AnalyzeResults.WinnerRulesOperations uses a type in BeloSoft.AnalyzeResults.Domain.
- The types involved
BeloSoft.AnalyzeResults.WinnerRulesOperations.WinnerRulesOperations→BeloSoft.AnalyzeResults.Domain.FeatureBeloSoft.AnalyzeResults.WinnerRulesOperations.WinnerRulesOperations→BeloSoft.AnalyzeResults.Domain.RuleBeloSoft.AnalyzeResults.WinnerRulesOperations.WinnerRulesOperations→BeloSoft.AnalyzeResults.Domain.SearchConfigBeloSoft.AnalyzeResults.WinnerRulesOperations.WinnerRulesOperations→BeloSoft.AnalyzeResults.Domain.StrategyResult
- Direction
- BeloSoft.AnalyzeResults.WinnerRulesOperations uses BeloSoft.AnalyzeResults.Domain, so a change to BeloSoft.AnalyzeResults.Domain can break BeloSoft.AnalyzeResults.WinnerRulesOperations, while a change to BeloSoft.AnalyzeResults.WinnerRulesOperations can't break BeloSoft.AnalyzeResults.Domain.
- Position
- Below the diagonal: BeloSoft.AnalyzeResults.WinnerRulesOperations uses a module listed above it, which is the healthy direction.
29→5 BeloSoft.AnalyzeResults.WinnerRulesOperations uses BeloSoft.Bfexplorer.HorseRacingStatto.API.Models✕
- Connections
- 2 pairs of types, where a type in BeloSoft.AnalyzeResults.WinnerRulesOperations uses a type in BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.
- The types involved
BeloSoft.AnalyzeResults.WinnerRulesOperations.WinnerRulesOperations→BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.RaceResultDataBeloSoft.AnalyzeResults.WinnerRulesOperations.WinnerRulesOperations→BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.RaceRunnerData
- Direction
- BeloSoft.AnalyzeResults.WinnerRulesOperations uses BeloSoft.Bfexplorer.HorseRacingStatto.API.Models, so a change to BeloSoft.Bfexplorer.HorseRacingStatto.API.Models can break BeloSoft.AnalyzeResults.WinnerRulesOperations, while a change to BeloSoft.AnalyzeResults.WinnerRulesOperations can't break BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.
- Position
- Below the diagonal: BeloSoft.AnalyzeResults.WinnerRulesOperations uses a module listed above it, which is the healthy direction.
30→5 BeloSoft.ExportResultsToCSV uses BeloSoft.Bfexplorer.HorseRacingStatto.API.Models✕
- Connections
- 2 pairs of types, where a type in BeloSoft.ExportResultsToCSV uses a type in BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.
- The types involved
BeloSoft.ExportResultsToCSV.CsvDataWrapper→BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.RaceRunnerDataBeloSoft.ExportResultsToCSV.CsvDataWrapper→BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.RacingStattoData
- Direction
- BeloSoft.ExportResultsToCSV uses BeloSoft.Bfexplorer.HorseRacingStatto.API.Models, so a change to BeloSoft.Bfexplorer.HorseRacingStatto.API.Models can break BeloSoft.ExportResultsToCSV, while a change to BeloSoft.ExportResultsToCSV can't break BeloSoft.Bfexplorer.HorseRacingStatto.API.Models.
- Position
- Below the diagonal: BeloSoft.ExportResultsToCSV uses a module listed above it, which is the healthy direction.
31→7 BetfairMarketAnalyzer uses BetfairMarketAnalyzer.Models✕
- Connections
- 3 pairs of types, where a type in BetfairMarketAnalyzer uses a type in BetfairMarketAnalyzer.Models.
- The types involved
BetfairMarketAnalyzer.Program→BetfairMarketAnalyzer.Models.AnalysisResultBetfairMarketAnalyzer.Program→BetfairMarketAnalyzer.Models.MarketSelectionDataBetfairMarketAnalyzer.Program→BetfairMarketAnalyzer.Models.TradedPriceVolume
- Direction
- BetfairMarketAnalyzer uses BetfairMarketAnalyzer.Models, so a change to BetfairMarketAnalyzer.Models can break BetfairMarketAnalyzer, while a change to BetfairMarketAnalyzer can't break BetfairMarketAnalyzer.Models.
- Position
- Below the diagonal: BetfairMarketAnalyzer uses a module listed above it, which is the healthy direction.
32→7 BetfairMarketAnalyzer.Services uses BetfairMarketAnalyzer.Models✕
- Connections
- 11 pairs of types, where a type in BetfairMarketAnalyzer.Services uses a type in BetfairMarketAnalyzer.Models.
- The types involved
BetfairMarketAnalyzer.Services.ReportGeneratorService→BetfairMarketAnalyzer.Models.AnalysisResultBetfairMarketAnalyzer.Services.ReportGeneratorService→BetfairMarketAnalyzer.Models.MarketDataBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.AnalysisResultBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.BetfairQuoteBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.MarketFlowBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.MarketSelectionDataBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.SupportResistanceLevelBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.TechnicalIndicatorsBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.TradedPriceVolumeBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.TradingRecommendationBetfairMarketAnalyzer.Services.TechnicalAnalysisService→BetfairMarketAnalyzer.Models.VolumeAnalysis
- Direction
- BetfairMarketAnalyzer.Services uses BetfairMarketAnalyzer.Models, so a change to BetfairMarketAnalyzer.Models can break BetfairMarketAnalyzer.Services, while a change to BetfairMarketAnalyzer.Services can't break BetfairMarketAnalyzer.Models.
- Position
- Below the diagonal: BetfairMarketAnalyzer.Services uses a module listed above it, which is the healthy direction.
33→8 BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService uses BetfairMarketAnalyzerFSharp.Models✕
- Connections
- 2 pairs of types, where a type in BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService uses a type in BetfairMarketAnalyzerFSharp.Models.
- The types involved
BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService.ReportGeneratorService→BetfairMarketAnalyzerFSharp.Models.AnalysisResultBetfairMarketAnalyzerFSharp.Services.ReportGeneratorService.ReportGeneratorService→BetfairMarketAnalyzerFSharp.Models.MarketData
- Direction
- BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService uses BetfairMarketAnalyzerFSharp.Models, so a change to BetfairMarketAnalyzerFSharp.Models can break BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService, while a change to BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService can't break BetfairMarketAnalyzerFSharp.Models.
- Position
- Below the diagonal: BetfairMarketAnalyzerFSharp.Services.ReportGeneratorService uses a module listed above it, which is the healthy direction.
34→8 BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService uses BetfairMarketAnalyzerFSharp.Models✕
- Connections
- 9 pairs of types, where a type in BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService uses a type in BetfairMarketAnalyzerFSharp.Models.
- The types involved
BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.AnalysisResultBetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.BetfairQuoteBetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.MarketFlowBetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.MarketSelectionDataBetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.SupportResistanceLevelBetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.TechnicalIndicatorsBetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.TradedPriceVolumeBetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.TradingRecommendationBetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService.TechnicalAnalysisService→BetfairMarketAnalyzerFSharp.Models.VolumeAnalysis
- Direction
- BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService uses BetfairMarketAnalyzerFSharp.Models, so a change to BetfairMarketAnalyzerFSharp.Models can break BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService, while a change to BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService can't break BetfairMarketAnalyzerFSharp.Models.
- Position
- Below the diagonal: BetfairMarketAnalyzerFSharp.Services.TechnicalAnalysisService uses a module listed above it, which is the healthy direction.
35→8 Program uses BetfairMarketAnalyzerFSharp.Models✕
- Connections
- 3 pairs of types, where a type in Program uses a type in BetfairMarketAnalyzerFSharp.Models.
- The types involved
Program.Program→BetfairMarketAnalyzerFSharp.Models.AnalysisResultProgram.Program→BetfairMarketAnalyzerFSharp.Models.MarketSelectionDataProgram.Program→BetfairMarketAnalyzerFSharp.Models.TradedPriceVolume
- Direction
- Program uses BetfairMarketAnalyzerFSharp.Models, so a change to BetfairMarketAnalyzerFSharp.Models can break Program, while a change to Program can't break BetfairMarketAnalyzerFSharp.Models.
- Position
- Below the diagonal: Program uses a module listed above it, which is the healthy direction.
36→13 scripts uses scripts.validate_trading_report✕
- Connections
- 1 pair of types, where a type in scripts uses a type in scripts.validate_trading_report.
- The types involved
scripts.validate_trading_report→scripts.validate_trading_report.Report
- Direction
- scripts uses scripts.validate_trading_report, so a change to scripts.validate_trading_report can break scripts, while a change to scripts can't break scripts.validate_trading_report.
- Position
- Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
37→16 src.BetfairMarketAnalyzerPython uses src.BetfairMarketAnalyzerPython.models.betfair_models✕
- Connections
- 1 pair of types, where a type in src.BetfairMarketAnalyzerPython uses a type in src.BetfairMarketAnalyzerPython.models.betfair_models.
- The types involved
src.BetfairMarketAnalyzerPython.main→src.BetfairMarketAnalyzerPython.models.betfair_models.MarketSelectionData
- Direction
- src.BetfairMarketAnalyzerPython uses src.BetfairMarketAnalyzerPython.models.betfair_models, so a change to src.BetfairMarketAnalyzerPython.models.betfair_models can break src.BetfairMarketAnalyzerPython, while a change to src.BetfairMarketAnalyzerPython can't break src.BetfairMarketAnalyzerPython.models.betfair_models.
- Position
- Below the diagonal: src.BetfairMarketAnalyzerPython uses a module listed above it, which is the healthy direction.
38→15 src.BetfairMarketAnalyzerPython.services.report_generator_service uses src.BetfairMarketAnalyzerPython.models.analysis_models✕
- Connections
- 1 pair of types, where a type in src.BetfairMarketAnalyzerPython.services.report_generator_service uses a type in src.BetfairMarketAnalyzerPython.models.analysis_models.
- The types involved
src.BetfairMarketAnalyzerPython.services.report_generator_service.ReportGeneratorService→src.BetfairMarketAnalyzerPython.models.analysis_models.AnalysisResult
- Direction
- src.BetfairMarketAnalyzerPython.services.report_generator_service uses src.BetfairMarketAnalyzerPython.models.analysis_models, so a change to src.BetfairMarketAnalyzerPython.models.analysis_models can break src.BetfairMarketAnalyzerPython.services.report_generator_service, while a change to src.BetfairMarketAnalyzerPython.services.report_generator_service can't break src.BetfairMarketAnalyzerPython.models.analysis_models.
- Position
- Below the diagonal: src.BetfairMarketAnalyzerPython.services.report_generator_service uses a module listed above it, which is the healthy direction.
38→16 src.BetfairMarketAnalyzerPython.services.report_generator_service uses src.BetfairMarketAnalyzerPython.models.betfair_models✕
- Connections
- 1 pair of types, where a type in src.BetfairMarketAnalyzerPython.services.report_generator_service uses a type in src.BetfairMarketAnalyzerPython.models.betfair_models.
- The types involved
src.BetfairMarketAnalyzerPython.services.report_generator_service.ReportGeneratorService→src.BetfairMarketAnalyzerPython.models.betfair_models.MarketData
- Direction
- src.BetfairMarketAnalyzerPython.services.report_generator_service uses src.BetfairMarketAnalyzerPython.models.betfair_models, so a change to src.BetfairMarketAnalyzerPython.models.betfair_models can break src.BetfairMarketAnalyzerPython.services.report_generator_service, while a change to src.BetfairMarketAnalyzerPython.services.report_generator_service can't break src.BetfairMarketAnalyzerPython.models.betfair_models.
- Position
- Below the diagonal: src.BetfairMarketAnalyzerPython.services.report_generator_service uses a module listed above it, which is the healthy direction.
39→15 src.BetfairMarketAnalyzerPython.services.technical_analysis_service uses src.BetfairMarketAnalyzerPython.models.analysis_models✕
- Connections
- 3 pairs of types, where a type in src.BetfairMarketAnalyzerPython.services.technical_analysis_service uses a type in src.BetfairMarketAnalyzerPython.models.analysis_models.
- The types involved
src.BetfairMarketAnalyzerPython.services.technical_analysis_service.TechnicalAnalysisService→src.BetfairMarketAnalyzerPython.models.analysis_models.AnalysisResultsrc.BetfairMarketAnalyzerPython.services.technical_analysis_service.TechnicalAnalysisService→src.BetfairMarketAnalyzerPython.models.analysis_models.MarketFlowsrc.BetfairMarketAnalyzerPython.services.technical_analysis_service.TechnicalAnalysisService→src.BetfairMarketAnalyzerPython.models.analysis_models.TechnicalIndicators
- Direction
- src.BetfairMarketAnalyzerPython.services.technical_analysis_service uses src.BetfairMarketAnalyzerPython.models.analysis_models, so a change to src.BetfairMarketAnalyzerPython.models.analysis_models can break src.BetfairMarketAnalyzerPython.services.technical_analysis_service, while a change to src.BetfairMarketAnalyzerPython.services.technical_analysis_service can't break src.BetfairMarketAnalyzerPython.models.analysis_models.
- Position
- Below the diagonal: src.BetfairMarketAnalyzerPython.services.technical_analysis_service uses a module listed above it, which is the healthy direction.
39→16 src.BetfairMarketAnalyzerPython.services.technical_analysis_service uses src.BetfairMarketAnalyzerPython.models.betfair_models✕
- Connections
- 1 pair of types, where a type in src.BetfairMarketAnalyzerPython.services.technical_analysis_service uses a type in src.BetfairMarketAnalyzerPython.models.betfair_models.
- The types involved
src.BetfairMarketAnalyzerPython.services.technical_analysis_service.TechnicalAnalysisService→src.BetfairMarketAnalyzerPython.models.betfair_models.MarketSelectionData
- Direction
- src.BetfairMarketAnalyzerPython.services.technical_analysis_service uses src.BetfairMarketAnalyzerPython.models.betfair_models, so a change to src.BetfairMarketAnalyzerPython.models.betfair_models can break src.BetfairMarketAnalyzerPython.services.technical_analysis_service, while a change to src.BetfairMarketAnalyzerPython.services.technical_analysis_service can't break src.BetfairMarketAnalyzerPython.models.betfair_models.
- Position
- Below the diagonal: src.BetfairMarketAnalyzerPython.services.technical_analysis_service uses a module listed above it, which is the healthy direction.
40→15 src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic uses src.BetfairMarketAnalyzerPython.models.analysis_models✕
- Connections
- 3 pairs of types, where a type in src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic uses a type in src.BetfairMarketAnalyzerPython.models.analysis_models.
- The types involved
src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic.TechnicalAnalysisServiceBasic→src.BetfairMarketAnalyzerPython.models.analysis_models.AnalysisResultsrc.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic.TechnicalAnalysisServiceBasic→src.BetfairMarketAnalyzerPython.models.analysis_models.MarketFlowsrc.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic.TechnicalAnalysisServiceBasic→src.BetfairMarketAnalyzerPython.models.analysis_models.TechnicalIndicators
- Direction
- src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic uses src.BetfairMarketAnalyzerPython.models.analysis_models, so a change to src.BetfairMarketAnalyzerPython.models.analysis_models can break src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic, while a change to src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic can't break src.BetfairMarketAnalyzerPython.models.analysis_models.
- Position
- Below the diagonal: src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic uses a module listed above it, which is the healthy direction.
40→16 src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic uses src.BetfairMarketAnalyzerPython.models.betfair_models✕
- Connections
- 1 pair of types, where a type in src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic uses a type in src.BetfairMarketAnalyzerPython.models.betfair_models.
- The types involved
src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic.TechnicalAnalysisServiceBasic→src.BetfairMarketAnalyzerPython.models.betfair_models.MarketSelectionData
- Direction
- src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic uses src.BetfairMarketAnalyzerPython.models.betfair_models, so a change to src.BetfairMarketAnalyzerPython.models.betfair_models can break src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic, while a change to src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic can't break src.BetfairMarketAnalyzerPython.models.betfair_models.
- Position
- Below the diagonal: src.BetfairMarketAnalyzerPython.services.technical_analysis_service_basic uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 20 | High / Critical |
| A07:2025 — Authentication Failures | 1 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | High / 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +11.6 pts | Low | Secret Scanning |
| Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5). | +4.6 pts | Low | Dependency Hygiene |
| Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene. | +3.7 pts | Low | Dependency Hygiene |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +3.2 pts | Medium | CI/CD gates |
| Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run. | +3.2 pts | Medium | Observability |
| Add tests that import the unreached modules (directly or through their public entry). | +3.2 pts | Medium | Test Coverage |
| Resolve the 8 redundant comment finding(s) in Comment Value — start with Program.cs (2), TechnicalAnalysisService.cs (2), ChartDisplay.tsx (2). | +1.5 pts | Low | Comment Value |
| Resolve the 2 BareSuppressMessage finding(s) in Explicit Debt — start with GlobalSuppressions.cs (2). | +1.2 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| src/MarketDataBrowser/src/components/ChartDisplay.tsx | 6.6 | Mixed | Cyclomatic Complexity: ChartDisplay.ChartDisplay (cyclomatic 23) |
| src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py | 7.0 | Mixed | Cyclomatic Complexity: TechnicalAnalysisService._generate_trading_recommendations (cyclomatic 17) |
| src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs | 7.2 | Mixed | Cyclomatic Complexity: TechnicalAnalysisService.calculateTechnicalIndicators (cyclomatic 23) |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/AiAgentCSharp/Program.cs | 7.3 | Mixed | Explicit Debt: CommentedOutCode |
| src/HelloBetfair/CSharp/MyStrategyBotTrigger/GlobalSuppressions.cs | 7.3 | Mixed | Explicit Debt: BareSuppressMessage |
| src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs | 7.4 | Mixed | Cognitive Complexity: QuipuAnalyze.deriveRuleExpression (cognitive 27) |
| src/MarketDataBrowser/src/components/TableDisplay.tsx | 7.8 | Mixed | Cyclomatic Complexity: TableDisplay.TableDisplay (cyclomatic 18) |
| src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py | 7.8 | Mixed | Cyclomatic Complexity: TechnicalAnalysisServiceBasic._generate_trading_recommendations (cyclomatic 17) |
| src/RacingStatto/FSharp/AnalyzeResults/Models.fs | 7.8 | Mixed | Code Duplication: Edited copy of a member (75 corresponding lines) |
| src/MarketDataBrowser/package.json | 7.8 | Mixed | Dependency Hygiene: Deprecated: eslint |
| src/MarketDataBrowser/src/store/useStore.ts | 8.5 | Near-clean | Cyclomatic Complexity: useStore.transformRacingpostData (cyclomatic 18) |
| src/BetfairMarketAnalyzerPython/services/report_generator_service.py | 8.5 | Near-clean | Cognitive Complexity: ReportGeneratorService._generate_technical_analysis (cognitive 18) |
| src/RacingStatto/FSharp/ExportResultsToCSV/Program.fs | 8.5 | Near-clean | Cognitive Complexity: App.main (cognitive 17) |
| src/AiAgentPython/agentBet.py | 8.5 | Near-clean | Code Duplication: Duplicated block (44 lines × 2) |
| src/BetfairMarketAnalyzer/Models/BetfairModels.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (17 lines × 2) |
| src/RacingStatto/FSharp/AnalyzeResults/RulesOperations.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| scripts/parse_strategy_logs.py | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 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.
What we checked — 53 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 106 of 141 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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 Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TechnicalAnalysisService.calculateTechnicalIndicators at 23.
What to do
- 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.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was TechnicalAnalysisService.calculateTechnicalIndicators at 44.
What to do
- 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.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with ChartDisplay.tsx. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
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.
What to do
- 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).
- 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).
- 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).
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
D12 · Dependency Hygiene
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).
What to do
- Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
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).
What to do
- 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).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 DeadPreprocessorBranch finding(s) in Explicit Debt — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 445 document(s) read across 6 unit(s).
D20 · ADR Quality
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.
D24 · Comment Value
8 of 71 judged comments only repeat the code they sit on (11.3 %).
What to do
- 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).
D26 · Project Cohesion
0 of 4 projects flagged as possibly oversized/incoherent.
D27 · Navigability
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.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. 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.
D30 · Dependency Vulnerabilities
20 finding(s): 0 critical, 15 high, 4 medium, 1 low.
What to do
- 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).
- 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).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- 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).
D34 · Knowledge Freshness
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.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
- 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 gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
- 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 tooling
- 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 & Rollback
- 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 & Backup
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 Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 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 Complexity
- (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 Files
R4 · 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
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- 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 Code
- 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 Hygiene
R9 · Circular Imports
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 88% | Strong | Solid. |
| Readiness | 18% | Critical — gated by R4, P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 99% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- 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
- 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)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 57 finding(s)
- Prerelease dependency: Azure.AI.Inference
- Prerelease dependency: Azure.AI.OpenAI
- Prerelease dependency: Microsoft.Extensions.AI.AzureAIInference
- Prerelease dependency: Quipu
- REDACTED
- REDACTED
- REDACTED
- BareSuppressMessage src/HelloBetfair/CSharp/MyStrategyBotTrigger/GlobalSuppressions.cs:8
- BareSuppressMessage src/HelloBetfair/CSharp/MyStrategyBotTrigger/GlobalSuppressions.cs:9
- 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
- TechnicalAnalysisServiceBasic._generate_trading_recommendations (cyclomatic 17) src/BetfairMarketAnalyzerPython/services/technical_analysis_service_basic.py:405
- Deprecated: eslint src/MarketDataBrowser/package.json:27
- CommentedOutCode src/AiAgentCSharp/Program.cs:36
- DeadPreprocessorBranch src/AiAgentCSharp/Program.cs:24
- 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
- TechnicalAnalysisService.analyzeMarketFlow (cognitive 22) src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs:167
- ReportGeneratorService._generate_technical_analysis (cognitive 18) src/BetfairMarketAnalyzerPython/services/report_generator_service.py:97
- TechnicalAnalysisService.generateTradingRecommendations (cognitive 18) src/BetfairMarketAnalyzerFSharp/Services/TechnicalAnalysisService.fs:236
- App.main (cognitive 17) src/RacingStatto/FSharp/ExportResultsToCSV/Program.fs:89
- TableDisplay.TableDisplay (cognitive 16) src/MarketDataBrowser/src/components/TableDisplay.tsx:24
- FunctionTooLong: ChartDisplay.ChartDisplay src/MarketDataBrowser/src/components/ChartDisplay.tsx:6
- REDACTED
- 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
- Duplicated block (54 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:263
- Duplicated block (46 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:187
- Duplicated block (28 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:75
- Duplicated block (26 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:235
- Duplicated block (44 lines × 2) src/AiAgentPython/agentBet.py:18
- Duplicated block (17 lines × 2) src/BetfairMarketAnalyzer/Models/BetfairModels.cs:7
- Duplicated block (15 lines × 4) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:153
- Duplicated block (18 lines × 2) src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:133
- Duplicated block (56 lines × 2) src/RacingStatto/FSharp/AnalyzeResults/Models.fs:1
- Duplicated block (15 lines × 2) src/RacingStatto/FSharp/AnalyzeResults/RulesOperations.fs:9
- Duplicated block (11–12 lines × 3) src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:170
- Duplicated block (11 lines × 2) src/RacingStatto/FSharp/AnalyzeResults/QuipuOperations.fs:108
- Duplicated block (6 lines × 2) scripts/parse_strategy_logs.py:72
- No CI pipeline
- No structured logging
- Duplicated block with local edits (24 matched lines × 2 locations) src/MarketDataBrowser/src/components/ChartDisplay.tsx:164
- Complex function (anonymous) (cyclomatic 16, cognitive 13) src/MarketDataBrowser/src/store/useStore.ts:18
- Test Coverage
- No test script
- Dead file (~101 LoC) src/MarketDataBrowser/src/components/layout/Topbar.tsx
- NuGet dependencies are not locked
- JavaScript dependencies are not locked docs/.obsidian/plugins/marp-slides/lib3/markdown-it/@kazumatu981/markdown-it-kroki/package.json:28
Minor — 44 finding(s)
- README/code drift docs/README.md:61
- README/code drift docs/Prompts/README.md:30
- README/code drift docs/Research/README.md:15
- README/code drift docs/Research/README.md:17
- README/code drift docs/Research/README.md:18
- README/code drift docs/Research/README.md:19
- README/code drift docs/Research/README.md:20
- README/code drift docs/Research/README.md:21
- README/code drift docs/Research/README.md:22
- README/code drift docs/Research/README.md:23
- README/code drift docs/Research/README.md:24
- README/code drift docs/Research/README.md:26
- README/code drift docs/Research/README.md:36
- README/code drift docs/Research/README.md:37
- README/code drift docs/Research/README.md:38
- README/code drift src/AiAgentCSharp/README.md:159
- redundant comment src/BetfairMarketAnalyzer/Program.cs:24
- redundant comment src/BetfairMarketAnalyzer/Program.cs:78
- redundant comment src/BetfairMarketAnalyzer/Services/ReportGeneratorService.cs:27
- redundant comment src/BetfairMarketAnalyzer/Services/TechnicalAnalysisService.cs:22
- redundant comment src/BetfairMarketAnalyzer/Services/TechnicalAnalysisService.cs:34
- redundant comment src/MarketDataBrowser/src/components/ChartDisplay.tsx:103
- redundant comment src/MarketDataBrowser/src/components/ChartDisplay.tsx:113
- redundant comment src/MarketDataBrowser/src/types/index.ts:20
- Deprecated: @humanwhocodes/config-array REDACTED:812
- Deprecated: @humanwhocodes/object-schema REDACTED:866
- Deprecated: glob REDACTED:2552
- Deprecated: inflight REDACTED:2753
- Deprecated: rimraf REDACTED:3367
- Outdated (npm): ag-grid-community src/MarketDataBrowser/package.json:18
- Outdated (npm): ag-grid-react src/MarketDataBrowser/package.json:17
- Outdated (npm): js-tokens
- Outdated (npm): react-is
- Duplicated predicate src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:355
- Duplicated predicate src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:392
- Duplicated predicate src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:335
- Duplicated predicate src/BetfairMarketAnalyzerPython/services/technical_analysis_service.py:372
- REDACTED
- No SAST
- No dependency-update automation src/AiAgentCSharp/AiAgentCSharp.csproj:18
- No release approval gate
- Unused export 'ApiResponse' src/MarketDataBrowser/src/types/index.ts:31
- Silent fallback default in catch src/BetfairMarketAnalyzer/Services/TechnicalAnalysisService.cs:125
- Pending state with no failure state src/MarketDataBrowser/src/components/ChartDisplay.tsx:168
Minor — 23 finding(s)
- Outdated (npm): @types/react
- Outdated (npm): asynckit
- Outdated (npm): axios
- Outdated (npm): es-object-atoms
- Outdated (npm): follow-redirects
- Outdated (npm): form-data
- Outdated (npm): hasown
- Outdated (npm): lightweight-charts
- Outdated (npm): mime-db
- Outdated (npm): mime-types
- Outdated (npm): proxy-from-env
- Outdated (npm): react
- Outdated (npm): react-dom
- Outdated (npm): scheduler
- Outdated (npm): use-sync-external-store
- Outdated (npm): zustand
- Outdated: Microsoft.Extensions.AI
- Outdated: Microsoft.Extensions.AI.OpenAI
- Outdated: Microsoft.Extensions.Configuration.UserSecrets
- Outdated: ModelContextProtocol.Core
- Outdated: FSharp.Core
- Outdated: CsvHelper
- doc comments repeat the names src/AiAgentCSharp/AiAgentHelpers.cs:8
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-336d5b3c798b45d2a88af8b9c787588d/history.json --exit-code 0 --source . | 4 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-336d5b3c798b45d2a88af8b9c787588d/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list BetfairAiTrading.slnx package --vulnerable --include-transitive --format json | 20 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/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 & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |