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.

rehnmark75/TradeSystemV1-Moved

https://github.com/rehnmark75/TradeSystemV1-Moved · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

456 raw signals (0 security + 456 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 426 actionable findings from 1 signal source. 30 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 · 426 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 17 High 95 Medium 65 Low 188 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 426 Crowd 0 Layer: Software 20 Frontend 4 Network 2 Hardware 12 Security 58 Cicd 1 Quality 223 Api 106

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

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 5 places

View all duplicates & near-duplicates findings →

Legacy markers 11 findings

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.

11 matching findings on this repo

low Very large file: worker/app/forex_scanner/archive/legacy_configs/config_ema_str…
info Commented-code block (6 lines) in worker/app/forex_scanner/archive/legacy_confi…
info Commented-code block (6 lines) in worker/app/forex_scanner/archive/legacy_confi…
info Commented-code block (10 lines) in worker/app/forex_scanner/archive/legacy_conf…
info Commented-code block (10 lines) in worker/app/forex_scanner/archive/legacy_conf…
info Commented-code block (6 lines) in worker/app/forex_scanner/archive/legacy_confi…
info Commented-code block (129 lines) in worker/app/forex_scanner/archive/legacy_con…
info Commented-code block (6 lines) in worker/app/forex_scanner/archive/legacy_confi…
low Old/deprecated-named symbol `_merge_enhanced_config_with_legacy` in worker/app/…
low Old/deprecated-named symbol `_validate_ema_signal_legacy` in worker/app/forex_s…
low Old/deprecated-named symbol `_calculate_confidence_legacy` in worker/app/forex_…

View all legacy markers findings →

Commented-out code 59 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 (7 lines) in prod-app/main.py:93
info Commented-code block (6 lines) in stock-scanner/app/stock_scanner/analysis/swin…
info Commented-code block (9 lines) in stock-scanner/app/stock_scanner/analysis/dayt…
info Commented-code block (7 lines) in stock-scanner/app/stock_scanner/services/auto…
info Commented-code block (5 lines) in stock-scanner/app/stock_scanner/services/intr…
info Commented-code block (5 lines) in worker/app/fx_xsec_momentum_probe.py:85
info Commented-code block (5 lines) in worker/app/htf_edge_probe.py:381
info Commented-code block (5 lines) in worker/app/trade_scan.py:647
info Commented-code block (5 lines) in worker/app/old_data/OldScans/pictureandchatgt…
info Commented-code block (7 lines) in worker/app/old_data/services/scanner_config.p…
info Commented-code block (6 lines) in worker/app/forex_scanner/backtest_cli.py:1570
info Commented-code block (5 lines) in worker/app/forex_scanner/monitoring/monitor_o…

View all commented-out code findings →

Config drift 33 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.

12 matching findings on this repo

critical Possible secret in prod-app/config.py prod-app/config.py:18
critical Possible secret in worker/app/old_data/services/scanner_config.py worker/app/old_data/services/scanner_config.py:1026
critical Possible secret in stream-app/config.py stream-app/config.py:6
critical Possible secret in streamlit/config.py streamlit/config.py:6
critical Possible secret in dev-app/config.py dev-app/config.py:80
low Very large file: worker/app/forex_scanner/archive/legacy_configs/config_ema_str…
low Very large file: worker/app/forex_scanner/configdata/strategies/config_smc_simp…
low Very large file: worker/app/forex_scanner/services/smc_simple_config_service.py…
low Very large file: streamlit/components/tabs/scanner_config_tab.py (1813 lines)
low Very large file: streamlit/components/tabs/smc_config_tab.py (2287 lines)
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:633
medium Agent authority lacks a verifier contract: .claude/agents/smc-simple-config-sch… .claude/agents/smc-simple-config-schema.md

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/a0235066-2b97-4ab8-8db8-c4dfafff4e44/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a0235066-2b97-4ab8-8db8-c4dfafff4e44/

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.