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.
Sign up free Scan another repo

jbarbre/Trade

https://github.com/jbarbre/Trade · scanned 2026-06-16 02:55 UTC (2 months ago)

115 raw signals (0 security + 115 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v2 · 99 actionable findings from 1 signal source. 16 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
74.2
/100
Security checks
74
0 findings
System graph
74
100.0% cov · 99 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 6 Medium 9 Low 81 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 99 Crowd 0 Layer: Software 28 Quality 32 Network 1 Frontend 1 Security 8 Cicd 1 Api 28
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 74.2/100 with 100.0% coverage. It contains 1854 nodes across 28 cross-layer flows, written primarily in mixed languages. Engine surfaced 115 findings — concentrated in quality (48), software (28), api (28). Risk profile is high: 0 critical, 6 high, 9 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 96 of 99 actionable findings. 115 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:206 SecretsClaude instruction
high System graph security auth conf 1.00 FastAPI POST `manual_fetch` without auth dependency — x_webhook.py:1224
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
x_webhook.py:1224 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `manual_truth_social_fetch` without auth dependency — x_webhook.py:1187
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
x_webhook.py:1187 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `receive_notification` without auth dependency — x_webhook.py:796
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
x_webhook.py:796 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `receive_truth_social_notification` without auth dependency — x_webhook.py:1046
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
x_webhook.py:1046 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `receive_x_ingest_heartbeat` without auth dependency — x_webhook.py:1025
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
x_webhook.py:1025 securityAuth fastapi unauth mutation
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in server.py:259
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
server.py:259 Cors wildcard
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — download_polymarket.py:274
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — forexcom_api.py:84
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — x_notification_poller.py:238
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph network Security conf 1.00 Privileged port 127 in use
Port 127 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
server.py Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 54 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 546 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 13 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: market_metadata.py:normalize_metadata_defaults, market_metadata.py:normalize_metadata This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
13 occurrences
repo-level (13 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: operator_alerts.py:now_ms, post_notification_store.py:now_ms, feed_probes.py:utc_now_ms This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: operator_alerts.py:iso_from_ms, post_notification_store.py:iso_from_ms, time_fidelity_orderbook_store.py:iso_from_ms, feed_probes.py:iso_from_ms This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: court_feeds.py:load_json, news_sites.py:load_json, paper_trader.py:load_json, policy_feeds.py:load_json This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why the…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `crypto_market_metadata_v1` in crypto_market_metadata.py:22
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `crypto_market_move_detector_state_v1` in crypto_market_move_detector.py:328
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `crypto_orderbook_snapshot_v1` in crypto_orderbook.py:168
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `crypto_paper_account_v1` in crypto_paper_trader.py:89
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `forex_market_metadata_v1` in forexcom_market_metadata.py:137
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `forex_market_move_detector_state_v1` in forex_market_move_detector.py:305
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `forexcom_paper_account_v1` in forexcom_paper_trader.py:87
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `operator_alert_resolution_index_v1` in operator_alert_resolution.py:195
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `scoring_process_trace_v1` in scoring_trace.py:9
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `source_registry_v1` in source_registry.py:1009
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `x_v2` in x_fetch.py:48
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: alert_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
operator_alerts.py:151
low System graph software Dead code conf 1.00 Possibly dead Python function: append_new_court_items
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
court_feeds.py:663
low System graph software Dead code conf 1.00 Possibly dead Python function: attach_control_metadata
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
market_metadata.py:517
low System graph software Dead code conf 1.00 Possibly dead Python function: call_codex_metadata_extractor
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
market_metadata.py:655
low System graph software Dead code conf 1.00 Possibly dead Python function: configured_feed_specs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
news_sites.py:787
low System graph software Dead code conf 1.00 Possibly dead Python function: default_metadata_model
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
market_metadata.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: expand_district
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
llm_scorer.py:1202
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_court_feeds
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
court_feeds.py:499
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_news_sites
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
news_sites.py:1525
low System graph software Dead code conf 1.00 Possibly dead Python function: format_markets_for_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
llm_scorer.py:4092
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
court_feeds.py:114
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
news_sites.py:672
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_endtag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
court_feeds.py:110
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_endtag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
news_sites.py:668
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_starttag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
court_feeds.py:106
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_starttag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
news_sites.py:664
low System graph software Dead code conf 1.00 Possibly dead Python function: load_manual_sources
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
source_registry.py:1038
low System graph software Dead code conf 1.00 Possibly dead Python function: load_market_family_requirements
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
source_registry.py:1033
low System graph software Dead code conf 1.00 Possibly dead Python function: load_source_registry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
source_registry.py:1026
low System graph software Dead code conf 1.00 Possibly dead Python function: market_information
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
forexcom_api.py:163
low System graph software Dead code conf 1.00 Possibly dead Python function: probe_court_feeds
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
court_feeds.py:538
low System graph software Dead code conf 1.00 Possibly dead Python function: probe_news_sites
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
news_sites.py:1568
low System graph software Dead code conf 1.00 Possibly dead Python function: route_court_event_to_markets
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
court_feeds.py:762
low System graph software Dead code conf 1.00 Possibly dead Python function: sibling_market_summaries
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
market_metadata.py:271
low System graph software Dead code conf 1.00 Possibly dead Python function: sleep_until_next
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
court_feeds.py:169
low System graph software Dead code conf 1.00 Possibly dead Python function: trigger_paper_trade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
x_webhook.py:534
low System graph software Dead code conf 1.00 Possibly dead Python function: write_metadata_cache
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
market_metadata.py:363
low System graph software Dead code conf 1.00 Possibly dead Python function: write_source_registry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
source_registry.py:1019
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`server.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/candles
`server.py` declares `GET /api/candles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/crypto/candles
`server.py` declares `GET /api/crypto/candles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/alert_history
`server.py` declares `GET /api/dashboard/alert_history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/candle_markets
`server.py` declares `GET /api/dashboard/candle_markets` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/market_candles
`server.py` declares `GET /api/dashboard/market_candles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/markets
`server.py` declares `GET /api/dashboard/markets` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/scoring_traces
`server.py` declares `GET /api/dashboard/scoring_traces` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/storage
`server.py` declares `GET /api/dashboard/storage` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/summary
`server.py` declares `GET /api/dashboard/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/date_range
`server.py` declares `GET /api/date_range` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/forex/candles
`server.py` declares `GET /api/forex/candles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/kalshi/candles
`server.py` declares `GET /api/kalshi/candles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/kalshi/date_range
`server.py` declares `GET /api/kalshi/date_range` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/kalshi/markets
`server.py` declares `GET /api/kalshi/markets` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/kalshi/posts
`server.py` declares `GET /api/kalshi/posts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/live_candles
`server.py` declares `GET /api/live_candles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ratings
`server.py` declares `GET /api/ratings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/trump_posts
`server.py` declares `GET /api/trump_posts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /webhook/status
`x_webhook.py` declares `GET /webhook/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/cancel_shutdown
`server.py` declares `POST /api/cancel_shutdown` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ratings
`server.py` declares `POST /api/ratings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/shutdown
`server.py` declares `POST /api/shutdown` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhook/fetch
`x_webhook.py` declares `POST /webhook/fetch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhook/notification
`x_webhook.py` declares `POST /webhook/notification` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhook/truthsocial/fetch
`x_webhook.py` declares `POST /webhook/truthsocial/fetch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhook/truthsocial/notification
`x_webhook.py` declares `POST /webhook/truthsocial/notification` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhook/x/heartbeat
`x_webhook.py` declares `POST /webhook/x/heartbeat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: crypto_replay_store.py (1322 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: news_sites.py (1711 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: paper_trader.py (4368 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: policy_feeds.py (1559 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server.py (7552 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: simulator.py (5885 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: x_webhook.py (1292 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/e0bb6e8e-af9a-4597-b1dc-3d1d68244485/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e0bb6e8e-af9a-4597-b1dc-3d1d68244485/

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.