Executive summary
MagicEthan/EliteQuant_Python falls short of our standard for production because the project has no automated tests and two passwords or keys sit in the current code. It scores 37 out of 100 and is rated Weak, and five of its eight critical findings are leaked passwords or keys.
Production Readiness, at 0, is the weakest lens and counts most in the score. The best first steps are replacing the two exposed passwords or keys and switching the old ones off and adding automated tests, each worth about 34 points. Raising Production Readiness to 70 would lift the score to about 68.
Three passwords or keys in the code's history and two in the code are open to anyone who can read the repository. The project has no automated tests, so a change can break it without warning. Adding automated tests and replacing each exposed password or key would close both risks. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 2,932 lines, about €2,500 to rebuild.
If Production Readiness rose from 0 to 70, the lowest score rated Strong, the score would rise from 37 to about 68.
Rebuild cost: about €2,500 · Estimate
| Cost to rebuild | €830 to €4,200, for 14 to 44 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 37. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,932 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 source | 2 source.account.account_manager | 3 source.backtest_engine | 4 source.brokerage.brokerage_base | 5 source.data.data_board | 6 source.data.data_feed_base | 7 source.event.backtest_event_engine | 8 source.event.client_mq | 9 source.event.event | 10 source.event.live_event_engine | 11 source.gui.ui_account_window | 12 source.gui.ui_fill_window | 13 source.gui.ui_log_window | 14 source.gui.ui_main_window | 15 source.gui.ui_market_window | 16 source.gui.ui_order_window | 17 source.gui.ui_position_window | 18 source.gui.ui_strategy_window | 19 source.log.trade_recorder_base | 20 source.risk.risk_manager_base | 21 source.strategy.strategy_base | 22 source.account.account_event | 23 source.brokerage.backtest_brokerage | 24 source.data.backtest_data_feed_local | 25 source.data.backtest_data_feed_quandl | 26 source.data.backtest_data_feed_tushare | 27 source.data.bar_event | 28 source.data.historical_event | 29 source.data.live_data_feed | 30 source.data.tick_event | 31 source.log.trade_recorder | 32 source.order.fill_event | 33 source.order.order_event | 34 source.order.order_status_event | 35 source.position.contract_event | 36 source.position.position_event | 37 source.risk.risk_manager | 38 source.strategy.mystrategy.buy_and_hold_strategy | 39 source.strategy.mystrategy.moving_average_cross_strategy | 40 source.strategy.mystrategy.order_per_interval_strategy |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 source | ||||||||||||||||||||||||||||||||||||||||
| 2 source.account.account_manager | ||||||||||||||||||||||||||||||||||||||||
| 3 source.backtest_engine | ||||||||||||||||||||||||||||||||||||||||
| 4 source.brokerage.brokerage_base | ||||||||||||||||||||||||||||||||||||||||
| 5 source.data.data_board | ||||||||||||||||||||||||||||||||||||||||
| 6 source.data.data_feed_base | ||||||||||||||||||||||||||||||||||||||||
| 7 source.event.backtest_event_engine | ||||||||||||||||||||||||||||||||||||||||
| 8 source.event.client_mq | ||||||||||||||||||||||||||||||||||||||||
| 9 source.event.event | ||||||||||||||||||||||||||||||||||||||||
| 10 source.event.live_event_engine | ||||||||||||||||||||||||||||||||||||||||
| 11 source.gui.ui_account_window | ||||||||||||||||||||||||||||||||||||||||
| 12 source.gui.ui_fill_window | ||||||||||||||||||||||||||||||||||||||||
| 13 source.gui.ui_log_window | ||||||||||||||||||||||||||||||||||||||||
| 14 source.gui.ui_main_window | ||||||||||||||||||||||||||||||||||||||||
| 15 source.gui.ui_market_window | ||||||||||||||||||||||||||||||||||||||||
| 16 source.gui.ui_order_window | ||||||||||||||||||||||||||||||||||||||||
| 17 source.gui.ui_position_window | ||||||||||||||||||||||||||||||||||||||||
| 18 source.gui.ui_strategy_window | ||||||||||||||||||||||||||||||||||||||||
| 19 source.log.trade_recorder_base | ||||||||||||||||||||||||||||||||||||||||
| 20 source.risk.risk_manager_base | ||||||||||||||||||||||||||||||||||||||||
| 21 source.strategy.strategy_base | ||||||||||||||||||||||||||||||||||||||||
| 22 source.account.account_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 source.brokerage.backtest_brokerage | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 source.data.backtest_data_feed_local | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 source.data.backtest_data_feed_quandl | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 source.data.backtest_data_feed_tushare | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 source.data.bar_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 source.data.historical_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 source.data.live_data_feed | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 source.data.tick_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 source.log.trade_recorder | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 source.order.fill_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 source.order.order_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 source.order.order_status_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 source.position.contract_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 source.position.position_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 source.risk.risk_manager | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 source.strategy.mystrategy.buy_and_hold_strategy | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 source.strategy.mystrategy.moving_average_cross_strategy | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 source.strategy.mystrategy.order_per_interval_strategy | 1 |
22→9 source.account.account_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.account.account_event uses a type in source.event.event.
- The types involved
source.account.account_event.AccountEvent→source.event.event.Event
- Direction
- source.account.account_event uses source.event.event, so a change to source.event.event can break source.account.account_event, while a change to source.account.account_event can't break source.event.event.
- Position
- Below the diagonal: source.account.account_event uses a module listed above it, which is the healthy direction.
23→4 source.brokerage.backtest_brokerage uses source.brokerage.brokerage_base✕
- Connections
- 1 pair of types, where a type in source.brokerage.backtest_brokerage uses a type in source.brokerage.brokerage_base.
- The types involved
source.brokerage.backtest_brokerage.BacktestBrokerage→source.brokerage.brokerage_base.BrokerageBase
- Direction
- source.brokerage.backtest_brokerage uses source.brokerage.brokerage_base, so a change to source.brokerage.brokerage_base can break source.brokerage.backtest_brokerage, while a change to source.brokerage.backtest_brokerage can't break source.brokerage.brokerage_base.
- Position
- Below the diagonal: source.brokerage.backtest_brokerage uses a module listed above it, which is the healthy direction.
24→6 source.data.backtest_data_feed_local uses source.data.data_feed_base✕
- Connections
- 1 pair of types, where a type in source.data.backtest_data_feed_local uses a type in source.data.data_feed_base.
- The types involved
source.data.backtest_data_feed_local.BacktestDataFeedLocal→source.data.data_feed_base.DataFeedBase
- Direction
- source.data.backtest_data_feed_local uses source.data.data_feed_base, so a change to source.data.data_feed_base can break source.data.backtest_data_feed_local, while a change to source.data.backtest_data_feed_local can't break source.data.data_feed_base.
- Position
- Below the diagonal: source.data.backtest_data_feed_local uses a module listed above it, which is the healthy direction.
25→6 source.data.backtest_data_feed_quandl uses source.data.data_feed_base✕
- Connections
- 1 pair of types, where a type in source.data.backtest_data_feed_quandl uses a type in source.data.data_feed_base.
- The types involved
source.data.backtest_data_feed_quandl.BacktestDataFeedQuandl→source.data.data_feed_base.DataFeedBase
- Direction
- source.data.backtest_data_feed_quandl uses source.data.data_feed_base, so a change to source.data.data_feed_base can break source.data.backtest_data_feed_quandl, while a change to source.data.backtest_data_feed_quandl can't break source.data.data_feed_base.
- Position
- Below the diagonal: source.data.backtest_data_feed_quandl uses a module listed above it, which is the healthy direction.
26→6 source.data.backtest_data_feed_tushare uses source.data.data_feed_base✕
- Connections
- 1 pair of types, where a type in source.data.backtest_data_feed_tushare uses a type in source.data.data_feed_base.
- The types involved
source.data.backtest_data_feed_tushare.BacktestDataFeedTushare→source.data.data_feed_base.DataFeedBase
- Direction
- source.data.backtest_data_feed_tushare uses source.data.data_feed_base, so a change to source.data.data_feed_base can break source.data.backtest_data_feed_tushare, while a change to source.data.backtest_data_feed_tushare can't break source.data.data_feed_base.
- Position
- Below the diagonal: source.data.backtest_data_feed_tushare uses a module listed above it, which is the healthy direction.
27→9 source.data.bar_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.data.bar_event uses a type in source.event.event.
- The types involved
source.data.bar_event.BarEvent→source.event.event.Event
- Direction
- source.data.bar_event uses source.event.event, so a change to source.event.event can break source.data.bar_event, while a change to source.data.bar_event can't break source.event.event.
- Position
- Below the diagonal: source.data.bar_event uses a module listed above it, which is the healthy direction.
28→9 source.data.historical_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.data.historical_event uses a type in source.event.event.
- The types involved
source.data.historical_event.HistoricalEvent→source.event.event.Event
- Direction
- source.data.historical_event uses source.event.event, so a change to source.event.event can break source.data.historical_event, while a change to source.data.historical_event can't break source.event.event.
- Position
- Below the diagonal: source.data.historical_event uses a module listed above it, which is the healthy direction.
29→6 source.data.live_data_feed uses source.data.data_feed_base✕
- Connections
- 1 pair of types, where a type in source.data.live_data_feed uses a type in source.data.data_feed_base.
- The types involved
source.data.live_data_feed.LiveDataFeed→source.data.data_feed_base.DataFeedBase
- Direction
- source.data.live_data_feed uses source.data.data_feed_base, so a change to source.data.data_feed_base can break source.data.live_data_feed, while a change to source.data.live_data_feed can't break source.data.data_feed_base.
- Position
- Below the diagonal: source.data.live_data_feed uses a module listed above it, which is the healthy direction.
30→9 source.data.tick_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.data.tick_event uses a type in source.event.event.
- The types involved
source.data.tick_event.TickEvent→source.event.event.Event
- Direction
- source.data.tick_event uses source.event.event, so a change to source.event.event can break source.data.tick_event, while a change to source.data.tick_event can't break source.event.event.
- Position
- Below the diagonal: source.data.tick_event uses a module listed above it, which is the healthy direction.
31→19 source.log.trade_recorder uses source.log.trade_recorder_base✕
- Connections
- 1 pair of types, where a type in source.log.trade_recorder uses a type in source.log.trade_recorder_base.
- The types involved
source.log.trade_recorder.ExampleTradeRecorder→source.log.trade_recorder_base.AbstractTradeRecorder
- Direction
- source.log.trade_recorder uses source.log.trade_recorder_base, so a change to source.log.trade_recorder_base can break source.log.trade_recorder, while a change to source.log.trade_recorder can't break source.log.trade_recorder_base.
- Position
- Below the diagonal: source.log.trade_recorder uses a module listed above it, which is the healthy direction.
32→9 source.order.fill_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.order.fill_event uses a type in source.event.event.
- The types involved
source.order.fill_event.FillEvent→source.event.event.Event
- Direction
- source.order.fill_event uses source.event.event, so a change to source.event.event can break source.order.fill_event, while a change to source.order.fill_event can't break source.event.event.
- Position
- Below the diagonal: source.order.fill_event uses a module listed above it, which is the healthy direction.
33→9 source.order.order_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.order.order_event uses a type in source.event.event.
- The types involved
source.order.order_event.OrderEvent→source.event.event.Event
- Direction
- source.order.order_event uses source.event.event, so a change to source.event.event can break source.order.order_event, while a change to source.order.order_event can't break source.event.event.
- Position
- Below the diagonal: source.order.order_event uses a module listed above it, which is the healthy direction.
34→9 source.order.order_status_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.order.order_status_event uses a type in source.event.event.
- The types involved
source.order.order_status_event.OrderStatusEvent→source.event.event.Event
- Direction
- source.order.order_status_event uses source.event.event, so a change to source.event.event can break source.order.order_status_event, while a change to source.order.order_status_event can't break source.event.event.
- Position
- Below the diagonal: source.order.order_status_event uses a module listed above it, which is the healthy direction.
35→9 source.position.contract_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.position.contract_event uses a type in source.event.event.
- The types involved
source.position.contract_event.ContractEvent→source.event.event.Event
- Direction
- source.position.contract_event uses source.event.event, so a change to source.event.event can break source.position.contract_event, while a change to source.position.contract_event can't break source.event.event.
- Position
- Below the diagonal: source.position.contract_event uses a module listed above it, which is the healthy direction.
36→9 source.position.position_event uses source.event.event✕
- Connections
- 1 pair of types, where a type in source.position.position_event uses a type in source.event.event.
- The types involved
source.position.position_event.PositionEvent→source.event.event.Event
- Direction
- source.position.position_event uses source.event.event, so a change to source.event.event can break source.position.position_event, while a change to source.position.position_event can't break source.event.event.
- Position
- Below the diagonal: source.position.position_event uses a module listed above it, which is the healthy direction.
37→20 source.risk.risk_manager uses source.risk.risk_manager_base✕
- Connections
- 1 pair of types, where a type in source.risk.risk_manager uses a type in source.risk.risk_manager_base.
- The types involved
source.risk.risk_manager.PassThroughRiskManager→source.risk.risk_manager_base.RiskManagerBase
- Direction
- source.risk.risk_manager uses source.risk.risk_manager_base, so a change to source.risk.risk_manager_base can break source.risk.risk_manager, while a change to source.risk.risk_manager can't break source.risk.risk_manager_base.
- Position
- Below the diagonal: source.risk.risk_manager uses a module listed above it, which is the healthy direction.
38→21 source.strategy.mystrategy.buy_and_hold_strategy uses source.strategy.strategy_base✕
- Connections
- 1 pair of types, where a type in source.strategy.mystrategy.buy_and_hold_strategy uses a type in source.strategy.strategy_base.
- The types involved
source.strategy.mystrategy.buy_and_hold_strategy.BuyAndHoldStrategy→source.strategy.strategy_base.StrategyBase
- Direction
- source.strategy.mystrategy.buy_and_hold_strategy uses source.strategy.strategy_base, so a change to source.strategy.strategy_base can break source.strategy.mystrategy.buy_and_hold_strategy, while a change to source.strategy.mystrategy.buy_and_hold_strategy can't break source.strategy.strategy_base.
- Position
- Below the diagonal: source.strategy.mystrategy.buy_and_hold_strategy uses a module listed above it, which is the healthy direction.
39→21 source.strategy.mystrategy.moving_average_cross_strategy uses source.strategy.strategy_base✕
- Connections
- 1 pair of types, where a type in source.strategy.mystrategy.moving_average_cross_strategy uses a type in source.strategy.strategy_base.
- The types involved
source.strategy.mystrategy.moving_average_cross_strategy.MovingAverageCrossStrategy→source.strategy.strategy_base.StrategyBase
- Direction
- source.strategy.mystrategy.moving_average_cross_strategy uses source.strategy.strategy_base, so a change to source.strategy.strategy_base can break source.strategy.mystrategy.moving_average_cross_strategy, while a change to source.strategy.mystrategy.moving_average_cross_strategy can't break source.strategy.strategy_base.
- Position
- Below the diagonal: source.strategy.mystrategy.moving_average_cross_strategy uses a module listed above it, which is the healthy direction.
40→21 source.strategy.mystrategy.order_per_interval_strategy uses source.strategy.strategy_base✕
- Connections
- 1 pair of types, where a type in source.strategy.mystrategy.order_per_interval_strategy uses a type in source.strategy.strategy_base.
- The types involved
source.strategy.mystrategy.order_per_interval_strategy.OrderPerIntervalStrategy→source.strategy.strategy_base.StrategyBase
- Direction
- source.strategy.mystrategy.order_per_interval_strategy uses source.strategy.strategy_base, so a change to source.strategy.strategy_base can break source.strategy.mystrategy.order_per_interval_strategy, while a change to source.strategy.mystrategy.order_per_interval_strategy can't break source.strategy.strategy_base.
- Position
- Below the diagonal: source.strategy.mystrategy.order_per_interval_strategy 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED; Resolve the 1 No automated tests finding(s) in Code Coverage; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. | +34.4 pts | Low | REDACTED Scanning |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +34.4 pts | High | Code Coverage |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +7.3 pts | Medium | CI/CD gates |
| 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. | +4.9 pts | Medium | Architecture documentation |
| Resolve the 2 Off the main sequence finding(s) in Coupling. | +1.2 pts | Low | Coupling |
| Resolve the 1 Circular dependency finding(s) in Coupling. | +0.8 pts | Low | Coupling |
| Resolve the 1 Unstable project source/gui finding(s) in Coupling. | +0.8 pts | Low | Coupling |
| Swallowed exception (empty catch) | +1.2 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.9 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| source/position/position.py | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| source/brokerage/backtest_brokerage.py | 7.3 | Mixed | Explicit Debt: TodoComment |
| source/event/client_mq.py | 7.8 | Mixed | Cyclomatic Complexity: ClientMq._run (cyclomatic 19) |
| source/gui/ui_main_window.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| source/data/backtest_data_feed_local.py | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 3) |
| source/live_engine.py | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| source/performance/performance_manager.py | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| source/event/backtest_event_engine.py | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| source/gui/ui_account_window.py | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 4) |
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 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 38 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, 28 of 38 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
- D14 License Compliance — 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. Not scored — no dependency manifest this pass reads for licence data (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so it declares no third-party dependency closure to grade. A gap in the analyzer, NOT a finding that this repository's licences are compliant: a manifest in an ecosystem outside that list, or third-party code copied into the tree, is not read — so this dimension asserts nothing about this repository's licensing in either direction.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 20 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- 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 20 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 — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D20 ADR Quality — 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 ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository.
- 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.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (20 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 20 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- 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.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- 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 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 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.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found. Whether there is anything here to recover could NOT be determined: persistence is detected from deployment/container manifests and from dependency manifests, and neither was readable by this pass, so a data store this code opens directly — a file, an embedded database — would not be visible to it. The blindness is this analyzer's, not a finding that the repository holds no data. You can widen what we reach: keep the deployment/container manifest or a dependency manifest in this repository — or a link to the ops repo that holds the DR evidence — so the persistence probe has something to read.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- 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.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
- 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 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D13 REDACTED Scanning: REDACTED 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").
- 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.
- 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").
- 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.
- 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.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ClientMq._run at 19.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ClientMq._run (cyclomatic 19). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was ClientMq._run at 25.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with ClientMq._run (cognitive 25). — Refactoring it lifts Cognitive Complexity from 9.4 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
7 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with live_engine.py, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (14 lines × 3) finding(s) in Code Duplication — start with backtest_data_feed_local.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with position.py. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
13 production modules (source-import), 1 dependency cycle(s), 1 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 2 module(s) off the main sequence.
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Unstable project source/gui finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 25 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: source/event/client_mq.py (4×19=76)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with client_mq.py. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
5 deducted task-comment markers across 2932 LoC (0.1/KLoC) → score 9.8. 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 5 TodoComment finding(s) in Explicit Debt — start with backtest_brokerage.py (2), position.py, ui_main_window.py. — One of this dimension's main actionable groups (5 warning-level).
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues.
D35 · Change Coupling
No strong hidden change-coupling between production files.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
- The projects source/account → source/event → source/account (one cycle inside a mutually-dependent group of 5 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
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
What to do
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — source/strategy/strategy_base.py:39, source/gui/ui_strategy_window.py:40, source/event/client_mq.py:37, …
- `except` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — source/order/order_manager.py:99, source/order/order_manager.py:105
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Strong | Solid. |
| Architecture | 77% | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 0% | Critical — gated by D8, D13, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85% | Checked 2 of 5 | Strongest area. |
Not evidenced — 3 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
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 77 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: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
- 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) 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 on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported 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 on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
- D14 License Compliance — No dependency manifest found — no declared dependency closure to grade for licences
- 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.
- D19 Documentation Quality — D19 withholds "Documentation: empty section": 1 candidate(s) were measured and not published.
- D20 ADR Quality — Repository kind not determined
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python 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. 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, 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (2932 LoC, 56 module-visible types across 14 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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
- D9 Test Distribution — No test suite could be collected, so there is no unit/integration/end-to-end mix to read. Not applicable: the absence of tests is D8's reading (Code Coverage), and is counted there once.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's Python source (1 module(s), 69 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 was 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
- 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.
- X29 Per-element action decided by a fixed element — 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
- 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.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle
- Circular dependency
- No automated tests
Serious — 27 finding(s)
- Swallowed exception (empty catch) source/strategy/strategy_base.py:39
- Swallowed exception (empty catch) source/gui/ui_strategy_window.py:40
- Swallowed exception (empty catch) source/event/client_mq.py:37
- Swallowed exception (empty catch) source/event/client_mq.py:80
- Swallowed exception (empty catch) source/event/client_mq.py:88
- Swallowed exception (empty catch) source/data/tick_event.py:65
- TodoComment source/position/position.py:10
- TodoComment source/gui/ui_main_window.py:61
- TodoComment REDACTED:141
- TodoComment source/brokerage/backtest_brokerage.py:63
- TodoComment source/brokerage/backtest_brokerage.py:72
- Duplicated block (7 lines × 2) source/live_engine.py:24
- Duplicated block (7 lines × 2) REDACTED:55
- Off the main sequence: source/performance
- Off the main sequence: source/util
- Swallowed exception (caught, then discarded) source/order/order_manager.py:99
- Swallowed exception (caught, then discarded) source/order/order_manager.py:105
- ClientMq._run (cyclomatic 19) source/event/client_mq.py:25
- Hotspot: source/event/client_mq.py source/event/client_mq.py:25
- ClientMq._run (cognitive 25) source/event/client_mq.py:25
- Duplicated block (14 lines × 3) source/data/backtest_data_feed_local.py:75
- Duplicated block (11 lines × 2) source/position/position.py:41
- Duplicated block (5 lines × 2) source/performance/performance_manager.py:45
- Duplicated block (10 lines × 2) source/event/backtest_event_engine.py:77
- Duplicated block (8 lines × 4) source/gui/ui_account_window.py:31
- Unstable project source/gui
- No CI pipeline
Minor — 3 finding(s)
- REDACTED
- No ADRs
- No SAST
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-a4262493ce23488483d5715a84413292/history.json --exit-code 0 --source . | 2 | 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-a4262493ce23488483d5715a84413292/tree.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |