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.
111 of your 215 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 55.23s for a 60.1 MB repo slow.
  • Repobility's analysis ran in 8.59s after the clone landed.

freqtrade/freqtrade

https://github.com/freqtrade/freqtrade · scanned 2026-06-05 11:41 UTC (5 days, 11 hours ago) · 10 languages

603 raw signals (197 security + 406 graph) 11/13 scanners ran 90th percentile · Python · large (100-500K LoC) System graph score 63 (higher by 25)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 98.0 0.15 14.70
practices_score 94.0 0.15 14.10
code_quality 52.0 0.10 5.20
Overall 1.00 88.0
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 2 places repo-level
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 5 places
View all duplicates & near-duplicates findings →
Commented-out code 24 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 (5 lines) in tests/freqtradebot/test_freqtradebot.py:1660
  • info Commented-code block (7 lines) in tests/exchange/test_binance.py:1086
  • info Commented-code block (13 lines) in tests/exchange/test_exchange.py:4555
  • info Commented-code block (6 lines) in tests/optimize/test_backtest_detail.py:502
  • info Commented-code block (8 lines) in tests/optimize/test_backtesting.py:630
  • info Commented-code block (14 lines) in tests/persistence/test_persistence.py:796
  • info Commented-code block (5 lines) in freqtrade/freqtradebot.py:117
  • info Commented-code block (5 lines) in freqtrade/strategy/informative_decorator.py:1…
  • info Commented-code block (5 lines) in freqtrade/freqai/freqai_interface.py:152
  • info Commented-code block (13 lines) in freqtrade/freqai/RL/BaseEnvironment.py:385
  • info Commented-code block (5 lines) in freqtrade/templates/FreqaiExampleStrategy.py:…
  • info Commented-code block (5 lines) in freqtrade/templates/sample_hyperopt_loss.py:15
View all commented-out code findings →
Config drift 16 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
  • high [MINED131] pre-commit hook `https://github.com/pre-commit/mirrors-mypy` pinned … .pre-commit-config.yaml:15
  • high [MINED106] Phantom test coverage: test_pairlist_resolving_with_config_pl_not_ex… tests/test_configuration.py:1215
  • high [MINED106] Phantom test coverage: test_load_config_stoploss_exchange_limit_rati… tests/test_configuration.py:1111
  • high [MINED106] Phantom test coverage: test_load_config_file_exception: Test functio… tests/test_configuration.py:290
  • high [MINED106] Phantom test coverage: test_load_config_file_error: Test function `t… tests/test_configuration.py:83
  • high [MINED106] Phantom test coverage: test_load_config_incorrect_stake_amount: Test… tests/test_configuration.py:63
  • high [MINED106] Phantom test coverage: test_load_config_missing_attributes: Test fun… tests/test_configuration.py:49
  • low File has no detected symbols: docs/javascripts/config.js
  • low File has no detected symbols: freqtrade/config_schema/config_schema.py
  • low Very large file: tests/test_configuration.py (1623 lines)
  • low Very large file: freqtrade/config_schema/config_schema.py (1508 lines)
  • low Old/deprecated-named symbol `section_old` in freqtrade/configuration/deprecated…
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/155326e5-9f75-4622-9ba3-83af963d25db/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/155326e5-9f75-4622-9ba3-83af963d25db/

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.