Executive summary
Zuytan/rustrade meets our standard for a template or a sample. It scores 63 out of 100 and is rated Strong, and 28 of its 30 critical findings are security problems in the build pipeline and in its code.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is protecting outgoing calls with timeouts, worth about 4 points. Automating dependency updates comes next, worth about 3 points.
Twenty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two weaknesses in the code could be used by an attacker. Pinning each tool to an exact version and fixing the weaknesses the scanner points to would close both risks. Saving the change and the message together would take care of the place where data is saved and a message sent separately.
The product code is 52,428 lines, about €90,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
New since the last survey: 36 findings
- Cyclomatic Complexity · SizingEngine::calculate_quantity (cyclomatic 18) src/application/risk_management/position/sizing_engine.rs
- Cyclomatic Complexity · Executor::handle_order (cyclomatic 16) src/application/agents/executor/mod.rs
- Cyclomatic Complexity · AlpacaExecutionService::execute (cyclomatic 16) src/infrastructure/alpaca/execution.rs
- Cognitive Complexity · Executor::handle_order (cognitive 24) src/application/agents/executor/mod.rs
- Cognitive Complexity · Executor::update_portfolio (cognitive 22) src/application/agents/executor/acceptance.rs
- Cognitive Complexity · Executor::reconcile_pending (cognitive 22) src/application/agents/executor/reconciliation.rs
- Cognitive Complexity · Executor::run (cognitive 19) src/application/agents/executor/mod.rs
- Cognitive Complexity · AlpacaExecutionService::execute (cognitive 18) src/infrastructure/alpaca/execution.rs
- Cognitive Complexity · check_coverage.main (cognitive 18) scripts/check_coverage.py
- Cognitive Complexity · CandleAggregator::on_quote (cognitive 17) src/application/market_data/candle_aggregator.rs
- Cognitive Complexity · TradeEvaluator::evaluate_and_propose (cognitive 16) src/application/agents/trade_evaluator.rs
- Cognitive Complexity · RiskManager::update_portfolio_valuation (cognitive 16) src/application/risk_management/core/risk_manager/valuation.rs
- God Classes · MethodTooLong: Database.apply_v1 REDACTED
- God Classes · ClassTooLong: AlpacaExecutionService src/infrastructure/alpaca/execution.rs
- God Classes · FileTooLong: alpaca/execution.rs src/infrastructure/alpaca/execution.rs
- Code Duplication · Duplicated block (12 lines × 2) src/infrastructure/alpaca/execution.rs
- Churn × Complexity Hotspots · Hotspot: src/application/risk_management/position/sizing_engine.rs src/application/risk_management/position/sizing_engine.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Change Coupling · Change coupling: risk_manager.rs ↔ execution.rs src/application/risk_management/core/risk_manager.rs
- Outbound HTTP resilience · Outbound HTTP without resilience src/application/risk_management/core/risk_manager/alerts.rs
Fixed since the last survey: 46 findings
- Cyclomatic Complexity · CircuitBreakerService::check_circuit_breaker (cyclomatic 16) src/application/risk_management/validation/circuit_breaker_service.rs
- Cognitive Complexity · Executor::handle_order (cognitive 28) src/application/agents/executor.rs
- Cognitive Complexity · CircuitBreakerService::check_circuit_breaker (cognitive 27) src/application/risk_management/validation/circuit_breaker_service.rs
- Cognitive Complexity · Executor::update_portfolio (cognitive 22) src/application/agents/executor.rs
- Cognitive Complexity · RiskManager::update_portfolio_valuation (cognitive 16) src/application/risk_management/core/risk_manager.rs
- God Classes · MethodTooLong: Database.init REDACTED
- God Classes · ClassTooLong: RiskManager src/application/risk_management/core/risk_manager.rs
- Code Duplication · Duplicated block (12 lines × 2) src/application/risk_management/validation/circuit_breaker_service.rs
- Churn × Complexity Hotspots · Hotspot: src/application/bootstrap/agents.rs src/application/bootstrap/agents.rs
- Churn × Complexity Hotspots · Hotspot: src/bin/benchmark.rs src/bin/benchmark.rs
- Churn × Complexity Hotspots · Hotspot: src/interfaces/dashboard.rs src/interfaces/dashboard.rs
- Churn × Complexity Hotspots · Hotspot: src/interfaces/dashboard_components/architecture_view.rs src/interfaces/dashboard_components/architecture_view.rs
- Churn × Complexity Hotspots · Hotspot: src/main.rs src/main.rs
- Churn × Complexity Hotspots · Hotspot: src/application/agents/analyst.rs src/application/agents/analyst.rs
- Churn × Complexity Hotspots · Hotspot: src/application/agents/user_agent.rs src/application/agents/user_agent.rs
- Churn × Complexity Hotspots · Hotspot: src/application/optimization/core/walk_forward.rs src/application/optimization/core/walk_forward.rs
- Churn × Complexity Hotspots · Hotspot: src/infrastructure/alpaca/websocket.rs src/infrastructure/alpaca/websocket.rs
- Churn × Complexity Hotspots · Hotspot: src/interfaces/ui_components/settings_state.rs src/interfaces/ui_components/settings_state.rs
- Churn × Complexity Hotspots · Hotspot: src/infrastructure/persistence/repositories/mod.rs src/infrastructure/persistence/repositories/mod.rs
- Churn × Complexity Hotspots · Hotspot: src/application/agents/executor.rs src/application/agents/executor.rs
- Churn × Complexity Hotspots · Hotspot: src/interfaces/dashboard_components/chart_panel.rs src/interfaces/dashboard_components/chart_panel.rs
- Churn × Complexity Hotspots · Hotspot: src/interfaces/dashboard_components/analytics_view.rs src/interfaces/dashboard_components/analytics_view.rs
- Churn × Complexity Hotspots · Hotspot: src/domain/performance/metrics.rs src/domain/performance/metrics.rs
- Churn × Complexity Hotspots · Hotspot: src/interfaces/dashboard_components/symbol_card.rs src/interfaces/dashboard_components/symbol_card.rs
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: RUSTSEC-2026-0382 REDACTED
- Dependency Vulnerabilities · Medium CVE: RUSTSEC-2026-0383 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0186 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0190 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0221 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0194 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0204 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0235 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0257 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0258 REDACTED
- Change Coupling · Change coupling: mod.rs ↔ execution_service.rs src/application/system/mod.rs
- Change Coupling · Change coupling: risk_manager.rs ↔ execution_service.rs src/application/risk_management/core/risk_manager.rs
- Access Controls · No authorization src/infrastructure/api/mod.rs
- Outbound HTTP resilience · Outbound HTTP without resilience src/application/risk_management/core/risk_manager.rs
Rebuild cost: about €90,000 · Estimate
| Cost to rebuild | €30,000 to €150,000, for 496 to 1,574 hours of work, about 0.6 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | High, 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.9 at a score of 63. 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 | Medium: 52,428 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 application.bootstrap.persistence | 2 application.market_data.spread_cache | 3 application.monitoring.health.connection_health_service | 4 application.monitoring.strategy.strategy_validator | 5 config | 6 domain.market.market_regime | 7 domain.market.strategy_config | 8 domain.market.timeframe | 9 domain.risk.risk_appetite | 10 domain.risk.state | 11 domain.snn.competitive_network | 12 infrastructure.i18n.service | 13 infrastructure.observability.metrics | 14 application.agents.analyst_config | 15 application.monitoring.health.agent_status | 16 domain.risk.optimal_parameters | 17 domain.trading.types | 18 application.optimization.core.grid | 19 application.optimization.core.types | 20 application.strategies.traits | 21 application.trading.symbol_context | 22 domain.ports | 23 domain.trading.portfolio | 24 interfaces.ui_components.settings_state | 25 application.agents.executor | 26 application.agents.signal_processor | 27 application.optimization.core.walk_forward | 28 application.risk_management.core.risk_manager | 29 domain.repositories | 30 domain.risk.filters.validator_trait | 31 application.agents.news_handler | 32 application.agents.trade_evaluator | 33 application.optimization.adaptive_optimization_service | 34 application.agents.candle_pipeline | 35 application.bootstrap.services | 36 application.agents.analyst | 37 application.bootstrap.agents | 38 application.system | 39 application.client | 40 application.agents.user_agent |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 application.bootstrap.persistence | ||||||||||||||||||||||||||||||||||||||||
| 2 application.market_data.spread_cache | ||||||||||||||||||||||||||||||||||||||||
| 3 application.monitoring.health.connection_health_service | ||||||||||||||||||||||||||||||||||||||||
| 4 application.monitoring.strategy.strategy_validator | ||||||||||||||||||||||||||||||||||||||||
| 5 config | ||||||||||||||||||||||||||||||||||||||||
| 6 domain.market.market_regime | ||||||||||||||||||||||||||||||||||||||||
| 7 domain.market.strategy_config | ||||||||||||||||||||||||||||||||||||||||
| 8 domain.market.timeframe | ||||||||||||||||||||||||||||||||||||||||
| 9 domain.risk.risk_appetite | ||||||||||||||||||||||||||||||||||||||||
| 10 domain.risk.state | ||||||||||||||||||||||||||||||||||||||||
| 11 domain.snn.competitive_network | ||||||||||||||||||||||||||||||||||||||||
| 12 infrastructure.i18n.service | ||||||||||||||||||||||||||||||||||||||||
| 13 infrastructure.observability.metrics | ||||||||||||||||||||||||||||||||||||||||
| 14 application.agents.analyst_config | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 application.monitoring.health.agent_status | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 domain.risk.optimal_parameters | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 domain.trading.types | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 application.optimization.core.grid | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 application.optimization.core.types | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 20 application.strategies.traits | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 application.trading.symbol_context | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 22 domain.ports | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 23 domain.trading.portfolio | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 interfaces.ui_components.settings_state | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 application.agents.executor | 2 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 application.agents.signal_processor | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 application.optimization.core.walk_forward | 1 | 2 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 28 application.risk_management.core.risk_manager | 1 | 2 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 29 domain.repositories | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 domain.risk.filters.validator_trait | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 application.agents.news_handler | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 application.agents.trade_evaluator | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 application.optimization.adaptive_optimization_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 application.agents.candle_pipeline | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 application.bootstrap.services | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 application.agents.analyst | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 37 application.bootstrap.agents | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 38 application.system | 1 | 1 | 2 | 1 | 1 | 1 | 2 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||
| 39 application.client | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 40 application.agents.user_agent | 2 | 1 | 1 | 1 | 1 | 1 | 1 |
14→5 application.agents.analyst_config uses config✕
- Connections
- 1 pair of types, where a type in application.agents.analyst_config uses a type in config.
- The types involved
rustrade.application.agents.analyst_config.AnalystConfig→rustrade.config.Config
- Direction
- application.agents.analyst_config uses config, so a change to config can break application.agents.analyst_config, while a change to application.agents.analyst_config can't break config.
- Position
- Below the diagonal: application.agents.analyst_config uses a module listed above it, which is the healthy direction.
14→9 application.agents.analyst_config uses domain.risk.risk_appetite✕
- Connections
- 1 pair of types, where a type in application.agents.analyst_config uses a type in domain.risk.risk_appetite.
- The types involved
rustrade.application.agents.analyst_config.AnalystConfig→rustrade.domain.risk.risk_appetite.RiskAppetite
- Direction
- application.agents.analyst_config uses domain.risk.risk_appetite, so a change to domain.risk.risk_appetite can break application.agents.analyst_config, while a change to application.agents.analyst_config can't break domain.risk.risk_appetite.
- Position
- Below the diagonal: application.agents.analyst_config uses a module listed above it, which is the healthy direction.
15→13 application.monitoring.health.agent_status uses infrastructure.observability.metrics✕
- Connections
- 1 pair of types, where a type in application.monitoring.health.agent_status uses a type in infrastructure.observability.metrics.
- The types involved
rustrade.application.monitoring.health.agent_status.AgentStatusRegistry→rustrade.infrastructure.observability.metrics.Metrics
- Direction
- application.monitoring.health.agent_status uses infrastructure.observability.metrics, so a change to infrastructure.observability.metrics can break application.monitoring.health.agent_status, while a change to application.monitoring.health.agent_status can't break infrastructure.observability.metrics.
- Position
- Below the diagonal: application.monitoring.health.agent_status uses a module listed above it, which is the healthy direction.
16→9 domain.risk.optimal_parameters uses domain.risk.risk_appetite✕
- Connections
- 3 pairs of types, where a type in domain.risk.optimal_parameters uses a type in domain.risk.risk_appetite.
- The types involved
rustrade.domain.risk.optimal_parameters.OptimalParameters→rustrade.domain.risk.risk_appetite.RiskProfilerustrade.domain.risk.optimal_parameters.OptimalParametersSet→rustrade.domain.risk.risk_appetite.RiskProfilerustrade.domain.risk.optimal_parameters.optimal_parameters$module→rustrade.domain.risk.risk_appetite.RiskProfile
- Direction
- domain.risk.optimal_parameters uses domain.risk.risk_appetite, so a change to domain.risk.risk_appetite can break domain.risk.optimal_parameters, while a change to domain.risk.optimal_parameters can't break domain.risk.risk_appetite.
- Position
- Below the diagonal: domain.risk.optimal_parameters uses a module listed above it, which is the healthy direction.
17→8 domain.trading.types uses domain.market.timeframe✕
- Connections
- 1 pair of types, where a type in domain.trading.types uses a type in domain.market.timeframe.
- The types involved
rustrade.domain.trading.types.FeatureSet→rustrade.domain.market.timeframe.Timeframe
- Direction
- domain.trading.types uses domain.market.timeframe, so a change to domain.market.timeframe can break domain.trading.types, while a change to domain.trading.types can't break domain.market.timeframe.
- Position
- Below the diagonal: domain.trading.types uses a module listed above it, which is the healthy direction.
18→7 application.optimization.core.grid uses domain.market.strategy_config✕
- Connections
- 1 pair of types, where a type in application.optimization.core.grid uses a type in domain.market.strategy_config.
- The types involved
rustrade.application.optimization.core.grid.grid$module→rustrade.domain.market.strategy_config.StrategyMode
- Direction
- application.optimization.core.grid uses domain.market.strategy_config, so a change to domain.market.strategy_config can break application.optimization.core.grid, while a change to application.optimization.core.grid can't break domain.market.strategy_config.
- Position
- Below the diagonal: application.optimization.core.grid uses a module listed above it, which is the healthy direction.
18→14 application.optimization.core.grid uses application.agents.analyst_config✕
- Connections
- 1 pair of types, where a type in application.optimization.core.grid uses a type in application.agents.analyst_config.
- The types involved
rustrade.application.optimization.core.grid.grid$module→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- application.optimization.core.grid uses application.agents.analyst_config, so a change to application.agents.analyst_config can break application.optimization.core.grid, while a change to application.optimization.core.grid can't break application.agents.analyst_config.
- Position
- Below the diagonal: application.optimization.core.grid uses a module listed above it, which is the healthy direction.
19→9 application.optimization.core.types uses domain.risk.risk_appetite✕
- Connections
- 1 pair of types, where a type in application.optimization.core.types uses a type in domain.risk.risk_appetite.
- The types involved
rustrade.application.optimization.core.types.OptimizationResult→rustrade.domain.risk.risk_appetite.RiskProfile
- Direction
- application.optimization.core.types uses domain.risk.risk_appetite, so a change to domain.risk.risk_appetite can break application.optimization.core.types, while a change to application.optimization.core.types can't break domain.risk.risk_appetite.
- Position
- Below the diagonal: application.optimization.core.types uses a module listed above it, which is the healthy direction.
19→14 application.optimization.core.types uses application.agents.analyst_config✕
- Connections
- 1 pair of types, where a type in application.optimization.core.types uses a type in application.agents.analyst_config.
- The types involved
rustrade.application.optimization.core.types.OptimizationResult→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- application.optimization.core.types uses application.agents.analyst_config, so a change to application.agents.analyst_config can break application.optimization.core.types, while a change to application.optimization.core.types can't break application.agents.analyst_config.
- Position
- Below the diagonal: application.optimization.core.types uses a module listed above it, which is the healthy direction.
19→16 application.optimization.core.types uses domain.risk.optimal_parameters✕
- Connections
- 2 pairs of types, where a type in application.optimization.core.types uses a type in domain.risk.optimal_parameters.
- The types involved
rustrade.application.optimization.core.types.OptimizationResult→rustrade.domain.risk.optimal_parameters.AssetTyperustrade.application.optimization.core.types.OptimizationResult→rustrade.domain.risk.optimal_parameters.OptimalParameters
- Direction
- application.optimization.core.types uses domain.risk.optimal_parameters, so a change to domain.risk.optimal_parameters can break application.optimization.core.types, while a change to application.optimization.core.types can't break domain.risk.optimal_parameters.
- Position
- Below the diagonal: application.optimization.core.types uses a module listed above it, which is the healthy direction.
19→17 application.optimization.core.types uses domain.trading.types✕
- Connections
- 2 pairs of types, where a type in application.optimization.core.types uses a type in domain.trading.types.
- The types involved
rustrade.application.optimization.core.types.PrefetchedBars→rustrade.domain.trading.types.Candlerustrade.application.optimization.core.types.SinglePeriodBars→rustrade.domain.trading.types.Candle
- Direction
- application.optimization.core.types uses domain.trading.types, so a change to domain.trading.types can break application.optimization.core.types, while a change to application.optimization.core.types can't break domain.trading.types.
- Position
- Below the diagonal: application.optimization.core.types uses a module listed above it, which is the healthy direction.
20→8 application.strategies.traits uses domain.market.timeframe✕
- Connections
- 2 pairs of types, where a type in application.strategies.traits uses a type in domain.market.timeframe.
- The types involved
rustrade.application.strategies.traits.AnalysisContext→rustrade.domain.market.timeframe.Timeframerustrade.application.strategies.traits.TimeframeFeatures→rustrade.domain.market.timeframe.Timeframe
- Direction
- application.strategies.traits uses domain.market.timeframe, so a change to domain.market.timeframe can break application.strategies.traits, while a change to application.strategies.traits can't break domain.market.timeframe.
- Position
- Below the diagonal: application.strategies.traits uses a module listed above it, which is the healthy direction.
20→17 application.strategies.traits uses domain.trading.types✕
- Connections
- 3 pairs of types, where a type in application.strategies.traits uses a type in domain.trading.types.
- The types involved
rustrade.application.strategies.traits.AnalysisContext→rustrade.domain.trading.types.FeatureSetrustrade.application.strategies.traits.AnalysisContext→rustrade.domain.trading.types.OrderSiderustrade.application.strategies.traits.Signal→rustrade.domain.trading.types.OrderSide
- Direction
- application.strategies.traits uses domain.trading.types, so a change to domain.trading.types can break application.strategies.traits, while a change to application.strategies.traits can't break domain.trading.types.
- Position
- Below the diagonal: application.strategies.traits uses a module listed above it, which is the healthy direction.
21→6 application.trading.symbol_context uses domain.market.market_regime✕
- Connections
- 1 pair of types, where a type in application.trading.symbol_context uses a type in domain.market.market_regime.
- The types involved
rustrade.application.trading.symbol_context.SymbolContext→rustrade.domain.market.market_regime.MarketRegimeDetector
- Direction
- application.trading.symbol_context uses domain.market.market_regime, so a change to domain.market.market_regime can break application.trading.symbol_context, while a change to application.trading.symbol_context can't break domain.market.market_regime.
- Position
- Below the diagonal: application.trading.symbol_context uses a module listed above it, which is the healthy direction.
21→7 application.trading.symbol_context uses domain.market.strategy_config✕
- Connections
- 1 pair of types, where a type in application.trading.symbol_context uses a type in domain.market.strategy_config.
- The types involved
rustrade.application.trading.symbol_context.SymbolContext→rustrade.domain.market.strategy_config.StrategyMode
- Direction
- application.trading.symbol_context uses domain.market.strategy_config, so a change to domain.market.strategy_config can break application.trading.symbol_context, while a change to application.trading.symbol_context can't break domain.market.strategy_config.
- Position
- Below the diagonal: application.trading.symbol_context uses a module listed above it, which is the healthy direction.
21→8 application.trading.symbol_context uses domain.market.timeframe✕
- Connections
- 1 pair of types, where a type in application.trading.symbol_context uses a type in domain.market.timeframe.
- The types involved
rustrade.application.trading.symbol_context.SymbolContext→rustrade.domain.market.timeframe.Timeframe
- Direction
- application.trading.symbol_context uses domain.market.timeframe, so a change to domain.market.timeframe can break application.trading.symbol_context, while a change to application.trading.symbol_context can't break domain.market.timeframe.
- Position
- Below the diagonal: application.trading.symbol_context uses a module listed above it, which is the healthy direction.
21→14 application.trading.symbol_context uses application.agents.analyst_config✕
- Connections
- 1 pair of types, where a type in application.trading.symbol_context uses a type in application.agents.analyst_config.
- The types involved
rustrade.application.trading.symbol_context.SymbolContext→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- application.trading.symbol_context uses application.agents.analyst_config, so a change to application.agents.analyst_config can break application.trading.symbol_context, while a change to application.trading.symbol_context can't break application.agents.analyst_config.
- Position
- Below the diagonal: application.trading.symbol_context uses a module listed above it, which is the healthy direction.
21→17 application.trading.symbol_context uses domain.trading.types✕
- Connections
- 2 pairs of types, where a type in application.trading.symbol_context uses a type in domain.trading.types.
- The types involved
rustrade.application.trading.symbol_context.SymbolContext→rustrade.domain.trading.types.Candlerustrade.application.trading.symbol_context.SymbolContext→rustrade.domain.trading.types.FeatureSet
- Direction
- application.trading.symbol_context uses domain.trading.types, so a change to domain.trading.types can break application.trading.symbol_context, while a change to application.trading.symbol_context can't break domain.trading.types.
- Position
- Below the diagonal: application.trading.symbol_context uses a module listed above it, which is the healthy direction.
22→6 domain.ports uses domain.market.market_regime✕
- Connections
- 1 pair of types, where a type in domain.ports uses a type in domain.market.market_regime.
- The types involved
rustrade.domain.ports.ExpectancyEvaluator→rustrade.domain.market.market_regime.MarketRegime
- Direction
- domain.ports uses domain.market.market_regime, so a change to domain.market.market_regime can break domain.ports, while a change to domain.ports can't break domain.market.market_regime.
- Position
- Below the diagonal: domain.ports uses a module listed above it, which is the healthy direction.
22→17 domain.ports uses domain.trading.types✕
- Connections
- 6 pairs of types, where a type in domain.ports uses a type in domain.trading.types.
- The types involved
rustrade.domain.ports.BrokerOrderState→rustrade.domain.trading.types.OrderStatusrustrade.domain.ports.ExecutionService→rustrade.domain.trading.types.Orderrustrade.domain.ports.FeatureEngineeringService→rustrade.domain.trading.types.Candlerustrade.domain.ports.FeatureEngineeringService→rustrade.domain.trading.types.FeatureSetrustrade.domain.ports.OrderUpdate→rustrade.domain.trading.types.OrderSiderustrade.domain.ports.OrderUpdate→rustrade.domain.trading.types.OrderStatus
- Direction
- domain.ports uses domain.trading.types, so a change to domain.trading.types can break domain.ports, while a change to domain.ports can't break domain.trading.types.
- Position
- Below the diagonal: domain.ports uses a module listed above it, which is the healthy direction.
23→17 domain.trading.portfolio uses domain.trading.types✕
- Connections
- 1 pair of types, where a type in domain.trading.portfolio uses a type in domain.trading.types.
- The types involved
rustrade.domain.trading.portfolio.Portfolio→rustrade.domain.trading.types.Trade
- Direction
- domain.trading.portfolio uses domain.trading.types, so a change to domain.trading.types can break domain.trading.portfolio, while a change to domain.trading.portfolio can't break domain.trading.types.
- Position
- Below the diagonal: domain.trading.portfolio uses a module listed above it, which is the healthy direction.
24→7 interfaces.ui_components.settings_state uses domain.market.strategy_config✕
- Connections
- 1 pair of types, where a type in interfaces.ui_components.settings_state uses a type in domain.market.strategy_config.
- The types involved
rustrade.interfaces.ui_components.settings_state.SettingsPanel→rustrade.domain.market.strategy_config.StrategyMode
- Direction
- interfaces.ui_components.settings_state uses domain.market.strategy_config, so a change to domain.market.strategy_config can break interfaces.ui_components.settings_state, while a change to interfaces.ui_components.settings_state can't break domain.market.strategy_config.
- Position
- Below the diagonal: interfaces.ui_components.settings_state uses a module listed above it, which is the healthy direction.
24→14 interfaces.ui_components.settings_state uses application.agents.analyst_config✕
- Connections
- 1 pair of types, where a type in interfaces.ui_components.settings_state uses a type in application.agents.analyst_config.
- The types involved
rustrade.interfaces.ui_components.settings_state.SettingsPanel→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- interfaces.ui_components.settings_state uses application.agents.analyst_config, so a change to application.agents.analyst_config can break interfaces.ui_components.settings_state, while a change to interfaces.ui_components.settings_state can't break application.agents.analyst_config.
- Position
- Below the diagonal: interfaces.ui_components.settings_state uses a module listed above it, which is the healthy direction.
25→3 application.agents.executor uses application.monitoring.health.connection_health_service✕
- Connections
- 2 pairs of types, where a type in application.agents.executor uses a type in application.monitoring.health.connection_health_service.
- The types involved
rustrade.application.agents.executor.Executor→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthServicerustrade.application.agents.executor.ExecutorDependencies→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthService
- Direction
- application.agents.executor uses application.monitoring.health.connection_health_service, so a change to application.monitoring.health.connection_health_service can break application.agents.executor, while a change to application.agents.executor can't break application.monitoring.health.connection_health_service.
- Position
- Below the diagonal: application.agents.executor uses a module listed above it, which is the healthy direction.
25→15 application.agents.executor uses application.monitoring.health.agent_status✕
- Connections
- 3 pairs of types, where a type in application.agents.executor uses a type in application.monitoring.health.agent_status.
- The types involved
rustrade.application.agents.executor.Executor→rustrade.application.monitoring.health.agent_status.AgentStatusRegistryrustrade.application.agents.executor.Executor→rustrade.application.monitoring.health.agent_status.HealthStatusrustrade.application.agents.executor.ExecutorDependencies→rustrade.application.monitoring.health.agent_status.AgentStatusRegistry
- Direction
- application.agents.executor uses application.monitoring.health.agent_status, so a change to application.monitoring.health.agent_status can break application.agents.executor, while a change to application.agents.executor can't break application.monitoring.health.agent_status.
- Position
- Below the diagonal: application.agents.executor uses a module listed above it, which is the healthy direction.
25→17 application.agents.executor uses domain.trading.types✕
- Connections
- 2 pairs of types, where a type in application.agents.executor uses a type in domain.trading.types.
- The types involved
rustrade.application.agents.executor.Executor→rustrade.domain.trading.types.Candlerustrade.application.agents.executor.Executor→rustrade.domain.trading.types.Order
- Direction
- application.agents.executor uses domain.trading.types, so a change to domain.trading.types can break application.agents.executor, while a change to application.agents.executor can't break domain.trading.types.
- Position
- Below the diagonal: application.agents.executor uses a module listed above it, which is the healthy direction.
25→23 application.agents.executor uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in application.agents.executor uses a type in domain.trading.portfolio.
- The types involved
rustrade.application.agents.executor.Executor→rustrade.domain.trading.portfolio.Portfolio
- Direction
- application.agents.executor uses domain.trading.portfolio, so a change to domain.trading.portfolio can break application.agents.executor, while a change to application.agents.executor can't break domain.trading.portfolio.
- Position
- Below the diagonal: application.agents.executor uses a module listed above it, which is the healthy direction.
26→14 application.agents.signal_processor uses application.agents.analyst_config✕
- Connections
- 1 pair of types, where a type in application.agents.signal_processor uses a type in application.agents.analyst_config.
- The types involved
rustrade.application.agents.signal_processor.SignalProcessor→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- application.agents.signal_processor uses application.agents.analyst_config, so a change to application.agents.analyst_config can break application.agents.signal_processor, while a change to application.agents.signal_processor can't break application.agents.analyst_config.
- Position
- Below the diagonal: application.agents.signal_processor uses a module listed above it, which is the healthy direction.
26→17 application.agents.signal_processor uses domain.trading.types✕
- Connections
- 1 pair of types, where a type in application.agents.signal_processor uses a type in domain.trading.types.
- The types involved
rustrade.application.agents.signal_processor.SignalProcessor→rustrade.domain.trading.types.TradeProposal
- Direction
- application.agents.signal_processor uses domain.trading.types, so a change to domain.trading.types can break application.agents.signal_processor, while a change to application.agents.signal_processor can't break domain.trading.types.
- Position
- Below the diagonal: application.agents.signal_processor uses a module listed above it, which is the healthy direction.
26→20 application.agents.signal_processor uses application.strategies.traits✕
- Connections
- 2 pairs of types, where a type in application.agents.signal_processor uses a type in application.strategies.traits.
- The types involved
rustrade.application.agents.signal_processor.SignalProcessor→rustrade.application.strategies.traits.PositionInforustrade.application.agents.signal_processor.SignalProcessor→rustrade.application.strategies.traits.Signal
- Direction
- application.agents.signal_processor uses application.strategies.traits, so a change to application.strategies.traits can break application.agents.signal_processor, while a change to application.agents.signal_processor can't break application.strategies.traits.
- Position
- Below the diagonal: application.agents.signal_processor uses a module listed above it, which is the healthy direction.
26→21 application.agents.signal_processor uses application.trading.symbol_context✕
- Connections
- 1 pair of types, where a type in application.agents.signal_processor uses a type in application.trading.symbol_context.
- The types involved
rustrade.application.agents.signal_processor.SignalProcessor→rustrade.application.trading.symbol_context.SymbolContext
- Direction
- application.agents.signal_processor uses application.trading.symbol_context, so a change to application.trading.symbol_context can break application.agents.signal_processor, while a change to application.agents.signal_processor can't break application.trading.symbol_context.
- Position
- Below the diagonal: application.agents.signal_processor uses a module listed above it, which is the healthy direction.
27→7 application.optimization.core.walk_forward uses domain.market.strategy_config✕
- Connections
- 1 pair of types, where a type in application.optimization.core.walk_forward uses a type in domain.market.strategy_config.
- The types involved
rustrade.application.optimization.core.walk_forward.GridSearchOptimizer→rustrade.domain.market.strategy_config.StrategyMode
- Direction
- application.optimization.core.walk_forward uses domain.market.strategy_config, so a change to domain.market.strategy_config can break application.optimization.core.walk_forward, while a change to application.optimization.core.walk_forward can't break domain.market.strategy_config.
- Position
- Below the diagonal: application.optimization.core.walk_forward uses a module listed above it, which is the healthy direction.
27→14 application.optimization.core.walk_forward uses application.agents.analyst_config✕
- Connections
- 2 pairs of types, where a type in application.optimization.core.walk_forward uses a type in application.agents.analyst_config.
- The types involved
rustrade.application.optimization.core.walk_forward.GridSearchOptimizer→rustrade.application.agents.analyst_config.AnalystConfigrustrade.application.optimization.core.walk_forward.walk_forward$module→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- application.optimization.core.walk_forward uses application.agents.analyst_config, so a change to application.agents.analyst_config can break application.optimization.core.walk_forward, while a change to application.optimization.core.walk_forward can't break application.agents.analyst_config.
- Position
- Below the diagonal: application.optimization.core.walk_forward uses a module listed above it, which is the healthy direction.
27→18 application.optimization.core.walk_forward uses application.optimization.core.grid✕
- Connections
- 1 pair of types, where a type in application.optimization.core.walk_forward uses a type in application.optimization.core.grid.
- The types involved
rustrade.application.optimization.core.walk_forward.GridSearchOptimizer→rustrade.application.optimization.core.grid.ParameterGrid
- Direction
- application.optimization.core.walk_forward uses application.optimization.core.grid, so a change to application.optimization.core.grid can break application.optimization.core.walk_forward, while a change to application.optimization.core.walk_forward can't break application.optimization.core.grid.
- Position
- Below the diagonal: application.optimization.core.walk_forward uses a module listed above it, which is the healthy direction.
27→19 application.optimization.core.walk_forward uses application.optimization.core.types✕
- Connections
- 5 pairs of types, where a type in application.optimization.core.walk_forward uses a type in application.optimization.core.types.
- The types involved
rustrade.application.optimization.core.walk_forward.GridSearchOptimizer→rustrade.application.optimization.core.types.OptimizationResultrustrade.application.optimization.core.walk_forward.GridSearchOptimizer→rustrade.application.optimization.core.types.PrefetchedBarsrustrade.application.optimization.core.walk_forward.GridSearchOptimizer→rustrade.application.optimization.core.types.SinglePeriodBarsrustrade.application.optimization.core.walk_forward.walk_forward$module→rustrade.application.optimization.core.types.OptimizationResultrustrade.application.optimization.core.walk_forward.walk_forward$module→rustrade.application.optimization.core.types.SinglePeriodBars
- Direction
- application.optimization.core.walk_forward uses application.optimization.core.types, so a change to application.optimization.core.types can break application.optimization.core.walk_forward, while a change to application.optimization.core.walk_forward can't break application.optimization.core.types.
- Position
- Below the diagonal: application.optimization.core.walk_forward uses a module listed above it, which is the healthy direction.
28→2 application.risk_management.core.risk_manager uses application.market_data.spread_cache✕
- Connections
- 1 pair of types, where a type in application.risk_management.core.risk_manager uses a type in application.market_data.spread_cache.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManagerDependencies→rustrade.application.market_data.spread_cache.SpreadCache
- Direction
- application.risk_management.core.risk_manager uses application.market_data.spread_cache, so a change to application.market_data.spread_cache can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break application.market_data.spread_cache.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
28→3 application.risk_management.core.risk_manager uses application.monitoring.health.connection_health_service✕
- Connections
- 2 pairs of types, where a type in application.risk_management.core.risk_manager uses a type in application.monitoring.health.connection_health_service.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManager→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthServicerustrade.application.risk_management.core.risk_manager.RiskManagerDependencies→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthService
- Direction
- application.risk_management.core.risk_manager uses application.monitoring.health.connection_health_service, so a change to application.monitoring.health.connection_health_service can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break application.monitoring.health.connection_health_service.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
28→5 application.risk_management.core.risk_manager uses config✕
- Connections
- 1 pair of types, where a type in application.risk_management.core.risk_manager uses a type in config.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManager→rustrade.config.AssetClass
- Direction
- application.risk_management.core.risk_manager uses config, so a change to config can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break config.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
28→10 application.risk_management.core.risk_manager uses domain.risk.state✕
- Connections
- 1 pair of types, where a type in application.risk_management.core.risk_manager uses a type in domain.risk.state.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManager→rustrade.domain.risk.state.RiskState
- Direction
- application.risk_management.core.risk_manager uses domain.risk.state, so a change to domain.risk.state can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break domain.risk.state.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
28→13 application.risk_management.core.risk_manager uses infrastructure.observability.metrics✕
- Connections
- 2 pairs of types, where a type in application.risk_management.core.risk_manager uses a type in infrastructure.observability.metrics.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManager→rustrade.infrastructure.observability.metrics.Metricsrustrade.application.risk_management.core.risk_manager.RiskManagerDependencies→rustrade.infrastructure.observability.metrics.Metrics
- Direction
- application.risk_management.core.risk_manager uses infrastructure.observability.metrics, so a change to infrastructure.observability.metrics can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break infrastructure.observability.metrics.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
28→15 application.risk_management.core.risk_manager uses application.monitoring.health.agent_status✕
- Connections
- 2 pairs of types, where a type in application.risk_management.core.risk_manager uses a type in application.monitoring.health.agent_status.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManager→rustrade.application.monitoring.health.agent_status.AgentStatusRegistryrustrade.application.risk_management.core.risk_manager.RiskManagerDependencies→rustrade.application.monitoring.health.agent_status.AgentStatusRegistry
- Direction
- application.risk_management.core.risk_manager uses application.monitoring.health.agent_status, so a change to application.monitoring.health.agent_status can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break application.monitoring.health.agent_status.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
28→17 application.risk_management.core.risk_manager uses domain.trading.types✕
- Connections
- 1 pair of types, where a type in application.risk_management.core.risk_manager uses a type in domain.trading.types.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManager→rustrade.domain.trading.types.TradeProposal
- Direction
- application.risk_management.core.risk_manager uses domain.trading.types, so a change to domain.trading.types can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break domain.trading.types.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
28→22 application.risk_management.core.risk_manager uses domain.ports✕
- Connections
- 1 pair of types, where a type in application.risk_management.core.risk_manager uses a type in domain.ports.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManager→rustrade.domain.ports.OrderUpdate
- Direction
- application.risk_management.core.risk_manager uses domain.ports, so a change to domain.ports can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break domain.ports.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
28→23 application.risk_management.core.risk_manager uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in application.risk_management.core.risk_manager uses a type in domain.trading.portfolio.
- The types involved
rustrade.application.risk_management.core.risk_manager.RiskManager→rustrade.domain.trading.portfolio.Portfolio
- Direction
- application.risk_management.core.risk_manager uses domain.trading.portfolio, so a change to domain.trading.portfolio can break application.risk_management.core.risk_manager, while a change to application.risk_management.core.risk_manager can't break domain.trading.portfolio.
- Position
- Below the diagonal: application.risk_management.core.risk_manager uses a module listed above it, which is the healthy direction.
29→7 domain.repositories uses domain.market.strategy_config✕
- Connections
- 1 pair of types, where a type in domain.repositories uses a type in domain.market.strategy_config.
- The types involved
rustrade.domain.repositories.StrategyRepository→rustrade.domain.market.strategy_config.StrategyDefinition
- Direction
- domain.repositories uses domain.market.strategy_config, so a change to domain.market.strategy_config can break domain.repositories, while a change to domain.repositories can't break domain.market.strategy_config.
- Position
- Below the diagonal: domain.repositories uses a module listed above it, which is the healthy direction.
29→10 domain.repositories uses domain.risk.state✕
- Connections
- 1 pair of types, where a type in domain.repositories uses a type in domain.risk.state.
- The types involved
rustrade.domain.repositories.RiskStateRepository→rustrade.domain.risk.state.RiskState
- Direction
- domain.repositories uses domain.risk.state, so a change to domain.risk.state can break domain.repositories, while a change to domain.repositories can't break domain.risk.state.
- Position
- Below the diagonal: domain.repositories uses a module listed above it, which is the healthy direction.
29→17 domain.repositories uses domain.trading.types✕
- Connections
- 3 pairs of types, where a type in domain.repositories uses a type in domain.trading.types.
- The types involved
rustrade.domain.repositories.CandleRepository→rustrade.domain.trading.types.Candlerustrade.domain.repositories.TradeRepository→rustrade.domain.trading.types.Orderrustrade.domain.repositories.TradeRepository→rustrade.domain.trading.types.OrderStatus
- Direction
- domain.repositories uses domain.trading.types, so a change to domain.trading.types can break domain.repositories, while a change to domain.repositories can't break domain.trading.types.
- Position
- Below the diagonal: domain.repositories uses a module listed above it, which is the healthy direction.
29→23 domain.repositories uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in domain.repositories uses a type in domain.trading.portfolio.
- The types involved
rustrade.domain.repositories.PortfolioRepository→rustrade.domain.trading.portfolio.Portfolio
- Direction
- domain.repositories uses domain.trading.portfolio, so a change to domain.trading.portfolio can break domain.repositories, while a change to domain.repositories can't break domain.trading.portfolio.
- Position
- Below the diagonal: domain.repositories uses a module listed above it, which is the healthy direction.
30→4 domain.risk.filters.validator_trait uses application.monitoring.strategy.strategy_validator✕
- Connections
- 1 pair of types, where a type in domain.risk.filters.validator_trait uses a type in application.monitoring.strategy.strategy_validator.
- The types involved
rustrade.domain.risk.filters.validator_trait.RiskValidator→rustrade.application.monitoring.strategy.strategy_validator.ValidationResult
- Direction
- domain.risk.filters.validator_trait uses application.monitoring.strategy.strategy_validator, so a change to application.monitoring.strategy.strategy_validator can break domain.risk.filters.validator_trait, while a change to domain.risk.filters.validator_trait can't break application.monitoring.strategy.strategy_validator.
- Position
- Below the diagonal: domain.risk.filters.validator_trait uses a module listed above it, which is the healthy direction.
30→10 domain.risk.filters.validator_trait uses domain.risk.state✕
- Connections
- 1 pair of types, where a type in domain.risk.filters.validator_trait uses a type in domain.risk.state.
- The types involved
rustrade.domain.risk.filters.validator_trait.ValidationContext→rustrade.domain.risk.state.RiskState
- Direction
- domain.risk.filters.validator_trait uses domain.risk.state, so a change to domain.risk.state can break domain.risk.filters.validator_trait, while a change to domain.risk.filters.validator_trait can't break domain.risk.state.
- Position
- Below the diagonal: domain.risk.filters.validator_trait uses a module listed above it, which is the healthy direction.
30→17 domain.risk.filters.validator_trait uses domain.trading.types✕
- Connections
- 1 pair of types, where a type in domain.risk.filters.validator_trait uses a type in domain.trading.types.
- The types involved
rustrade.domain.risk.filters.validator_trait.ValidationContext→rustrade.domain.trading.types.TradeProposal
- Direction
- domain.risk.filters.validator_trait uses domain.trading.types, so a change to domain.trading.types can break domain.risk.filters.validator_trait, while a change to domain.risk.filters.validator_trait can't break domain.trading.types.
- Position
- Below the diagonal: domain.risk.filters.validator_trait uses a module listed above it, which is the healthy direction.
30→23 domain.risk.filters.validator_trait uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in domain.risk.filters.validator_trait uses a type in domain.trading.portfolio.
- The types involved
rustrade.domain.risk.filters.validator_trait.ValidationContext→rustrade.domain.trading.portfolio.Portfolio
- Direction
- domain.risk.filters.validator_trait uses domain.trading.portfolio, so a change to domain.trading.portfolio can break domain.risk.filters.validator_trait, while a change to domain.risk.filters.validator_trait can't break domain.trading.portfolio.
- Position
- Below the diagonal: domain.risk.filters.validator_trait uses a module listed above it, which is the healthy direction.
31→14 application.agents.news_handler uses application.agents.analyst_config✕
- Connections
- 1 pair of types, where a type in application.agents.news_handler uses a type in application.agents.analyst_config.
- The types involved
rustrade.application.agents.news_handler.NewsHandler→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- application.agents.news_handler uses application.agents.analyst_config, so a change to application.agents.analyst_config can break application.agents.news_handler, while a change to application.agents.news_handler can't break application.agents.analyst_config.
- Position
- Below the diagonal: application.agents.news_handler uses a module listed above it, which is the healthy direction.
31→17 application.agents.news_handler uses domain.trading.types✕
- Connections
- 1 pair of types, where a type in application.agents.news_handler uses a type in domain.trading.types.
- The types involved
rustrade.application.agents.news_handler.news_handler$module→rustrade.domain.trading.types.TradeProposal
- Direction
- application.agents.news_handler uses domain.trading.types, so a change to domain.trading.types can break application.agents.news_handler, while a change to application.agents.news_handler can't break domain.trading.types.
- Position
- Below the diagonal: application.agents.news_handler uses a module listed above it, which is the healthy direction.
31→21 application.agents.news_handler uses application.trading.symbol_context✕
- Connections
- 2 pairs of types, where a type in application.agents.news_handler uses a type in application.trading.symbol_context.
- The types involved
rustrade.application.agents.news_handler.NewsHandler→rustrade.application.trading.symbol_context.SymbolContextrustrade.application.agents.news_handler.news_handler$module→rustrade.application.trading.symbol_context.SymbolContext
- Direction
- application.agents.news_handler uses application.trading.symbol_context, so a change to application.trading.symbol_context can break application.agents.news_handler, while a change to application.agents.news_handler can't break application.trading.symbol_context.
- Position
- Below the diagonal: application.agents.news_handler uses a module listed above it, which is the healthy direction.
31→26 application.agents.news_handler uses application.agents.signal_processor✕
- Connections
- 1 pair of types, where a type in application.agents.news_handler uses a type in application.agents.signal_processor.
- The types involved
rustrade.application.agents.news_handler.NewsHandler→rustrade.application.agents.signal_processor.SignalProcessor
- Direction
- application.agents.news_handler uses application.agents.signal_processor, so a change to application.agents.signal_processor can break application.agents.news_handler, while a change to application.agents.news_handler can't break application.agents.signal_processor.
- Position
- Below the diagonal: application.agents.news_handler uses a module listed above it, which is the healthy direction.
32→6 application.agents.trade_evaluator uses domain.market.market_regime✕
- Connections
- 1 pair of types, where a type in application.agents.trade_evaluator uses a type in domain.market.market_regime.
- The types involved
rustrade.application.agents.trade_evaluator.EvaluationInput→rustrade.domain.market.market_regime.MarketRegime
- Direction
- application.agents.trade_evaluator uses domain.market.market_regime, so a change to domain.market.market_regime can break application.agents.trade_evaluator, while a change to application.agents.trade_evaluator can't break domain.market.market_regime.
- Position
- Below the diagonal: application.agents.trade_evaluator uses a module listed above it, which is the healthy direction.
32→17 application.agents.trade_evaluator uses domain.trading.types✕
- Connections
- 2 pairs of types, where a type in application.agents.trade_evaluator uses a type in domain.trading.types.
- The types involved
rustrade.application.agents.trade_evaluator.EvaluationInput→rustrade.domain.trading.types.OrderSiderustrade.application.agents.trade_evaluator.TradeEvaluator→rustrade.domain.trading.types.TradeProposal
- Direction
- application.agents.trade_evaluator uses domain.trading.types, so a change to domain.trading.types can break application.agents.trade_evaluator, while a change to application.agents.trade_evaluator can't break domain.trading.types.
- Position
- Below the diagonal: application.agents.trade_evaluator uses a module listed above it, which is the healthy direction.
32→20 application.agents.trade_evaluator uses application.strategies.traits✕
- Connections
- 1 pair of types, where a type in application.agents.trade_evaluator uses a type in application.strategies.traits.
- The types involved
rustrade.application.agents.trade_evaluator.EvaluationInput→rustrade.application.strategies.traits.Signal
- Direction
- application.agents.trade_evaluator uses application.strategies.traits, so a change to application.strategies.traits can break application.agents.trade_evaluator, while a change to application.agents.trade_evaluator can't break application.strategies.traits.
- Position
- Below the diagonal: application.agents.trade_evaluator uses a module listed above it, which is the healthy direction.
32→21 application.agents.trade_evaluator uses application.trading.symbol_context✕
- Connections
- 1 pair of types, where a type in application.agents.trade_evaluator uses a type in application.trading.symbol_context.
- The types involved
rustrade.application.agents.trade_evaluator.TradeEvaluator→rustrade.application.trading.symbol_context.SymbolContext
- Direction
- application.agents.trade_evaluator uses application.trading.symbol_context, so a change to application.trading.symbol_context can break application.agents.trade_evaluator, while a change to application.agents.trade_evaluator can't break application.trading.symbol_context.
- Position
- Below the diagonal: application.agents.trade_evaluator uses a module listed above it, which is the healthy direction.
32→26 application.agents.trade_evaluator uses application.agents.signal_processor✕
- Connections
- 1 pair of types, where a type in application.agents.trade_evaluator uses a type in application.agents.signal_processor.
- The types involved
rustrade.application.agents.trade_evaluator.TradeEvaluator→rustrade.application.agents.signal_processor.SignalProcessor
- Direction
- application.agents.trade_evaluator uses application.agents.signal_processor, so a change to application.agents.signal_processor can break application.agents.trade_evaluator, while a change to application.agents.trade_evaluator can't break application.agents.signal_processor.
- Position
- Below the diagonal: application.agents.trade_evaluator uses a module listed above it, which is the healthy direction.
33→6 application.optimization.adaptive_optimization_service uses domain.market.market_regime✕
- Connections
- 1 pair of types, where a type in application.optimization.adaptive_optimization_service uses a type in domain.market.market_regime.
- The types involved
rustrade.application.optimization.adaptive_optimization_service.AdaptiveOptimizationService→rustrade.domain.market.market_regime.MarketRegimeDetector
- Direction
- application.optimization.adaptive_optimization_service uses domain.market.market_regime, so a change to domain.market.market_regime can break application.optimization.adaptive_optimization_service, while a change to application.optimization.adaptive_optimization_service can't break domain.market.market_regime.
- Position
- Below the diagonal: application.optimization.adaptive_optimization_service uses a module listed above it, which is the healthy direction.
33→27 application.optimization.adaptive_optimization_service uses application.optimization.core.walk_forward✕
- Connections
- 1 pair of types, where a type in application.optimization.adaptive_optimization_service uses a type in application.optimization.core.walk_forward.
- The types involved
rustrade.application.optimization.adaptive_optimization_service.AdaptiveOptimizationService→rustrade.application.optimization.core.walk_forward.GridSearchOptimizer
- Direction
- application.optimization.adaptive_optimization_service uses application.optimization.core.walk_forward, so a change to application.optimization.core.walk_forward can break application.optimization.adaptive_optimization_service, while a change to application.optimization.adaptive_optimization_service can't break application.optimization.core.walk_forward.
- Position
- Below the diagonal: application.optimization.adaptive_optimization_service uses a module listed above it, which is the healthy direction.
34→6 application.agents.candle_pipeline uses domain.market.market_regime✕
- Connections
- 1 pair of types, where a type in application.agents.candle_pipeline uses a type in domain.market.market_regime.
- The types involved
rustrade.application.agents.candle_pipeline.CandlePipeline→rustrade.domain.market.market_regime.MarketRegime
- Direction
- application.agents.candle_pipeline uses domain.market.market_regime, so a change to domain.market.market_regime can break application.agents.candle_pipeline, while a change to application.agents.candle_pipeline can't break domain.market.market_regime.
- Position
- Below the diagonal: application.agents.candle_pipeline uses a module listed above it, which is the healthy direction.
34→17 application.agents.candle_pipeline uses domain.trading.types✕
- Connections
- 2 pairs of types, where a type in application.agents.candle_pipeline uses a type in domain.trading.types.
- The types involved
rustrade.application.agents.candle_pipeline.CandlePipeline→rustrade.domain.trading.types.TradeProposalrustrade.application.agents.candle_pipeline.PipelineContext→rustrade.domain.trading.types.Candle
- Direction
- application.agents.candle_pipeline uses domain.trading.types, so a change to domain.trading.types can break application.agents.candle_pipeline, while a change to application.agents.candle_pipeline can't break domain.trading.types.
- Position
- Below the diagonal: application.agents.candle_pipeline uses a module listed above it, which is the healthy direction.
34→20 application.agents.candle_pipeline uses application.strategies.traits✕
- Connections
- 1 pair of types, where a type in application.agents.candle_pipeline uses a type in application.strategies.traits.
- The types involved
rustrade.application.agents.candle_pipeline.CandlePipeline→rustrade.application.strategies.traits.Signal
- Direction
- application.agents.candle_pipeline uses application.strategies.traits, so a change to application.strategies.traits can break application.agents.candle_pipeline, while a change to application.agents.candle_pipeline can't break application.strategies.traits.
- Position
- Below the diagonal: application.agents.candle_pipeline uses a module listed above it, which is the healthy direction.
34→21 application.agents.candle_pipeline uses application.trading.symbol_context✕
- Connections
- 1 pair of types, where a type in application.agents.candle_pipeline uses a type in application.trading.symbol_context.
- The types involved
rustrade.application.agents.candle_pipeline.PipelineContext→rustrade.application.trading.symbol_context.SymbolContext
- Direction
- application.agents.candle_pipeline uses application.trading.symbol_context, so a change to application.trading.symbol_context can break application.agents.candle_pipeline, while a change to application.agents.candle_pipeline can't break application.trading.symbol_context.
- Position
- Below the diagonal: application.agents.candle_pipeline uses a module listed above it, which is the healthy direction.
34→23 application.agents.candle_pipeline uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in application.agents.candle_pipeline uses a type in domain.trading.portfolio.
- The types involved
rustrade.application.agents.candle_pipeline.PipelineContext→rustrade.domain.trading.portfolio.Portfolio
- Direction
- application.agents.candle_pipeline uses domain.trading.portfolio, so a change to domain.trading.portfolio can break application.agents.candle_pipeline, while a change to application.agents.candle_pipeline can't break domain.trading.portfolio.
- Position
- Below the diagonal: application.agents.candle_pipeline uses a module listed above it, which is the healthy direction.
34→32 application.agents.candle_pipeline uses application.agents.trade_evaluator✕
- Connections
- 1 pair of types, where a type in application.agents.candle_pipeline uses a type in application.agents.trade_evaluator.
- The types involved
rustrade.application.agents.candle_pipeline.CandlePipeline→rustrade.application.agents.trade_evaluator.TradeEvaluator
- Direction
- application.agents.candle_pipeline uses application.agents.trade_evaluator, so a change to application.agents.trade_evaluator can break application.agents.candle_pipeline, while a change to application.agents.candle_pipeline can't break application.agents.trade_evaluator.
- Position
- Below the diagonal: application.agents.candle_pipeline uses a module listed above it, which is the healthy direction.
35→1 application.bootstrap.services uses application.bootstrap.persistence✕
- Connections
- 1 pair of types, where a type in application.bootstrap.services uses a type in application.bootstrap.persistence.
- The types involved
rustrade.application.bootstrap.services.ServicesBootstrap→rustrade.application.bootstrap.persistence.PersistenceHandle
- Direction
- application.bootstrap.services uses application.bootstrap.persistence, so a change to application.bootstrap.persistence can break application.bootstrap.services, while a change to application.bootstrap.services can't break application.bootstrap.persistence.
- Position
- Below the diagonal: application.bootstrap.services uses a module listed above it, which is the healthy direction.
35→2 application.bootstrap.services uses application.market_data.spread_cache✕
- Connections
- 1 pair of types, where a type in application.bootstrap.services uses a type in application.market_data.spread_cache.
- The types involved
rustrade.application.bootstrap.services.ServicesHandle→rustrade.application.market_data.spread_cache.SpreadCache
- Direction
- application.bootstrap.services uses application.market_data.spread_cache, so a change to application.market_data.spread_cache can break application.bootstrap.services, while a change to application.bootstrap.services can't break application.market_data.spread_cache.
- Position
- Below the diagonal: application.bootstrap.services uses a module listed above it, which is the healthy direction.
35→3 application.bootstrap.services uses application.monitoring.health.connection_health_service✕
- Connections
- 1 pair of types, where a type in application.bootstrap.services uses a type in application.monitoring.health.connection_health_service.
- The types involved
rustrade.application.bootstrap.services.ServicesHandle→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthService
- Direction
- application.bootstrap.services uses application.monitoring.health.connection_health_service, so a change to application.monitoring.health.connection_health_service can break application.bootstrap.services, while a change to application.bootstrap.services can't break application.monitoring.health.connection_health_service.
- Position
- Below the diagonal: application.bootstrap.services uses a module listed above it, which is the healthy direction.
35→5 application.bootstrap.services uses config✕
- Connections
- 1 pair of types, where a type in application.bootstrap.services uses a type in config.
- The types involved
rustrade.application.bootstrap.services.ServicesBootstrap→rustrade.config.Config
- Direction
- application.bootstrap.services uses config, so a change to config can break application.bootstrap.services, while a change to application.bootstrap.services can't break config.
- Position
- Below the diagonal: application.bootstrap.services uses a module listed above it, which is the healthy direction.
35→13 application.bootstrap.services uses infrastructure.observability.metrics✕
- Connections
- 2 pairs of types, where a type in application.bootstrap.services uses a type in infrastructure.observability.metrics.
- The types involved
rustrade.application.bootstrap.services.ServicesBootstrap→rustrade.infrastructure.observability.metrics.Metricsrustrade.application.bootstrap.services.ServicesHandle→rustrade.infrastructure.observability.metrics.Metrics
- Direction
- application.bootstrap.services uses infrastructure.observability.metrics, so a change to infrastructure.observability.metrics can break application.bootstrap.services, while a change to application.bootstrap.services can't break infrastructure.observability.metrics.
- Position
- Below the diagonal: application.bootstrap.services uses a module listed above it, which is the healthy direction.
35→23 application.bootstrap.services uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in application.bootstrap.services uses a type in domain.trading.portfolio.
- The types involved
rustrade.application.bootstrap.services.ServicesBootstrap→rustrade.domain.trading.portfolio.Portfolio
- Direction
- application.bootstrap.services uses domain.trading.portfolio, so a change to domain.trading.portfolio can break application.bootstrap.services, while a change to application.bootstrap.services can't break domain.trading.portfolio.
- Position
- Below the diagonal: application.bootstrap.services uses a module listed above it, which is the healthy direction.
35→33 application.bootstrap.services uses application.optimization.adaptive_optimization_service✕
- Connections
- 1 pair of types, where a type in application.bootstrap.services uses a type in application.optimization.adaptive_optimization_service.
- The types involved
rustrade.application.bootstrap.services.ServicesHandle→rustrade.application.optimization.adaptive_optimization_service.AdaptiveOptimizationService
- Direction
- application.bootstrap.services uses application.optimization.adaptive_optimization_service, so a change to application.optimization.adaptive_optimization_service can break application.bootstrap.services, while a change to application.bootstrap.services can't break application.optimization.adaptive_optimization_service.
- Position
- Below the diagonal: application.bootstrap.services uses a module listed above it, which is the healthy direction.
36→2 application.agents.analyst uses application.market_data.spread_cache✕
- Connections
- 1 pair of types, where a type in application.agents.analyst uses a type in application.market_data.spread_cache.
- The types involved
rustrade.application.agents.analyst.AnalystDependencies→rustrade.application.market_data.spread_cache.SpreadCache
- Direction
- application.agents.analyst uses application.market_data.spread_cache, so a change to application.market_data.spread_cache can break application.agents.analyst, while a change to application.agents.analyst can't break application.market_data.spread_cache.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
36→3 application.agents.analyst uses application.monitoring.health.connection_health_service✕
- Connections
- 2 pairs of types, where a type in application.agents.analyst uses a type in application.monitoring.health.connection_health_service.
- The types involved
rustrade.application.agents.analyst.Analyst→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthServicerustrade.application.agents.analyst.AnalystDependencies→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthService
- Direction
- application.agents.analyst uses application.monitoring.health.connection_health_service, so a change to application.monitoring.health.connection_health_service can break application.agents.analyst, while a change to application.agents.analyst can't break application.monitoring.health.connection_health_service.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
36→8 application.agents.analyst uses domain.market.timeframe✕
- Connections
- 1 pair of types, where a type in application.agents.analyst uses a type in domain.market.timeframe.
- The types involved
rustrade.application.agents.analyst.Analyst→rustrade.domain.market.timeframe.Timeframe
- Direction
- application.agents.analyst uses domain.market.timeframe, so a change to domain.market.timeframe can break application.agents.analyst, while a change to application.agents.analyst can't break domain.market.timeframe.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
36→14 application.agents.analyst uses application.agents.analyst_config✕
- Connections
- 1 pair of types, where a type in application.agents.analyst uses a type in application.agents.analyst_config.
- The types involved
rustrade.application.agents.analyst.Analyst→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- application.agents.analyst uses application.agents.analyst_config, so a change to application.agents.analyst_config can break application.agents.analyst, while a change to application.agents.analyst can't break application.agents.analyst_config.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
36→15 application.agents.analyst uses application.monitoring.health.agent_status✕
- Connections
- 2 pairs of types, where a type in application.agents.analyst uses a type in application.monitoring.health.agent_status.
- The types involved
rustrade.application.agents.analyst.Analyst→rustrade.application.monitoring.health.agent_status.AgentStatusRegistryrustrade.application.agents.analyst.AnalystDependencies→rustrade.application.monitoring.health.agent_status.AgentStatusRegistry
- Direction
- application.agents.analyst uses application.monitoring.health.agent_status, so a change to application.monitoring.health.agent_status can break application.agents.analyst, while a change to application.agents.analyst can't break application.monitoring.health.agent_status.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
36→17 application.agents.analyst uses domain.trading.types✕
- Connections
- 1 pair of types, where a type in application.agents.analyst uses a type in domain.trading.types.
- The types involved
rustrade.application.agents.analyst.Analyst→rustrade.domain.trading.types.Candle
- Direction
- application.agents.analyst uses domain.trading.types, so a change to domain.trading.types can break application.agents.analyst, while a change to application.agents.analyst can't break domain.trading.types.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
36→21 application.agents.analyst uses application.trading.symbol_context✕
- Connections
- 1 pair of types, where a type in application.agents.analyst uses a type in application.trading.symbol_context.
- The types involved
rustrade.application.agents.analyst.Analyst→rustrade.application.trading.symbol_context.SymbolContext
- Direction
- application.agents.analyst uses application.trading.symbol_context, so a change to application.trading.symbol_context can break application.agents.analyst, while a change to application.agents.analyst can't break application.trading.symbol_context.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
36→31 application.agents.analyst uses application.agents.news_handler✕
- Connections
- 1 pair of types, where a type in application.agents.analyst uses a type in application.agents.news_handler.
- The types involved
rustrade.application.agents.analyst.Analyst→rustrade.application.agents.news_handler.NewsHandler
- Direction
- application.agents.analyst uses application.agents.news_handler, so a change to application.agents.news_handler can break application.agents.analyst, while a change to application.agents.analyst can't break application.agents.news_handler.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
36→34 application.agents.analyst uses application.agents.candle_pipeline✕
- Connections
- 1 pair of types, where a type in application.agents.analyst uses a type in application.agents.candle_pipeline.
- The types involved
rustrade.application.agents.analyst.Analyst→rustrade.application.agents.candle_pipeline.CandlePipeline
- Direction
- application.agents.analyst uses application.agents.candle_pipeline, so a change to application.agents.candle_pipeline can break application.agents.analyst, while a change to application.agents.analyst can't break application.agents.candle_pipeline.
- Position
- Below the diagonal: application.agents.analyst uses a module listed above it, which is the healthy direction.
37→1 application.bootstrap.agents uses application.bootstrap.persistence✕
- Connections
- 1 pair of types, where a type in application.bootstrap.agents uses a type in application.bootstrap.persistence.
- The types involved
rustrade.application.bootstrap.agents.AgentsBootstrap→rustrade.application.bootstrap.persistence.PersistenceHandle
- Direction
- application.bootstrap.agents uses application.bootstrap.persistence, so a change to application.bootstrap.persistence can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break application.bootstrap.persistence.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
37→3 application.bootstrap.agents uses application.monitoring.health.connection_health_service✕
- Connections
- 1 pair of types, where a type in application.bootstrap.agents uses a type in application.monitoring.health.connection_health_service.
- The types involved
rustrade.application.bootstrap.agents.AgentsBootstrap→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthService
- Direction
- application.bootstrap.agents uses application.monitoring.health.connection_health_service, so a change to application.monitoring.health.connection_health_service can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break application.monitoring.health.connection_health_service.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
37→5 application.bootstrap.agents uses config✕
- Connections
- 2 pairs of types, where a type in application.bootstrap.agents uses a type in config.
- The types involved
rustrade.application.bootstrap.agents.AgentsBootstrap→rustrade.config.Configrustrade.application.bootstrap.agents.agents$module→rustrade.config.Config
- Direction
- application.bootstrap.agents uses config, so a change to config can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break config.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
37→13 application.bootstrap.agents uses infrastructure.observability.metrics✕
- Connections
- 1 pair of types, where a type in application.bootstrap.agents uses a type in infrastructure.observability.metrics.
- The types involved
rustrade.application.bootstrap.agents.AgentsBootstrap→rustrade.infrastructure.observability.metrics.Metrics
- Direction
- application.bootstrap.agents uses infrastructure.observability.metrics, so a change to infrastructure.observability.metrics can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break infrastructure.observability.metrics.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
37→14 application.bootstrap.agents uses application.agents.analyst_config✕
- Connections
- 1 pair of types, where a type in application.bootstrap.agents uses a type in application.agents.analyst_config.
- The types involved
rustrade.application.bootstrap.agents.agents$module→rustrade.application.agents.analyst_config.AnalystConfig
- Direction
- application.bootstrap.agents uses application.agents.analyst_config, so a change to application.agents.analyst_config can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break application.agents.analyst_config.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
37→15 application.bootstrap.agents uses application.monitoring.health.agent_status✕
- Connections
- 2 pairs of types, where a type in application.bootstrap.agents uses a type in application.monitoring.health.agent_status.
- The types involved
rustrade.application.bootstrap.agents.AgentsBootstrap→rustrade.application.monitoring.health.agent_status.AgentStatusRegistryrustrade.application.bootstrap.agents.agents$module→rustrade.application.monitoring.health.agent_status.AgentStatusRegistry
- Direction
- application.bootstrap.agents uses application.monitoring.health.agent_status, so a change to application.monitoring.health.agent_status can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break application.monitoring.health.agent_status.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
37→23 application.bootstrap.agents uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in application.bootstrap.agents uses a type in domain.trading.portfolio.
- The types involved
rustrade.application.bootstrap.agents.AgentsBootstrap→rustrade.domain.trading.portfolio.Portfolio
- Direction
- application.bootstrap.agents uses domain.trading.portfolio, so a change to domain.trading.portfolio can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break domain.trading.portfolio.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
37→33 application.bootstrap.agents uses application.optimization.adaptive_optimization_service✕
- Connections
- 1 pair of types, where a type in application.bootstrap.agents uses a type in application.optimization.adaptive_optimization_service.
- The types involved
rustrade.application.bootstrap.agents.agents$module→rustrade.application.optimization.adaptive_optimization_service.AdaptiveOptimizationService
- Direction
- application.bootstrap.agents uses application.optimization.adaptive_optimization_service, so a change to application.optimization.adaptive_optimization_service can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break application.optimization.adaptive_optimization_service.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
37→35 application.bootstrap.agents uses application.bootstrap.services✕
- Connections
- 1 pair of types, where a type in application.bootstrap.agents uses a type in application.bootstrap.services.
- The types involved
rustrade.application.bootstrap.agents.AgentsBootstrap→rustrade.application.bootstrap.services.ServicesHandle
- Direction
- application.bootstrap.agents uses application.bootstrap.services, so a change to application.bootstrap.services can break application.bootstrap.agents, while a change to application.bootstrap.agents can't break application.bootstrap.services.
- Position
- Below the diagonal: application.bootstrap.agents uses a module listed above it, which is the healthy direction.
38→1 application.system uses application.bootstrap.persistence✕
- Connections
- 1 pair of types, where a type in application.system uses a type in application.bootstrap.persistence.
- The types involved
rustrade.application.system.Application→rustrade.application.bootstrap.persistence.PersistenceHandle
- Direction
- application.system uses application.bootstrap.persistence, so a change to application.bootstrap.persistence can break application.system, while a change to application.system can't break application.bootstrap.persistence.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→2 application.system uses application.market_data.spread_cache✕
- Connections
- 1 pair of types, where a type in application.system uses a type in application.market_data.spread_cache.
- The types involved
rustrade.application.system.Application→rustrade.application.market_data.spread_cache.SpreadCache
- Direction
- application.system uses application.market_data.spread_cache, so a change to application.market_data.spread_cache can break application.system, while a change to application.system can't break application.market_data.spread_cache.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→3 application.system uses application.monitoring.health.connection_health_service✕
- Connections
- 2 pairs of types, where a type in application.system uses a type in application.monitoring.health.connection_health_service.
- The types involved
rustrade.application.system.Application→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthServicerustrade.application.system.SystemHandle→rustrade.application.monitoring.health.connection_health_service.ConnectionHealthService
- Direction
- application.system uses application.monitoring.health.connection_health_service, so a change to application.monitoring.health.connection_health_service can break application.system, while a change to application.system can't break application.monitoring.health.connection_health_service.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→5 application.system uses config✕
- Connections
- 1 pair of types, where a type in application.system uses a type in config.
- The types involved
rustrade.application.system.Application→rustrade.config.Config
- Direction
- application.system uses config, so a change to config can break application.system, while a change to application.system can't break config.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→7 application.system uses domain.market.strategy_config✕
- Connections
- 1 pair of types, where a type in application.system uses a type in domain.market.strategy_config.
- The types involved
rustrade.application.system.SystemHandle→rustrade.domain.market.strategy_config.StrategyMode
- Direction
- application.system uses domain.market.strategy_config, so a change to domain.market.strategy_config can break application.system, while a change to application.system can't break domain.market.strategy_config.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→9 application.system uses domain.risk.risk_appetite✕
- Connections
- 1 pair of types, where a type in application.system uses a type in domain.risk.risk_appetite.
- The types involved
rustrade.application.system.SystemHandle→rustrade.domain.risk.risk_appetite.RiskAppetite
- Direction
- application.system uses domain.risk.risk_appetite, so a change to domain.risk.risk_appetite can break application.system, while a change to application.system can't break domain.risk.risk_appetite.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→13 application.system uses infrastructure.observability.metrics✕
- Connections
- 2 pairs of types, where a type in application.system uses a type in infrastructure.observability.metrics.
- The types involved
rustrade.application.system.Application→rustrade.infrastructure.observability.metrics.Metricsrustrade.application.system.SystemHandle→rustrade.infrastructure.observability.metrics.Metrics
- Direction
- application.system uses infrastructure.observability.metrics, so a change to infrastructure.observability.metrics can break application.system, while a change to application.system can't break infrastructure.observability.metrics.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→15 application.system uses application.monitoring.health.agent_status✕
- Connections
- 2 pairs of types, where a type in application.system uses a type in application.monitoring.health.agent_status.
- The types involved
rustrade.application.system.Application→rustrade.application.monitoring.health.agent_status.AgentStatusRegistryrustrade.application.system.SystemHandle→rustrade.application.monitoring.health.agent_status.AgentStatusRegistry
- Direction
- application.system uses application.monitoring.health.agent_status, so a change to application.monitoring.health.agent_status can break application.system, while a change to application.system can't break application.monitoring.health.agent_status.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→23 application.system uses domain.trading.portfolio✕
- Connections
- 2 pairs of types, where a type in application.system uses a type in domain.trading.portfolio.
- The types involved
rustrade.application.system.Application→rustrade.domain.trading.portfolio.Portfoliorustrade.application.system.SystemHandle→rustrade.domain.trading.portfolio.Portfolio
- Direction
- application.system uses domain.trading.portfolio, so a change to domain.trading.portfolio can break application.system, while a change to application.system can't break domain.trading.portfolio.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→33 application.system uses application.optimization.adaptive_optimization_service✕
- Connections
- 1 pair of types, where a type in application.system uses a type in application.optimization.adaptive_optimization_service.
- The types involved
rustrade.application.system.Application→rustrade.application.optimization.adaptive_optimization_service.AdaptiveOptimizationService
- Direction
- application.system uses application.optimization.adaptive_optimization_service, so a change to application.optimization.adaptive_optimization_service can break application.system, while a change to application.system can't break application.optimization.adaptive_optimization_service.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
38→35 application.system uses application.bootstrap.services✕
- Connections
- 1 pair of types, where a type in application.system uses a type in application.bootstrap.services.
- The types involved
rustrade.application.system.Application→rustrade.application.bootstrap.services.ServicesHandle
- Direction
- application.system uses application.bootstrap.services, so a change to application.bootstrap.services can break application.system, while a change to application.system can't break application.bootstrap.services.
- Position
- Below the diagonal: application.system uses a module listed above it, which is the healthy direction.
39→7 application.client uses domain.market.strategy_config✕
- Connections
- 1 pair of types, where a type in application.client uses a type in domain.market.strategy_config.
- The types involved
rustrade.application.client.SystemClient→rustrade.domain.market.strategy_config.StrategyMode
- Direction
- application.client uses domain.market.strategy_config, so a change to domain.market.strategy_config can break application.client, while a change to application.client can't break domain.market.strategy_config.
- Position
- Below the diagonal: application.client uses a module listed above it, which is the healthy direction.
39→9 application.client uses domain.risk.risk_appetite✕
- Connections
- 1 pair of types, where a type in application.client uses a type in domain.risk.risk_appetite.
- The types involved
rustrade.application.client.SystemClient→rustrade.domain.risk.risk_appetite.RiskAppetite
- Direction
- application.client uses domain.risk.risk_appetite, so a change to domain.risk.risk_appetite can break application.client, while a change to application.client can't break domain.risk.risk_appetite.
- Position
- Below the diagonal: application.client uses a module listed above it, which is the healthy direction.
39→15 application.client uses application.monitoring.health.agent_status✕
- Connections
- 1 pair of types, where a type in application.client uses a type in application.monitoring.health.agent_status.
- The types involved
rustrade.application.client.SystemClient→rustrade.application.monitoring.health.agent_status.AgentStatusRegistry
- Direction
- application.client uses application.monitoring.health.agent_status, so a change to application.monitoring.health.agent_status can break application.client, while a change to application.client can't break application.monitoring.health.agent_status.
- Position
- Below the diagonal: application.client uses a module listed above it, which is the healthy direction.
39→17 application.client uses domain.trading.types✕
- Connections
- 1 pair of types, where a type in application.client uses a type in domain.trading.types.
- The types involved
rustrade.application.client.SystemClient→rustrade.domain.trading.types.TradeProposal
- Direction
- application.client uses domain.trading.types, so a change to domain.trading.types can break application.client, while a change to application.client can't break domain.trading.types.
- Position
- Below the diagonal: application.client uses a module listed above it, which is the healthy direction.
39→23 application.client uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in application.client uses a type in domain.trading.portfolio.
- The types involved
rustrade.application.client.SystemClient→rustrade.domain.trading.portfolio.Portfolio
- Direction
- application.client uses domain.trading.portfolio, so a change to domain.trading.portfolio can break application.client, while a change to application.client can't break domain.trading.portfolio.
- Position
- Below the diagonal: application.client uses a module listed above it, which is the healthy direction.
39→36 application.client uses application.agents.analyst✕
- Connections
- 1 pair of types, where a type in application.client uses a type in application.agents.analyst.
- The types involved
rustrade.application.client.SystemClient→rustrade.application.agents.analyst.AnalystCommand
- Direction
- application.client uses application.agents.analyst, so a change to application.agents.analyst can break application.client, while a change to application.client can't break application.agents.analyst.
- Position
- Below the diagonal: application.client uses a module listed above it, which is the healthy direction.
39→38 application.client uses application.system✕
- Connections
- 1 pair of types, where a type in application.client uses a type in application.system.
- The types involved
rustrade.application.client.SystemClient→rustrade.application.system.SystemHandle
- Direction
- application.client uses application.system, so a change to application.system can break application.client, while a change to application.client can't break application.system.
- Position
- Below the diagonal: application.client uses a module listed above it, which is the healthy direction.
40→7 application.agents.user_agent uses domain.market.strategy_config✕
- Connections
- 2 pairs of types, where a type in application.agents.user_agent uses a type in domain.market.strategy_config.
- The types involved
rustrade.application.agents.user_agent.UserAgent→rustrade.domain.market.strategy_config.StrategyModerustrade.application.agents.user_agent.UserAgentConfig→rustrade.domain.market.strategy_config.StrategyMode
- Direction
- application.agents.user_agent uses domain.market.strategy_config, so a change to domain.market.strategy_config can break application.agents.user_agent, while a change to application.agents.user_agent can't break domain.market.strategy_config.
- Position
- Below the diagonal: application.agents.user_agent uses a module listed above it, which is the healthy direction.
40→9 application.agents.user_agent uses domain.risk.risk_appetite✕
- Connections
- 1 pair of types, where a type in application.agents.user_agent uses a type in domain.risk.risk_appetite.
- The types involved
rustrade.application.agents.user_agent.UserAgentConfig→rustrade.domain.risk.risk_appetite.RiskAppetite
- Direction
- application.agents.user_agent uses domain.risk.risk_appetite, so a change to domain.risk.risk_appetite can break application.agents.user_agent, while a change to application.agents.user_agent can't break domain.risk.risk_appetite.
- Position
- Below the diagonal: application.agents.user_agent uses a module listed above it, which is the healthy direction.
40→12 application.agents.user_agent uses infrastructure.i18n.service✕
- Connections
- 1 pair of types, where a type in application.agents.user_agent uses a type in infrastructure.i18n.service.
- The types involved
rustrade.application.agents.user_agent.UserAgent→rustrade.infrastructure.i18n.service.I18nService
- Direction
- application.agents.user_agent uses infrastructure.i18n.service, so a change to infrastructure.i18n.service can break application.agents.user_agent, while a change to application.agents.user_agent can't break infrastructure.i18n.service.
- Position
- Below the diagonal: application.agents.user_agent uses a module listed above it, which is the healthy direction.
40→17 application.agents.user_agent uses domain.trading.types✕
- Connections
- 1 pair of types, where a type in application.agents.user_agent uses a type in domain.trading.types.
- The types involved
rustrade.application.agents.user_agent.UserAgent→rustrade.domain.trading.types.OrderSide
- Direction
- application.agents.user_agent uses domain.trading.types, so a change to domain.trading.types can break application.agents.user_agent, while a change to application.agents.user_agent can't break domain.trading.types.
- Position
- Below the diagonal: application.agents.user_agent uses a module listed above it, which is the healthy direction.
40→23 application.agents.user_agent uses domain.trading.portfolio✕
- Connections
- 1 pair of types, where a type in application.agents.user_agent uses a type in domain.trading.portfolio.
- The types involved
rustrade.application.agents.user_agent.UserAgent→rustrade.domain.trading.portfolio.Portfolio
- Direction
- application.agents.user_agent uses domain.trading.portfolio, so a change to domain.trading.portfolio can break application.agents.user_agent, while a change to application.agents.user_agent can't break domain.trading.portfolio.
- Position
- Below the diagonal: application.agents.user_agent uses a module listed above it, which is the healthy direction.
40→24 application.agents.user_agent uses interfaces.ui_components.settings_state✕
- Connections
- 1 pair of types, where a type in application.agents.user_agent uses a type in interfaces.ui_components.settings_state.
- The types involved
rustrade.application.agents.user_agent.UserAgent→rustrade.interfaces.ui_components.settings_state.SettingsPanel
- Direction
- application.agents.user_agent uses interfaces.ui_components.settings_state, so a change to interfaces.ui_components.settings_state can break application.agents.user_agent, while a change to application.agents.user_agent can't break interfaces.ui_components.settings_state.
- Position
- Below the diagonal: application.agents.user_agent uses a module listed above it, which is the healthy direction.
40→39 application.agents.user_agent uses application.client✕
- Connections
- 1 pair of types, where a type in application.agents.user_agent uses a type in application.client.
- The types involved
rustrade.application.agents.user_agent.UserAgent→rustrade.application.client.SystemClient
- Direction
- application.agents.user_agent uses application.client, so a change to application.client can break application.agents.user_agent, while a change to application.agents.user_agent can't break application.client.
- Position
- Below the diagonal: application.agents.user_agent 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 — Domain Modelling
At a glance — Event-Driven
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 28 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
Roadmap
Top priorities: Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail; Enable Dependabot/Renovate or a dependency-review gate; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail. | +3.6 pts | Medium | Outbound HTTP resilience |
| Enable Dependabot/Renovate or a dependency-review gate. | +3.2 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.8 pts | Medium | Release Hygiene |
| Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only. | +2.4 pts | Medium | Web-Security Posture |
| Interpolated log message defeats structured logging | +1.9 pts | Medium | Structured logging |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.9 pts | Low | Static Analysis (SAST) |
| Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own. | +1.5 pts | Medium | Access Controls |
| Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge. | +0.9 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/application/agents/analyst.rs | 5.7 | Mixed | Cyclomatic Complexity: Analyst::run (cyclomatic 27) |
| src/application/risk_management/core/risk_manager.rs | 5.9 | Mixed | Cyclomatic Complexity: RiskManager::run (cyclomatic 31) |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/application/strategies/traits.rs | 6.0 | Near-clean | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Near-clean | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/domain/performance/metrics.rs | 7.0 | Near-clean | Cyclomatic Complexity: PerformanceMetrics::calculate_time_series_metrics_with_benchmark (cyclomatic 20) |
| src/bin/benchmark.rs | 7.0 | Near-clean | Cyclomatic Complexity: rustrade::bin::benchmark::main (cyclomatic 48) |
| src/interfaces/dashboard_components/architecture_view.rs | 7.0 | Near-clean | Cyclomatic Complexity: rustrade::interfaces::dashboard_components::architecture_view::render_agent_graph (cyclomatic 46) |
| src/application/optimization/simulator/engine.rs | 7.0 | Near-clean | Cyclomatic Complexity: Simulator::run_with_multi_bars (cyclomatic 26) |
| src/domain/snn/competitive_network.rs | 7.0 | Near-clean | Cyclomatic Complexity: CompetitiveSnnNetwork::backward (cyclomatic 16) |
| src/infrastructure/alpaca/execution.rs | 7.0 | Near-clean | Cyclomatic Complexity: AlpacaExecutionService::execute (cyclomatic 16) |
| src/application/strategies/smc.rs | 7.0 | Near-clean | Cyclomatic Complexity: SMCStrategy::analyze (cyclomatic 27) |
| src/application/optimization/core/walk_forward.rs | 7.0 | Near-clean | Cyclomatic Complexity: GridSearchOptimizer::generate_combinations (cyclomatic 16) |
| src/application/benchmarking/engine.rs | 7.0 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| src/bin/optimize/main.rs | 7.1 | Near-clean | Cognitive Complexity: rustrade::bin::optimize::main::main (cognitive 25) |
| src/main.rs | 7.1 | Near-clean | Cyclomatic Complexity: rustrade::main (cyclomatic 21) |
| src/infrastructure/alpaca/market_data/historical.rs | 7.1 | Near-clean | Cyclomatic Complexity: AlpacaMarketDataService::get_historical_bars_internal (cyclomatic 18) |
| src/infrastructure/alpaca/websocket.rs | 7.2 | Near-clean | Cyclomatic Complexity: AlpacaWebSocketManager::run_connection (cyclomatic 31) |
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 64 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 64 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, 332 of 344 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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 READ here — but this repository measures it: a coverage step in CI (`cargo tarpaulin`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- 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 source is present (.rs) and this repository declares a Cargo test suite (repository root, 135 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (8.06 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 238 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.
- 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.
- 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 deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 ToolchainServer (.). the service did not build — `cargo build --locked --bin 'rustrade'` exited 1: info: syncing channel updates for 1.99.1-x86_64-unknown-linux-gnu error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-1.99.1.toml.sha256' to '/usr/local/rustup/tmp/qakn…; runtime evidence skipped (launch chosen because 'axum' dependency in Cargo.toml, binary 'rustrade').
- GD1 Unfinished & placeholder code — 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 reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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. 452 further occurrence(s) are not listed individually; the score already reflects all 492.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- 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.
- 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
37 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was rustrade::bin::benchmark::main at 48. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SettingsPanel::apply_persisted_settings at 17 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/interfaces/ui_components/settings_state.rs (SettingsPanel::apply_persisted_settings at 17), src/infrastructure/persistence/repositories/mod.rs (SqliteOrderRepository::map_rows_to_orders at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with rustrade::bin::benchmark::main (cyclomatic 48), rustrade::interfaces::dashboard_components::architecture_view::render_agent_graph (cyclomatic 46), rustrade::interfaces::dashboard::render_dashboard (cyclomatic 43). — 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 6.3 to about 7.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
91 method(s) exceeded the cognitive complexity threshold of 15; the worst was rustrade::bin::benchmark::main at 174.
What to do
- Bring the 33 bodies over 30 down to 30 or less in Cognitive Complexity — start with rustrade::bin::benchmark::main (cognitive 174), GridSearchOptimizer::generate_combinations (cognitive 108), rustrade::interfaces::dashboard_components::architecture_view::render_agent_graph (cognitive 95). — 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 33 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
52 god class(es) detected.
What to do
- Resolve the 25 MethodTooLong finding(s) in God Classes — start with engine.rs (3), metrics.rs (3), walk_forward.rs (2). — One of this dimension's main actionable groups (25 warning-level).
- Resolve the 19 FunctionTooLong finding(s) in God Classes — start with architecture_view.rs (2), main.rs (2), train_surrogate.rs (2). — One of this dimension's main actionable groups (19 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with architecture_view.rs, main.rs, execution.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
57 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with optimization_history_repository.rs (2), benchmark.rs, optimal_parameters_persistence.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with engine.rs, genetic.rs, walk_forward.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with metrics.rs, competitive_network.rs, optimal_parameters_persistence.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
2 of 120 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with reporting.rs, trade_filter.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
600 test methods: 534 unit, 64 integration, 0 BDD, 2 e2e. The Rust suite contributes 600 `#[test]` function(s) across 135 file(s) declaring at least one; its unit/integration split is Cargo's own — 21 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
2 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 640 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/application/risk_management/position/sizing_engine.rs (2×18=36)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with sizing_engine.rs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
1 deducted task-comment markers across 52428 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with traits.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 11 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 2 build units (Cargo, Python) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
28 finding(s): 0 critical, 28 high, 0 medium, 0 low. 26 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 26 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (26 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 0 high, 7 medium, 0 low.
What to do
- Resolve the 5 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 194 of the 280 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: analyst.rs↔optimizer.rs 81%; analyst.rs↔websocket.rs 73%; optimizer.rs↔mod.rs 69%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with optimizer.rs, risk_manager.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with analyst.rs. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 1 platform declaration(s) and 6 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
AX9 · CQS / query purity
- `BinanceMarketDataService.get_historical_bars` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — src/infrastructure/binance/market_data.rs:382
What to do
- Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
DM1 · Aggregate boundaries
DM2 · Strongly-typed ids
DM4 · Rich vs anemic domain model
ED4 · Outbox / dual-write
- `AdaptiveOptimizationService.execute_reoptimization` performs two independent DURABLE writes — a durable state write (`history_repo.save`, :192) and a second independent durable store write — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox). — src/application/optimization/adaptive_optimization_service.rs:142
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `walkthrough.md`, but `walkthrough.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:115
What to do
- Reconcile the README with reality: README.md links to `walkthrough.md`, but `walkthrough.md` does not exist.
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P2 · Observability
What to do
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/application/risk_management/core/risk_manager/alerts.rs:43
- `Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/infrastructure/news/rss.rs:30
What to do
- Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
- `run_parallel` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — src/application/optimization/parallel_benchmark.rs:84
What to do
- Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
S1 · Web-Security Posture
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `axum::serve(` (src/infrastructure/api/mod.rs:115).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `axum::serve(` (src/infrastructure/api/mod.rs:115).
- No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `axum::serve(` (src/infrastructure/api/mod.rs:115).
What to do
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: derive `validator::Validate` (or `garde::Validate`) on the request types and reject with `StatusCode::BAD_REQUEST`, and cap bodies with `DefaultBodyLimit::max`/`RequestBodyLimitLayer` or actix's `JsonConfig::default().limit(…)`.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error!` at line 93 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:93
- `error!` at line 102 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:102
- `error!` at line 123 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:123
- `error!` at line 133 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:133
- `error!` at line 140 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:140
- `info!` at line 181 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:181
- `info!` at line 226 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:226
- `info!` at line 250 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:250
- `error!` at line 258 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:258
- `info!` at line 145 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/ui.rs:145
- `error!` at line 122 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/ui_components/settings_state.rs:122
- `error!` at line 124 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/ui_components/settings_state.rs:124
- `error!` at line 374 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/ui_components/settings_view.rs:374
- `error!` at line 384 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/ui_components/settings_view.rs:384
- `error!` at line 392 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/ui_components/settings_view.rs:392
- `error!` at line 400 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/ui_components/settings_view.rs:400
- `error!` at line 254 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/settings_components/symbol_selector.rs:254
- `info!` at line 258 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/settings_components/symbol_selector.rs:258
- `info!` at line 359 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/interfaces/dashboard_components/architecture_view.rs:359
- `warn!` at line 13 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/notifications.rs:13
- `warn!` at line 54 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/notifications.rs:54
- `info!` at line 58 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/notifications.rs:58
- `info!` at line 63 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/notifications.rs:63
- `info!` at line 46 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/infrastructure/optimal_parameters_persistence.rs:46, REDACTED:46
- `info!` at line 71 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/optimal_parameters_persistence.rs:71
- `info!` at line 77 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/settings_persistence.rs:77
- `info!` at line 101 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/settings_persistence.rs:101
- `info!` at line 97 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — REDACTED:97
- `info!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — REDACTED:128
- `info!` at line 64 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/persistence/repositories/mod.rs:64
- `info!` at line 42 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/persistence/repositories/strategy_repository.rs:42
- `info!` at line 78 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/observability/reporter.rs:78
- `info!` at line 94 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/observability/reporter.rs:94
- `warn!` at line 101 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/observability/reporter.rs:101
- `warn!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/observability/reporter.rs:104
- `info!` at line 48 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/news/mock_news.rs:48
- `info!` at line 68 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/news/mock_news.rs:68
- `debug!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/news/rss.rs:56
- `error!` at line 137 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/infrastructure/news/rss.rs:137
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by D2, X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 75% | Exemplary | Solid. |
| Readiness | 57% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63% | Adequate | Acceptable, with room to improve. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Event-Driven | 80% | Exemplary | Solid. |
| Event Sourcing | 100% | Exemplary | Solid. |
| Performance | 82% | Exemplary | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service did not build — `cargo build --locked --bin 'rustrade'` exited 1: info: syncing channel updates for 1.99.1-x86_64-unknown-linux-gnu error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-1.99.1.toml.sha256' to '/usr/local/rustup/tmp/qakn…; runtime evidence skipped (launch chosen because 'axum' dependency in Cargo.toml, binary 'rustrade') 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 a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~6118 lines of test source are present (.rs) 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 included — the .rs suite was found but not re-run
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python, Rust not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — 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. Aggregate roots were found in only one source directory (domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM5 Encapsulated state — this Rust crate declares no type implementing a hand-rolled Hash/PartialEq, so DM5's value-identity encapsulation read has no population to be taken over
- DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P8 Schema migrations — sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 30 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Query writes persistent state on the read path: BinanceMarketDataService.get_historical_bars src/infrastructure/binance/market_data.rs:382
- Dual write (no outbox): AdaptiveOptimizationService.execute_reoptimization src/application/optimization/adaptive_optimization_service.rs:142
Serious — 258 finding(s)
- rustrade::bin::benchmark::main (cognitive 174) src/bin/benchmark.rs:232
- rustrade::interfaces::dashboard_components::architecture_view::render_agent_graph (cognitive 95) src/interfaces/dashboard_components/architecture_view.rs:307
- rustrade::interfaces::dashboard::render_dashboard (cognitive 68) src/interfaces/dashboard.rs:17
- rustrade::interfaces::dashboard_components::chart_panel::render_chart_panel (cognitive 67) src/interfaces/dashboard_components/chart_panel.rs:9
- rustrade::application::ml::derivative_encoding::encode_multi_feature (cognitive 64) src/application/ml/derivative_encoding.rs:60
- rustrade::interfaces::dashboard_components::analytics_view::render_analytics_view (cognitive 51) src/interfaces/dashboard_components/analytics_view.rs:6
- rustrade::domain::performance::calculator::calculate_metrics_from_orders (cognitive 49) src/domain/performance/calculator.rs:15
- rustrade::main (cognitive 43) src/main.rs:45
- rustrade::bin::train_surrogate::main (cognitive 38) src/bin/train_surrogate.rs:386
- rustrade::interfaces::settings_components::symbol_selector::render_symbol_selector (cognitive 33) src/interfaces/settings_components/symbol_selector.rs:47
- rustrade::interfaces::settings_components::help_about::render_help_tab (cognitive 30) src/interfaces/settings_components/help_about.rs:28
- rustrade::interfaces::dashboard_components::activity_feed::render_logs_panel (cognitive 29) src/interfaces/dashboard_components/activity_feed.rs:74
- rustrade::bin::ensemble_optimizer::main (cognitive 28) src/bin/ensemble_optimizer.rs:40
- rustrade::bin::optimize::main::main (cognitive 25) src/bin/optimize/main.rs:503
- rustrade::infrastructure::api::handle_socket (cognitive 25) src/infrastructure/api/mod.rs:218
- rustrade::interfaces::dashboard_components::architecture_view::render_agent_detail_panel (cognitive 25) src/interfaces/dashboard_components/architecture_view.rs:649
- rustrade::application::agents::regime_handler::apply_dynamic_risk_scaling (cognitive 24) src/application/agents/regime_handler.rs:77
- rustrade::bin::optimize::main::run_optimize (cognitive 21) src/bin/optimize/main.rs:205
- rustrade::bin::optimize::main::run_clusters (cognitive 21) src/bin/optimize/main.rs:334
- rustrade::interfaces::dashboard_components::symbol_card::render_symbol_card (cognitive 20) src/interfaces/dashboard_components/symbol_card.rs:6
- rustrade::application::bootstrap::agents::spawn_adaptive_optimization (cognitive 18) src/application/bootstrap/agents.rs:534
- rustrade::interfaces::dashboard_components::news_feed::render_news_feed (cognitive 17) src/interfaces/dashboard_components/news_feed.rs:5
- rustrade::interfaces::ui_components::settings_view::render_trading_engine_content (cognitive 17) src/interfaces/ui_components/settings_view.rs:182
- rustrade::interfaces::ui_components::settings_view::render_save_button (cognitive 17) src/interfaces/ui_components/settings_view.rs:322
- rustrade::application::agents::position_lifecycle::manage_pending_orders (cognitive 16) src/application/agents/position_lifecycle.rs:28
- MethodTooLong: AgentsBootstrap.init src/application/bootstrap/agents.rs:54
- MethodTooLong: Simulator.run_with_multi_bars src/application/optimization/simulator/engine.rs:322
- MethodTooLong: PerformanceMetrics.calculate_time_series_metrics_with_benchmark src/domain/performance/metrics.rs:92
- MethodTooLong: Database.apply_v1 REDACTED:135
- MethodTooLong: AlpacaExecutionService.new src/infrastructure/alpaca/execution.rs:36
- MethodTooLong: MockExecutionService.execute src/infrastructure/mock/execution_service.rs:76
- MethodTooLong: ParameterGrid.gene_bounds src/application/optimization/core/grid.rs:54
- MethodTooLong: GridSearchOptimizer.generate_combinations src/application/optimization/core/walk_forward.rs:43
- MethodTooLong: RiskManager.cmd_handle_proposal src/application/risk_management/core/risk_manager/handler.rs:109
- MethodTooLong: AlpacaMarketDataService.get_historical_bars_internal src/infrastructure/alpaca/market_data/historical.rs:255
- MethodTooLong: Metrics.new src/infrastructure/observability/metrics.rs:59
- MethodTooLong: StrategyEnvLoader.from_env src/config/strategy_config.rs:17
- MethodTooLong: Sentinel.run src/application/agents/sentinel.rs:58
- MethodTooLong: CompetitiveSnnNetwork.forward src/domain/snn/competitive_network.rs:150
- MethodTooLong: PerformanceMetrics.calculate_from_equity_curve src/domain/performance/metrics.rs:328
- MethodTooLong: RiskManager.run src/application/risk_management/core/risk_manager.rs:266
- MethodTooLong: AlpacaWebSocketManager.run_connection src/infrastructure/alpaca/websocket.rs:300
- MethodTooLong: TechnicalFeatureEngineeringService.update src/application/monitoring/strategy/feature_engineering_service.rs:199
- MethodTooLong: Analyst.run src/application/agents/analyst.rs:183
- MethodTooLong: WarmupService.warmup_context src/application/agents/warmup_service.rs:86
- MethodTooLong: Simulator.run_with_bars src/application/optimization/simulator/engine.rs:166
- MethodTooLong: CompetitiveSnnNetwork.backward src/domain/snn/competitive_network.rs:344
- MethodTooLong: Simulator.run_simulation_core src/application/optimization/simulator/engine.rs:17
- MethodTooLong: ServiceFactory.create_services src/infrastructure/factory.rs:18
- MethodTooLong: GridSearchOptimizer.run_optimization src/application/optimization/core/walk_forward.rs:276
- FunctionTooLong: rustrade::interfaces::dashboard::render_dashboard src/interfaces/dashboard.rs:17
- FunctionTooLong: rustrade::bin::benchmark::main src/bin/benchmark.rs:232
- FunctionTooLong: rustrade::interfaces::dashboard_components::architecture_view::render_agent_graph src/interfaces/dashboard_components/architecture_view.rs:307
- FunctionTooLong: rustrade::bin::optimize::main::main src/bin/optimize/main.rs:503
- FunctionTooLong: rustrade::bin::train_surrogate::main src/bin/train_surrogate.rs:386
- FunctionTooLong: rustrade::interfaces::settings_components::strategy_settings::render_strategy_settings src/interfaces/settings_components/strategy_settings.rs:68
- FunctionTooLong: rustrade::main src/main.rs:45
- FunctionTooLong: rustrade::interfaces::dashboard_components::architecture_view::render_agent_detail_panel src/interfaces/dashboard_components/architecture_view.rs:649
- FunctionTooLong: rustrade::interfaces::settings_components::symbol_selector::render_symbol_selector src/interfaces/settings_components/symbol_selector.rs:47
- FunctionTooLong: rustrade::interfaces::settings_components::help_about::render_help_tab src/interfaces/settings_components/help_about.rs:28
- FunctionTooLong: rustrade::interfaces::dashboard_components::symbol_card::render_symbol_card src/interfaces/dashboard_components/symbol_card.rs:6
- FunctionTooLong: rustrade::interfaces::settings_components::risk_settings::render_risk_settings src/interfaces/settings_components/risk_settings.rs:14
- FunctionTooLong: rustrade::interfaces::dashboard_components::analytics_view::render_analytics_view src/interfaces/dashboard_components/analytics_view.rs:6
- FunctionTooLong: rustrade::interfaces::dashboard_components::chart_panel::render_chart_panel src/interfaces/dashboard_components/chart_panel.rs:9
- FunctionTooLong: rustrade::bin::train_surrogate::fetch_and_encode_data src/bin/train_surrogate.rs:167
- FunctionTooLong: rustrade::bin::ensemble_optimizer::main src/bin/ensemble_optimizer.rs:40
- FunctionTooLong: rustrade::interfaces::dashboard_components::activity_feed::render_logs_panel src/interfaces/dashboard_components/activity_feed.rs:74
- FunctionTooLong: rustrade::application::ml::derivative_encoding::encode_multi_feature src/application/ml/derivative_encoding.rs:60
- FunctionTooLong: rustrade::application::optimization::core::grid::decode_genome src/application/optimization/core/grid.rs:228
- rustrade::bin::benchmark::main (cyclomatic 48) src/bin/benchmark.rs:232
- rustrade::interfaces::dashboard_components::architecture_view::render_agent_graph (cyclomatic 46) src/interfaces/dashboard_components/architecture_view.rs:307
- rustrade::interfaces::dashboard::render_dashboard (cyclomatic 43) src/interfaces/dashboard.rs:17
- rustrade::application::ml::derivative_encoding::encode_multi_feature (cyclomatic 36) src/application/ml/derivative_encoding.rs:60
- rustrade::domain::performance::calculator::calculate_metrics_from_orders (cyclomatic 22) src/domain/performance/calculator.rs:15
- rustrade::interfaces::settings_components::symbol_selector::render_symbol_selector (cyclomatic 21) src/interfaces/settings_components/symbol_selector.rs:47
- rustrade::main (cyclomatic 21) src/main.rs:45
- rustrade::bin::train_surrogate::main (cyclomatic 20) src/bin/train_surrogate.rs:386
- rustrade::interfaces::dashboard_components::activity_feed::render_logs_panel (cyclomatic 20) src/interfaces/dashboard_components/activity_feed.rs:74
- rustrade::interfaces::dashboard_components::chart_panel::render_chart_panel (cyclomatic 18) src/interfaces/dashboard_components/chart_panel.rs:9
- rustrade::interfaces::dashboard_components::analytics_view::render_analytics_view (cyclomatic 17) src/interfaces/dashboard_components/analytics_view.rs:6
- rustrade::bin::ensemble_optimizer::main (cyclomatic 16) src/bin/ensemble_optimizer.rs:40
- rustrade::interfaces::dashboard_components::architecture_view::render_agent_detail_panel (cyclomatic 16) src/interfaces/dashboard_components/architecture_view.rs:649
- Duplicated block (9 lines × 2) src/bin/benchmark.rs:234
- Duplicated block (9 lines × 2) src/infrastructure/optimal_parameters_persistence.rs:59
- Duplicated block (9 lines × 2) src/main.rs:190
- Duplicated block (9 lines × 2) src/infrastructure/binance/execution.rs:344
- Duplicated block (9 lines × 2) src/infrastructure/persistence/repositories/optimization_history_repository.rs:95
- Duplicated block (9 lines × 2) src/infrastructure/persistence/repositories/optimization_history_repository.rs:57
- Duplicated block (9 lines × 2) src/interfaces/dashboard_components/architecture_view.rs:269
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) src/application/benchmarking/engine.rs:368
- Duplicated block (13 lines × 2) src/application/optimization/core/genetic.rs:61
- Duplicated block (13 lines × 2) src/application/optimization/core/walk_forward.rs:261
- Duplicated block (13 lines × 2) src/bin/benchmark.rs:214
- Duplicated block (13 lines × 2) src/main.rs:176
- AlpacaMarketDataService::get_historical_bars_internal (cognitive 61) src/infrastructure/alpaca/market_data/historical.rs:255
- AlpacaMarketDataService::get_historical_movers (cognitive 21) src/infrastructure/alpaca/market_data/historical.rs:12
- AlpacaMarketDataService::get_prices_internal (cognitive 21) src/infrastructure/alpaca/market_data/price.rs:238
- AlpacaMarketDataService::fetch_historical_bars_internal (cognitive 17) src/infrastructure/alpaca/market_data/historical.rs:110
- Executor::handle_order (cognitive 24) src/application/agents/executor/mod.rs:160
- Executor::update_portfolio (cognitive 22) src/application/agents/executor/acceptance.rs:113
- Executor::reconcile_pending (cognitive 22) src/application/agents/executor/reconciliation.rs:71
- Executor::run (cognitive 19) src/application/agents/executor/mod.rs:95
- FileTooLong: dashboard_components/architecture_view.rs src/interfaces/dashboard_components/architecture_view.rs
- FileTooLong: optimize/main.rs src/bin/optimize/main.rs
- FileTooLong: alpaca/execution.rs src/infrastructure/alpaca/execution.rs
- FileTooLong: bin/benchmark.rs src/bin/benchmark.rs
- Duplicated block (8 lines × 2) src/application/agents/user_agent/metrics.rs:45
- Duplicated block (8 lines × 2) src/domain/snn/competitive_network.rs:431
- Duplicated block (8 lines × 2) src/infrastructure/optimal_parameters_persistence.rs:23
- Duplicated block (8 lines × 2) src/config/risk_env_config.rs:40
- SMCStrategy::detect_fvg (cognitive 82) src/application/strategies/smc.rs:49
- SMCStrategy::analyze (cognitive 75) src/application/strategies/smc.rs:347
- SMCStrategy::find_last_ob (cognitive 24) src/application/strategies/smc.rs:182
- RiskManager::run (cognitive 67) src/application/risk_management/core/risk_manager.rs:266
- RiskManager::cmd_handle_proposal (cognitive 38) src/application/risk_management/core/risk_manager/handler.rs:109
- RiskManager::update_portfolio_valuation (cognitive 16) src/application/risk_management/core/risk_manager/valuation.rs:33
- Simulator::run_with_multi_bars (cognitive 50) src/application/optimization/simulator/engine.rs:322
- Simulator::run_with_bars (cognitive 32) src/application/optimization/simulator/engine.rs:166
- Simulator::run_simulation_core (cognitive 29) src/application/optimization/simulator/engine.rs:17
- UserAgent::update (cognitive 38) src/application/agents/user_agent.rs:230
- UserAgent::parse_log_for_activity (cognitive 32) src/application/agents/user_agent/activity.rs:68
- UserAgent::calculate_trade_statistics (cognitive 30) src/application/agents/user_agent/metrics.rs:116
- Duplicated block (12 lines × 2) src/application/strategies/snn_surrogate_strategy.rs:147
- Duplicated block (12 lines × 2) src/domain/performance/metrics.rs:208
- Duplicated block (12 lines × 2) src/infrastructure/alpaca/execution.rs:600
- Duplicated block (10 lines × 2) src/application/strategies/order_flow.rs:64
- Duplicated block (10 lines × 2) src/application/strategies/order_flow.rs:84
- Duplicated block (10 lines × 2) src/infrastructure/binance/execution.rs:420
- Duplicated block (7 lines × 2) src/domain/performance/metrics.rs:283
- Duplicated block (7 lines × 2) src/infrastructure/mock/execution_service.rs:150
- Duplicated block (7 lines × 2) src/application/agents/user_agent.rs:99
- Duplicated block (6 lines × 2) src/application/optimization/core/walk_forward.rs:311
- Duplicated block (6 lines × 2) src/bin/benchmark.rs:202
- Duplicated block (6 lines × 2) src/config/risk_env_config.rs:154
- RiskManager::run (cyclomatic 31) src/application/risk_management/core/risk_manager.rs:266
- RiskManager::cmd_handle_proposal (cyclomatic 20) src/application/risk_management/core/risk_manager/handler.rs:109
- SMCStrategy::analyze (cyclomatic 27) src/application/strategies/smc.rs:347
- SMCStrategy::detect_fvg (cyclomatic 25) src/application/strategies/smc.rs:49
- Simulator::run_with_multi_bars (cyclomatic 26) src/application/optimization/simulator/engine.rs:322
- Simulator::run_with_bars (cyclomatic 19) src/application/optimization/simulator/engine.rs:166
- UserAgent::parse_log_for_activity (cyclomatic 24) src/application/agents/user_agent/activity.rs:68
- UserAgent::update (cyclomatic 17) src/application/agents/user_agent.rs:230
- GridSearchOptimizer::generate_combinations (cognitive 108) src/application/optimization/core/walk_forward.rs:43
- GridSearchOptimizer::run_optimization (cognitive 16) src/application/optimization/core/walk_forward.rs:276
- AlpacaWebSocketManager::run_connection (cognitive 77) src/infrastructure/alpaca/websocket.rs:300
- AlpacaWebSocketManager::spawn_connection_task (cognitive 21) src/infrastructure/alpaca/websocket.rs:210
- Analyst::run (cognitive 69) src/application/agents/analyst.rs:183
- Analyst::handle_news_signal (cognitive 17) src/application/agents/analyst.rs:558
- PerformanceMetrics::calculate_time_series_metrics_with_benchmark (cognitive 34) src/domain/performance/metrics.rs:92
- PerformanceMetrics::calculate_from_equity_curve (cognitive 25) src/domain/performance/metrics.rs:328
- CompetitiveSnnNetwork::backward (cognitive 34) src/domain/snn/competitive_network.rs:344
- CompetitiveSnnNetwork::forward (cognitive 23) src/domain/snn/competitive_network.rs:150
- OrderReconciler::reconcile_pending_orders (cognitive 21) src/application/risk_management/execution/order_reconciler.rs:127
- OrderReconciler::handle_order_update (cognitive 19) src/application/risk_management/execution/order_reconciler.rs:51
- AlpacaExecutionService::new (cognitive 19) src/infrastructure/alpaca/execution.rs:36
- AlpacaExecutionService::execute (cognitive 18) src/infrastructure/alpaca/execution.rs:297
- TooManyFields: StrategyConfig src/domain/config/strategy_config.rs:33
- TooManyFields: AnalysisContext src/application/strategies/traits.rs:35
- ClassTooLong: AlpacaExecutionService src/infrastructure/alpaca/execution.rs:22
- ClassTooLong: PerformanceMetrics src/domain/performance/metrics.rs:12
- REDACTED
- REDACTED
- Change coupling: optimizer.rs ↔ mod.rs src/application/optimization/optimizer.rs:1
- Change coupling: risk_manager.rs ↔ execution.rs src/application/risk_management/core/risk_manager.rs:1
- Duplicated block (11 lines × 2) src/infrastructure/binance/market_data.rs:370
- Duplicated block (11 lines × 2) src/infrastructure/persistence/repositories/performance_snapshot_repository.rs:60
- Duplicated block (5 lines × 2) src/bin/train_gen.rs:64
- Duplicated block (5 lines × 2) src/domain/snn/competitive_network.rs:117
- Duplicated block (14 lines × 2) src/bin/optimize/main.rs:303
- Duplicated block (14 lines × 2) src/application/strategies/smc.rs:384
- Low cohesion: OptimizeReporter (LCOM4 5) src/application/optimization/reporting.rs:11
- Low cohesion: TradeFilter (LCOM4 4) src/application/trading/trade_filter.rs:10
- Outbound HTTP without resilience src/application/risk_management/core/risk_manager/alerts.rs:43
- Outbound HTTP without resilience src/infrastructure/news/rss.rs:30
- AlpacaWebSocketManager::run_connection (cyclomatic 31) src/infrastructure/alpaca/websocket.rs:300
- Sentinel::run (cyclomatic 29) src/application/agents/sentinel.rs:58
- AgentsBootstrap::init (cyclomatic 29) src/application/bootstrap/agents.rs:54
- Analyst::run (cyclomatic 27) src/application/agents/analyst.rs:183
- BinanceWebSocketManager::connect_and_stream (cyclomatic 22) src/infrastructure/binance/websocket.rs:116
- PerformanceMetrics::calculate_time_series_metrics_with_benchmark (cyclomatic 20) src/domain/performance/metrics.rs:92
- EnsembleStrategy::analyze (cyclomatic 19) src/application/strategies/ensemble.rs:146
- SizingEngine::calculate_quantity (cyclomatic 18) src/application/risk_management/position/sizing_engine.rs:164
- AlpacaMarketDataService::get_historical_bars_internal (cyclomatic 18) src/infrastructure/alpaca/market_data/historical.rs:255
- SnnSurrogateStrategy::prepare_rolling_window (cyclomatic 17) src/application/strategies/snn_surrogate_strategy.rs:85
- MonteCarloEngine::simulate (cyclomatic 17) src/domain/performance/monte_carlo.rs:28
- Executor::handle_order (cyclomatic 16) src/application/agents/executor/mod.rs:160
- GridSearchOptimizer::generate_combinations (cyclomatic 16) src/application/optimization/core/walk_forward.rs:43
- OrderFlowStrategy::analyze (cyclomatic 16) src/application/strategies/order_flow.rs:51
- CompetitiveSnnNetwork::backward (cyclomatic 16) src/domain/snn/competitive_network.rs:344
- AlpacaExecutionService::execute (cyclomatic 16) src/infrastructure/alpaca/execution.rs:297
- Hotspot: src/application/risk_management/position/sizing_engine.rs src/application/risk_management/position/sizing_engine.rs:164
- TodoComment src/application/strategies/traits.rs:290
- Sentinel::run (cognitive 81) src/application/agents/sentinel.rs:58
- RssNewsService::subscribe_news (cognitive 56) src/infrastructure/news/rss.rs:41
- AgentsBootstrap::init (cognitive 44) src/application/bootstrap/agents.rs:54
- MonteCarloEngine::simulate (cognitive 42) src/domain/performance/monte_carlo.rs:28
- ListenerAgent::run (cognitive 37) src/application/agents/listener.rs:64
- OrderFlowStrategy::analyze (cognitive 37) src/application/strategies/order_flow.rs:51
- MarketScanner::run (cognitive 33) src/application/agents/scanner.rs:36
- BinanceWebSocketManager::connect_and_stream (cognitive 32) src/infrastructure/binance/websocket.rs:116
- SnnSurrogateStrategy::prepare_rolling_window (cognitive 31) src/application/strategies/snn_surrogate_strategy.rs:85
- compare_strategies.main (cognitive 30) scripts/compare_strategies.py:57
- SessionManager::initialize_session (cognitive 29) src/application/risk_management/session/session_manager.rs:51
- EnsembleStrategy::analyze (cognitive 29) src/application/strategies/ensemble.rs:146
- AnalysisContext::multi_timeframe_trend_strength (cognitive 27) src/application/strategies/traits.rs:190
- EmpiricalWinRateProvider::get_overall_win_rate (cognitive 25) src/application/monitoring/strategy/empirical_win_rate_provider.rs:126
- Scanner::scan (cognitive 24) src/infrastructure/alpaca/market_data/crypto_movers.rs:16
- AlpacaTradingStream::run_connection (cognitive 23) src/infrastructure/alpaca/trading_stream.rs:141
- MockExecutionService::execute (cognitive 23) src/infrastructure/mock/execution_service.rs:76
- TechnicalFeatureEngineeringService::update (cognitive 22) src/application/monitoring/strategy/feature_engineering_service.rs:199
- SizingEngine::calculate_quantity (cognitive 21) src/application/risk_management/position/sizing_engine.rs:164
- HistoricalWinRateProvider::calculate_win_rate_from_orders (cognitive 20) src/application/optimization/win_rate_provider.rs:77
- DashboardViewModel::get_metrics (cognitive 20) src/interfaces/view_models/dashboard_view_model.rs:38
- DataCollector::update_labels_and_flush (cognitive 19) src/application/ml/data_collector.rs:57
- ManualAdx::next (cognitive 19) src/application/monitoring/strategy/feature_engineering_service.rs:53
- GeneticOptimizer::run_optimization (cognitive 18) src/application/optimization/core/genetic.rs:54
- DiffIzhikevichLayer::backward (cognitive 18) src/domain/snn/izhikevich_diff.rs:304
- check_coverage.main (cognitive 18) scripts/check_coverage.py:36
- CandleAggregator::on_quote (cognitive 17) src/application/market_data/candle_aggregator.rs:178
- TradeEvaluator::evaluate_and_propose (cognitive 16) src/application/agents/trade_evaluator.rs:44
- MarketRegimeDetector::detect (cognitive 16) src/domain/market/market_regime.rs:130
- ArbitrageEngine::check_opportunity (cognitive 16) src/domain/trading/arbitrage.rs:25
- Change-coupling hub: analyst.rs → sentinel.rs, optimizer.rs, websocket.rs src/application/agents/analyst.rs
- REDACTED
- Near-duplicate member pair (127 shared lines) src/domain/performance/metrics.rs:97
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/application/benchmarking/engine.rs:367
- Duplicated block (36–38 lines × 2) src/application/benchmarking/engine.rs:275
- Duplicated block (32 lines × 2) src/domain/performance/metrics.rs:293
- Duplicated block (30 lines × 2) src/domain/performance/metrics.rs:221
- Duplicated block (25–27 lines × 2) src/application/strategies/smc.rs:76
- Duplicated block (26–27 lines × 2) src/bin/benchmark.rs:354
- Duplicated block (24 lines × 2) src/domain/performance/metrics.rs:183
- Duplicated block (22–23 lines × 2) src/domain/risk/risk_config.rs:122
- Duplicated block (22 lines × 2) src/domain/performance/metrics.rs:253
- Duplicated block (16–20 lines × 2) src/bin/benchmark.rs:320
- Duplicated block (20 lines × 2) src/domain/ml/feature_registry.rs:30
- Duplicated block (18–20 lines × 2) src/interfaces/dashboard_components/architecture_view.rs:397
- Duplicated block (17 lines × 2) src/application/benchmarking/engine.rs:383
- Duplicated block (16 lines × 3) src/application/benchmarking/engine.rs:382
- Duplicated block (11–15 lines × 3) src/application/benchmarking/engine.rs:63
- Duplicated block (12–13 lines × 2) src/application/market_data/timeframe_aggregator.rs:79
- Duplicated block (10–12 lines × 2) src/domain/performance/metrics.rs:152
- Duplicated block (11 lines × 4) src/application/benchmarking/engine.rs:382
- Duplicated block (7–9 lines × 2) src/application/benchmarking/reporting.rs:243
- Duplicated block (6 lines × 3) src/domain/snn/competitive_network.rs:424
- Duplicated block (10 lines × 3) src/infrastructure/alpaca/execution.rs:420
- Duplicated block (11 lines × 3) src/infrastructure/binance/execution.rs:318
- Duplicated block (8 lines × 4) src/infrastructure/alpaca/execution.rs:423
- Duplicated block (27–28 lines × 2) scripts/compare_strategies.py:28
- Coverage collected but not gated
- Sync-over-async blocking src/application/optimization/parallel_benchmark.rs:84
Minor — 54 finding(s)
- Interpolated log message defeats structured logging src/main.rs:93
- Interpolated log message defeats structured logging src/main.rs:102
- Interpolated log message defeats structured logging src/main.rs:123
- Interpolated log message defeats structured logging src/main.rs:133
- Interpolated log message defeats structured logging src/main.rs:140
- Interpolated log message defeats structured logging src/main.rs:181
- Interpolated log message defeats structured logging src/main.rs:226
- Interpolated log message defeats structured logging src/main.rs:250
- Interpolated log message defeats structured logging src/main.rs:258
- Interpolated log message defeats structured logging src/interfaces/ui.rs:145
- Interpolated log message defeats structured logging src/interfaces/ui_components/settings_state.rs:122
- Interpolated log message defeats structured logging src/interfaces/ui_components/settings_state.rs:124
- Interpolated log message defeats structured logging src/interfaces/ui_components/settings_view.rs:374
- Interpolated log message defeats structured logging src/interfaces/ui_components/settings_view.rs:384
- Interpolated log message defeats structured logging src/interfaces/ui_components/settings_view.rs:392
- Interpolated log message defeats structured logging src/interfaces/ui_components/settings_view.rs:400
- Interpolated log message defeats structured logging src/interfaces/settings_components/symbol_selector.rs:254
- Interpolated log message defeats structured logging src/interfaces/settings_components/symbol_selector.rs:258
- Interpolated log message defeats structured logging src/interfaces/dashboard_components/architecture_view.rs:359
- Interpolated log message defeats structured logging src/infrastructure/notifications.rs:13
- Interpolated log message defeats structured logging src/infrastructure/notifications.rs:54
- Interpolated log message defeats structured logging src/infrastructure/notifications.rs:58
- Interpolated log message defeats structured logging src/infrastructure/notifications.rs:63
- Interpolated log message defeats structured logging src/infrastructure/optimal_parameters_persistence.rs:46
- Interpolated log message defeats structured logging src/infrastructure/optimal_parameters_persistence.rs:71
- Silent fallback default on Err src/application/agents/user_agent/metrics.rs:206
- Silent fallback default on Err src/application/agents/user_agent/metrics.rs:249
- Silent fallback default on Err src/application/monitoring/health/agent_status.rs:112
- No named authorization policies
- Projects may be oversized for their cohesion
- REDACTED
- No ADRs
- README/code drift README.md:115
- CI build step not evidenced
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
- No inbound request validation detected
- Duplicated predicate src/application/risk_management/core/risk_manager.rs:401
Minor — 2 finding(s)
- Outdated: toml
- Outdated: uuid
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-06ddb5788a16405190d4f491e90efc97/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-06ddb5788a16405190d4f491e90efc97/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 28 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 7 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |