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

strikegex/gex-heatmap

https://github.com/strikegex/gex-heatmap · scanned 2026-06-16 00:23 UTC (2 months, 2 weeks ago)

151 raw signals (0 security + 151 graph)

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

Complete repo analysis

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

JSON
Combined
66.4
/100
Security checks
66
0 findings
System graph
66
88.9% cov · 139 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 0 Medium 26 Low 95 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 139 Crowd 0 Layer: Software 19 Frontend 6 Security 17 Quality 47 Api 50
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 66.4/100 with 88.9% coverage. It contains 3512 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 151 findings — concentrated in quality (59), api (50), software (19). Risk profile is low: 0 critical, 0 high, 26 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 121 of 139 actionable findings. 151 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/account.js:151
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/alerts.js:37
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/core.js:242
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/heatmap.js:40
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/perf.js:25
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — static/js/spx-journal.js:34
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
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. 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 quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in chrome-extension/content.js:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
chrome-extension/content.js:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in chrome-extension/popup.js:130
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
chrome-extension/popup.js:130 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/account.js:35
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/account.js:35 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/alerts.js:30
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/alerts.js:30 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/chart.js:777
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/chart.js:777 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/commander.js:64
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/commander.js:64 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/core.js:331
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/core.js:331 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/heatmap.js:51
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/heatmap.js:51 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/history.js:37
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/history.js:37 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/ic-simulator.js:237
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/ic-simulator.js:237 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/ladder.js:194
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/ladder.js:194 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/perf.js:35
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/perf.js:35 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/spx-journal.js:154
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/spx-journal.js:154 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in static/js/strike-stack.js:209
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
static/js/strike-stack.js:209 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in static/js/account.js:284
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
static/js/account.js:284 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in static/js/core.js:427
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
static/js/core.js:427 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in static/js/spx-journal.js:60
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
static/js/spx-journal.js:60 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — gex_fetcher.py:57
`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
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 67 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — static/js/alerts.js:34
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — static/js/ic-simulator.js:138
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: gex_fetcher.py:is_weekly, gex_fetcher.py:is_weekly 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.
10 occurrences
repo-level (10 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: gex_strategies.py:should_enter, gex_strategies.py:should_enter, gex_strategies.py:should_enter, gex_strategies.py:should_enter This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolid…
4 occurrences
repo-level (4 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 `cs_old` in tests/test_signup_flow.py:97
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 `data_copy` in state.py:1416
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 `gex_account_prefs_v1` in static/js/core.js: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 `mem_old` in tests/test_auth.py:303
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 `mem_v2` in tests/test_webhooks.py:170
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 `test_get_gex_data_returns_copy` in tests/test_state.py:72
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: alerts_check_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:869
low System graph software Dead code conf 1.00 Possibly dead Python function: apply_learning_adjustments
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gex_autoresearch.py:1687
low System graph software Dead code conf 1.00 Possibly dead Python function: backfill_king_daily_close
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gex_db.py:3173
low System graph software Dead code conf 1.00 Possibly dead Python function: db_get_email_lead_count
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gex_db.py:4944
low System graph software Dead code conf 1.00 Possibly dead Python function: db_list_affiliates
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gex_db.py:5065
low System graph software Dead code conf 1.00 Possibly dead Python function: deco
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
middleware/auth.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: discord_auto_post_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/discord_posts.py:368
low System graph software Dead code conf 1.00 Possibly dead Python function: email_queue_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:641
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_loop_0dte
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:223
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_loop_all
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:538
low System graph software Dead code conf 1.00 Possibly dead Python function: live_price_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:437
low System graph software Dead code conf 1.00 Possibly dead Python function: membership_expiry_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:652
low System graph software Dead code conf 1.00 Possibly dead Python function: safe_jsonify
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
middleware/security.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: schwab_sync_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:734
low System graph software Dead code conf 1.00 Possibly dead Python function: set_king_streak
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
state.py:1799
low System graph software Dead code conf 1.00 Possibly dead Python function: snapshot_retention_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:713
low System graph software Dead code conf 1.00 Possibly dead Python function: update_gex_data_recalc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
state.py:1398
low System graph software Dead code conf 1.00 Possibly dead Python function: update_member_field
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
state.py:1598
low System graph software Dead code conf 1.00 Possibly dead Python function: weekend_wallst_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/fetch_loops.py:1047
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — chrome-extension/background.js:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — static/js/core.js:1847
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — static/js/heatmap.js:49
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/auto-login
`blueprints/auth.py` declares `ANY /api/auto-login` 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: ANY /api/autoresearch/backfill-accuracy
`blueprints/knowledge.py` declares `ANY /api/autoresearch/backfill-accuracy` 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: ANY /api/autoresearch/brief
`blueprints/knowledge.py` declares `ANY /api/autoresearch/brief` 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: ANY /api/autoresearch/evaluate
`blueprints/knowledge.py` declares `ANY /api/autoresearch/evaluate` 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: ANY /api/autoresearch/evolve
`blueprints/knowledge.py` declares `ANY /api/autoresearch/evolve` 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: ANY /api/autoresearch/morning-analysis
`blueprints/knowledge.py` declares `ANY /api/autoresearch/morning-analysis` 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: ANY /api/autoresearch/progress
`blueprints/knowledge.py` declares `ANY /api/autoresearch/progress` 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: ANY /api/autoresearch/record
`blueprints/knowledge.py` declares `ANY /api/autoresearch/record` 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: ANY /api/autoresearch/validate-trade
`blueprints/knowledge.py` declares `ANY /api/autoresearch/validate-trade` 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: ANY /api/autoresearch/validations
`blueprints/knowledge.py` declares `ANY /api/autoresearch/validations` 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: ANY /api/backtest/strategies
`blueprints/knowledge.py` declares `ANY /api/backtest/strategies` 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: ANY /api/checkout
`blueprints/stripe_pay.py` declares `ANY /api/checkout` 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: ANY /api/checkout/confirm
`blueprints/stripe_pay.py` declares `ANY /api/checkout/confirm` 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: ANY /api/gex-preview
`blueprints/gex_api.py` declares `ANY /api/gex-preview` 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: ANY /api/gex/accuracy
`blueprints/gex_api.py` declares `ANY /api/gex/accuracy` 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: ANY /api/gex/symbol-search
`blueprints/gex_api.py` declares `ANY /api/gex/symbol-search` 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: ANY /api/journal
`blueprints/knowledge.py` declares `ANY /api/journal` 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: ANY /api/journal/<trade_date>/outcome
`blueprints/knowledge.py` declares `ANY /api/journal/<trade_date>/outcome` 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: ANY /api/journal/recent
`blueprints/knowledge.py` declares `ANY /api/journal/recent` 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: ANY /api/journal/similar
`blueprints/knowledge.py` declares `ANY /api/journal/similar` 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: ANY /api/journal/stats
`blueprints/knowledge.py` declares `ANY /api/journal/stats` 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: ANY /api/member/claim-password
`blueprints/auth.py` declares `ANY /api/member/claim-password` 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: ANY /api/member/reset-password
`blueprints/auth.py` declares `ANY /api/member/reset-password` 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: ANY /api/opening-baseline
`blueprints/gex_api.py` declares `ANY /api/opening-baseline` 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: ANY /api/rolling-baseline
`blueprints/gex_api.py` declares `ANY /api/rolling-baseline` 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: ANY /api/signals/evaluate
`blueprints/knowledge.py` declares `ANY /api/signals/evaluate` 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: ANY /api/spx-journal/comparable-setups
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/comparable-setups` 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: ANY /api/spx-journal/edge
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/edge` 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: ANY /api/spx-journal/events
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/events` 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: ANY /api/spx-journal/projection
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/projection` 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: ANY /api/spx-journal/settings
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/settings` 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: ANY /api/spx-journal/sizing
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/sizing` 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: ANY /api/spx-journal/stats
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/stats` 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: ANY /api/spx-journal/today
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/today` 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: ANY /api/spx-journal/today/entry-exit
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/today/entry-exit` 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: ANY /api/spx-journal/today/intraday-snapshot
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/today/intraday-snapshot` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/spx-journal/today/post-mortem
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/today/post-mortem` 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: ANY /api/spx-journal/today/skip
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/today/skip` 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: ANY /api/spx-journal/trades
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/trades` 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: ANY /api/spx-journal/trades/<int:trade_id>
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/trades/<int:trade_id>` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/spx-journal/trades/<int:trade_id>/confirm
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/trades/<int:trade_id>/confirm` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/spx-journal/trades/<int:trade_id>/skip
`blueprints/spx_journal.py` declares `ANY /api/spx-journal/trades/<int:trade_id>/skip` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/stripe/webhook
`blueprints/stripe_pay.py` declares `ANY /api/stripe/webhook` 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: ANY /api/trades/<int:trade_id>
`blueprints/knowledge.py` declares `ANY /api/trades/<int:trade_id>` 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: ANY /api/tv/generate-key
`blueprints/tv_api.py` declares `ANY /api/tv/generate-key` 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: ANY /api/tv/levels
`blueprints/tv_api.py` declares `ANY /api/tv/levels` 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: ANY /api/tv/revoke-key
`blueprints/tv_api.py` declares `ANY /api/tv/revoke-key` 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: ANY /api/tv/strikes
`blueprints/tv_api.py` declares `ANY /api/tv/strikes` 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: ANY /simulator
`blueprints/spx_journal.py` declares `ANY /simulator` 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: ANY /spx-journal
`blueprints/spx_journal.py` declares `ANY /spx-journal` 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: gex_autoresearch.py (1787 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: gex_db.py (5805 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: gex_fetcher.py (1714 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: schwab_sync.py (1435 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/commander.py (1496 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: state.py (1855 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: static/js/core.js (2236 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: static/js/spx-journal.js (1915 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_gex_db.py (1332 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_spx_journal.py (1589 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/f7e4211a-d802-48a5-9500-ef1aad0adfab/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f7e4211a-d802-48a5-9500-ef1aad0adfab/

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.