tradingstrategy-ai/trade-executor

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

Scan timing: clone 1.38s · analysis 0.33s · 0.1 MB · GitHub API rate-limit (preflight)

https://github.com/tradingstrategy-ai/trade-executor · scanned 2026-06-05 13:00 UTC (5 days, 9 hours ago) · 10 languages

698 raw signals (8 security + 690 graph) 24th percentile · Unknown · System graph score 73 (lower by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 9 hours ago · v2 · 314 actionable findings from 2 signal sources. 39 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 306 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	30.0	0.15	4.50
`security_score`	87.5	0.25	21.88
`testing_score`	70.0	0.20	14.00
`documentation_score`	58.7	0.15	8.80
`practices_score`	70.0	0.15	10.50
`code_quality`	80.0	0.10	8.00
Overall		1.00	67.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 2 Medium 12 Low 230 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 306 Crowd 0 Layer: Quality 260 Security 3 Software 41 Api 1 Hardware 6 Frontend 1 Cicd 2

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 8 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `get_quantity_old` in tests/legacy/test_legacy_repa…

View all legacy markers findings →

Commented-out code 67 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (12 lines) in tests/conftest.py:91
info Commented-code block (7 lines) in tests/test_rebalance.py:1369
info Commented-code block (5 lines) in tests/test_state.py:1626
info Commented-code block (5 lines) in tests/backtest/test_forward_fill.py:72
info Commented-code block (5 lines) in tests/backtest/test_grid_search.py:904
info Commented-code block (6 lines) in tests/backtest/test_backtest_ema_crossover.py…
info Commented-code block (5 lines) in tests/cli/test_telegram_logging.py:44
info Commented-code block (8 lines) in tests/cli/test_cli_commands.py:190
info Commented-code block (10 lines) in tests/ethereum/polygon_forked/conftest.py:341
info Commented-code block (7 lines) in tests/ethereum/polygon_forked/1delta/test_one…
info Commented-code block (6 lines) in tests/ethereum/polygon_forked/1delta/test_one…
info Commented-code block (5 lines) in tests/ethereum/polygon_forked/generic-router/…

View all commented-out code findings →

Config drift 3 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

3 matching findings on this repo

low Possibly dead Python function: cell_5_chain_config scripts/profile_vault_of_vaults_notebook.py:76
info Commented-code block (10 lines) in tradeexecutor/ethereum/web3config.py:295
low Old/deprecated-named symbol `quoter_v2` in tradeexecutor/ethereum/lagoon/univer…

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/330d5596-8b67-4bf1-923c-29f10e45559b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/330d5596-8b67-4bf1-923c-29f10e45559b/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.