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.

82beye/BarroAiTrade

https://github.com/82beye/BarroAiTrade · scanned 2026-06-17 01:13 UTC (1 month, 2 weeks ago)

206 raw signals (0 security + 206 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -30.9 (diff) · 187 actionable findings from 1 signal source. 19 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 · 187 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 18 Medium 23 Low 126 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 187 Crowd 0 Layer: Software 18 Frontend 2 Network 11 Security 16 Cicd 2 Quality 106 Api 32

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

4 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 8 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.

8 matching findings on this repo

low File has no detected symbols: backend/db/_legacy_sqlite.py
low Very large file: backend/legacy_scalping/main.py (2419 lines)
low Very large file: backend/legacy_scalping/execution/kiwoom_api.py (1569 lines)
medium Agent authority lacks a verifier contract: backend/legacy_scalping/SKILL.md backend/legacy_scalping/SKILL.md
low Old/deprecated-named symbol `test_c8_from_legacy` in backend/tests/strategy/tes…
low Old/deprecated-named symbol `sim_legacy` in backend/tests/backtester/test_intra…
info Commented-code block (13 lines) in backend/legacy_scalping/strategy/scalping_te…
low Old/deprecated-named symbol `from_legacy` in backend/models/strategy.py:47

View all legacy markers findings →

Commented-out code 19 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 (6 lines) in backend/tests/strategy/test_short_term_high_e…
info Commented-code block (5 lines) in backend/tests/journal/test_active_positions.p…
info Commented-code block (5 lines) in backend/tests/gateway/test_kiwoom_native_rank…
info Commented-code block (5 lines) in backend/api/routes/signals.py:71
info Commented-code block (13 lines) in backend/legacy_scalping/strategy/scalping_te…
info Commented-code block (5 lines) in backend/models/strategy.py:144
info Commented-code block (5 lines) in backend/core/orchestrator.py:43
info Commented-code block (6 lines) in backend/core/supertrend_auto_trader.py:77
info Commented-code block (7 lines) in backend/core/strategy/f_zone.py:58
info Commented-code block (5 lines) in backend/core/strategy/swing_38.py:50
info Commented-code block (9 lines) in backend/core/strategy/supertrend.py:244
info Commented-code block (9 lines) in backend/core/strategy/gold_zone.py:50

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

high FastAPI PUT `update_config` without auth dependency — backend/api/routes/config… backend/api/routes/config.py:58

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/57b411dc-3d08-4b14-8981-74566226a011/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/57b411dc-3d08-4b14-8981-74566226a011/

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.