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

Va3elina/moex-aggregator

https://github.com/Va3elina/moex-aggregator · scanned 2026-06-16 00:47 UTC (2 months, 1 week ago)

350 raw signals (13 security + 337 graph)

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

Complete repo analysis

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

JSON
Combined
54.6
/100
Security checks
55
7 findings
System graph
55
100.0% cov · 300 findings
Critical
2
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 2 High 41 Medium 34 Low 122 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 300 Crowd 0 Layer: Quality 171 Security 20 Software 19 Frontend 15 Network 1 Hardware 4 Api 77
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 54.6/100 with 100.0% coverage. It contains 4069 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 337 findings — concentrated in quality (202), api (77), software (19). Risk profile is high: 0 critical, 38 high, 53 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 199 of 307 actionable findings. 460 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.

critical Security checks quality Practices conf 0.82 9 occurrences Foundry mined mock as real or placeholder: Va3elina/moex-aggregator
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
9 occurrences
repo-level (9 hits)
critical Security checks security auth conf 0.78 6 occurrences Foundry mined security auth guardrail gaps: Va3elina/moex-aggregator
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
6 occurrences
repo-level (6 hits)
high Security checks quality Practices conf 0.84 27 occurrences Foundry mined bad chains: Va3elina/moex-aggregator
Comment chain pattern product: bad_chains Repo: Va3elina/moex-aggregator Thread: Va3elina/moex-aggregator#87 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, …
27 occurrences
repo-level (27 hits)
high Security checks quality Quality conf 0.76 2 occurrences Foundry mined schema ui api mismatch: Va3elina/moex-aggregator
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
2 occurrences
repo-level (2 hits)
high Security checks quality Testing conf 0.78 14 occurrences Foundry mined test ci gap after feedback: Va3elina/moex-aggregator
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_high_confi…
14 occurrences
repo-level (14 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/oauth/${providerId}/url (docs/design-system/project/reference/frontend/src/pages/LoginPage.tsx:110)
`docs/design-system/project/reference/frontend/src/pages/LoginPage.tsx:110` calls `GET /api/auth/oauth/${providerId}/url` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/oauth/<p>/url` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/oauth/${providerId}/url (frontend/src/pages/LoginPage.tsx:129)
`frontend/src/pages/LoginPage.tsx:129` calls `GET /api/auth/oauth/${providerId}/url` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/oauth/<p>/url` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/oauth/providers (docs/design-system/project/reference/frontend/src/pages/LoginPage.tsx:59)
`docs/design-system/project/reference/frontend/src/pages/LoginPage.tsx:59` calls `GET /api/auth/oauth/providers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/oauth/providers` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/oauth/providers (frontend/src/pages/LoginPage.tsx:61)
`frontend/src/pages/LoginPage.tsx:61` calls `GET /api/auth/oauth/providers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/oauth/providers` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/billing/features (frontend/src/contexts/TierFeaturesContext.tsx:103)
`frontend/src/contexts/TierFeaturesContext.tsx:103` calls `GET /api/billing/features` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/features` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/billing/history?limit=20 (frontend/src/pages/ProfilePage.tsx:126)
`frontend/src/pages/ProfilePage.tsx:126` calls `GET /api/billing/history?limit=20` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/history` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/billing/plans (frontend/src/pages/PricingPage.tsx:124)
`frontend/src/pages/PricingPage.tsx:124` calls `GET /api/billing/plans` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/plans` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/billing/status (frontend/src/pages/ProfilePage.tsx:118)
`frontend/src/pages/ProfilePage.tsx:118` calls `GET /api/billing/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/status` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/heatmap/prices (docs/design-system/project/reference/frontend/src/pages/HeatmapPage.tsx:209)
`docs/design-system/project/reference/frontend/src/pages/HeatmapPage.tsx:209` calls `GET /api/heatmap/prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heatmap/prices` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/heatmap/prices (frontend/src/pages/HeatmapPage.tsx:296)
`frontend/src/pages/HeatmapPage.tsx:296` calls `GET /api/heatmap/prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heatmap/prices` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/heatmap/stocks?size_by=value_1m&color_by=change_1m&group_by=none (docs/design-system/project/reference/frontend/src/pages/OverviewPage.tsx:94)
`docs/design-system/project/reference/frontend/src/pages/OverviewPage.tsx:94` calls `GET /api/heatmap/stocks?size_by=value_1m&color_by=change_1m&group_by=none` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/heatmap/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /logos/sprite-manifest.json (frontend/src/components/TickerLogo.tsx:53)
`frontend/src/components/TickerLogo.tsx:53` calls `GET /logos/sprite-manifest.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/logos/sprite-manifest.json` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /logos/sprite-manifest.json (frontend/src/hooks/usePrefetchLogos.ts:26)
`frontend/src/hooks/usePrefetchLogos.ts:26` calls `GET /logos/sprite-manifest.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/logos/sprite-manifest.json` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/change-password (docs/design-system/project/reference/frontend/src/pages/ProfilePage.tsx:58)
`docs/design-system/project/reference/frontend/src/pages/ProfilePage.tsx:58` calls `POST /api/auth/change-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/change-password` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/change-password (frontend/src/pages/ProfilePage.tsx:201)
`frontend/src/pages/ProfilePage.tsx:201` calls `POST /api/auth/change-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/change-password` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/login (frontend/src/pages/LoginPage.tsx:92)
`frontend/src/pages/LoginPage.tsx:92` calls `POST /api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/oauth/${provider} (docs/design-system/project/reference/frontend/src/pages/AuthCallback.tsx:123)
`docs/design-system/project/reference/frontend/src/pages/AuthCallback.tsx:123` calls `POST /api/auth/oauth/${provider}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/oauth/<p>` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/oauth/${provider} (frontend/src/pages/AuthCallback.tsx:153)
`frontend/src/pages/AuthCallback.tsx:153` calls `POST /api/auth/oauth/${provider}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/oauth/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/oauth/telegram (docs/design-system/project/reference/frontend/src/pages/AuthCallback.tsx:74)
`docs/design-system/project/reference/frontend/src/pages/AuthCallback.tsx:74` calls `POST /api/auth/oauth/telegram` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/oauth/telegram` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/oauth/telegram (frontend/src/pages/AuthCallback.tsx:74)
`frontend/src/pages/AuthCallback.tsx:74` calls `POST /api/auth/oauth/telegram` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/oauth/telegram` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/refresh (docs/design-system/project/reference/frontend/src/contexts/AuthContext.tsx:108)
`docs/design-system/project/reference/frontend/src/contexts/AuthContext.tsx:108` calls `POST /api/auth/refresh` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/refresh` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/refresh (docs/design-system/project/reference/frontend/src/contexts/AuthContext.tsx:40)
`docs/design-system/project/reference/frontend/src/contexts/AuthContext.tsx:40` calls `POST /api/auth/refresh` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/refresh` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/refresh (docs/design-system/project/reference/frontend/src/services/api.ts:42)
`docs/design-system/project/reference/frontend/src/services/api.ts:42` calls `POST /api/auth/refresh` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/refresh` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/refresh (frontend/src/services/api.ts:46)
`frontend/src/services/api.ts:46` calls `POST /api/auth/refresh` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/refresh` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/billing/${action} (frontend/src/pages/ProfilePage.tsx:151)
`frontend/src/pages/ProfilePage.tsx:151` calls `POST /api/billing/${action}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/billing/retention/accept (frontend/src/pages/ProfilePage.tsx:171)
`frontend/src/pages/ProfilePage.tsx:171` calls `POST /api/billing/retention/accept` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/retention/accept` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/billing/stub/simulate (frontend/src/pages/BillingStubPage.tsx:28)
`frontend/src/pages/BillingStubPage.tsx:28` calls `POST /api/billing/stub/simulate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/stub/simulate` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `exchange` without auth dependency — api/routers/extension.py:105
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/extension.py:105 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `google_oauth_callback` without auth dependency — api/routers/oauth.py:337
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/oauth.py:337 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `receive_csp_report` without auth dependency — api/routers/csp_report.py:41
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/csp_report.py:41 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_tokens` without auth dependency — api/routers/auth.py:442
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/auth.py:442 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stub_simulate` without auth dependency — api/routers/billing.py:508
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/billing.py:508 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `telegram_oauth_callback` without auth dependency — api/routers/oauth.py:500
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/oauth.py:500 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `vk_oauth_callback` without auth dependency — api/routers/oauth.py:344
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/oauth.py:344 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `yandex_oauth_callback` without auth dependency — api/routers/oauth.py:428
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/oauth.py:428 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in signals/detectors/ensemble.py:71
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
signals/detectors/ensemble.py:71 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in signals/research/explore.py:85
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
signals/research/explore.py:85 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in signals/research/explore_v2.py:69
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
signals/research/explore_v2.py:69 Tls verify false
medium Security checks quality Practices conf 0.62 46 occurrences Foundry mined assumption checks: Va3elina/moex-aggregator
Comment chain pattern product: assumption_checks Repo: Va3elina/moex-aggregator Thread: Va3elina/moex-aggregator#9 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts,…
46 occurrences
repo-level (46 hits)
medium Security checks quality Practices conf 0.70 19 occurrences Foundry mined unresolved feedback: Va3elina/moex-aggregator
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
19 occurrences
repo-level (19 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/design-system/project/reference/frontend/src/contexts/AuthContext.tsx:64
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 — docs/design-system/project/reference/frontend/src/pages/AuthCallback.tsx:74
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 — docs/design-system/project/reference/frontend/src/services/api.ts:69
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 — frontend/public/sw.js:51
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 — frontend/src/components/mobile/MobileAssetSearch.tsx:97
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 — frontend/src/components/TickerLogo.tsx:53
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 — frontend/src/pages/ApiDocsPage.tsx:705
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 — frontend/src/pages/AuthCallback.tsx:74
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 — frontend/src/pages/LoginPage.tsx:92
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 — frontend/src/services/api.ts:231
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 — signals/relay/cf-worker.js:29
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 authority lacks a verifier contract: .claude/skills/moex-fund-scha-backfill/references/uk-vim.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/moex-fund-scha-backfill/references/uk-vim.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/moex-responsive-audit/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/moex-responsive-audit/SKILL.md VerificationClaude instruction
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, lockfile. 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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 6 occurrences Frontend route `/auth/callback/google` has no Link/navigate to it — docs/design-system/project/reference/frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
6 occurrences
repo-level (6 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 17 occurrences Frontend route `/style-preview` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
17 occurrences
repo-level (17 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in api/main.py:117
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api/main.py:117 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/claude-design-flows-redesign.html:548
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/claude-design-flows-redesign.html:548 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in docs/design-system/project/reference/frontend/src/contexts/AuthContext.tsx:47
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
docs/design-system/project/reference/frontend/src/contexts/AuthContext.tsx:47 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in docs/design-system/project/reference/frontend/src/services/api.ts:49
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
docs/design-system/project/reference/frontend/src/services/api.ts:49 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/contexts/AuthContext.tsx:84
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/contexts/AuthContext.tsx:84 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/pages/embed/EmbedPage.tsx:71
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/pages/embed/EmbedPage.tsx:71 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/pages/LoginPage.tsx:149
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/pages/LoginPage.tsx:149 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/services/api.ts:53
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/services/api.ts:53 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/process-new-logos.py:23
`subprocess.run(...)` 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 — signals/detectors/ensemble.py:60
`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 — signals/research/explore.py:74
`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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 64 placeholder/mock markers across 41 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 3 in use
Port 3 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
backup_db.sh Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
4 test file(s) for 502 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 16 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_USER_ID`, `ALERT_BOT_USERNAME`, `ALLOWED_ORIGINS`, `COMMODITY_API_ROOT`, `DEV`, `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET`, `GOOGLE_REDIRECT_URI` + 8 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. 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 hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 620 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:4 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:25 containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/components/funds/FundDetailModal.tsx:298
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 11 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: tg_bot.py:main_keyboard, tg_bot.py:main 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.
11 occurrences
repo-level (11 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: main_orchestrator.py:get_moscow_time, Candles/fetch_candles_spot_realtime.py:get_moscow_time, Candles/fetch_candles_futures_realtime.py:get_moscow_time This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/a…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: api/middleware.py:dispatch, api/middleware.py:dispatch, api/middleware.py:dispatch, api/middleware.py:dispatch This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document …
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: api/billing/tbank.py:create_checkout, api/billing/tbank.py:charge, api/billing/provider.py:create_checkout, api/billing/provider.py:charge This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygien…
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: docs/design-system/project/reference/frontend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
docs/design-system/project/reference/frontend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `allowedLegacy` in frontend/src/pages/OpenInterestPage.tsx:468
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 `cmd_backup` in tg_bot.py:94
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 `diagnostics_v2` in signals/research/diagnostics_v2.py:13
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 `diagnostics_v2` in signals/scoring.py:26
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 `explore_v2` in signals/features.py:4
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 `explore_v2` in signals/research/build_calibration.py:4
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 `explore_v2` in signals/research/explore_v2.py:13
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 `frame_consent_v1` in frontend/src/components/CookieConsentBanner.tsx:5
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 `frame_consent_v1` in frontend/src/contexts/AnalyticsContext.tsx:37
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 `frame_consent_v1` in frontend/src/pages/ProfilePage.tsx:809
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 `frame_features_matrix_v1` in frontend/src/contexts/TierFeaturesContext.tsx:68
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 `frame_pwa_install_dismissed_v1` in frontend/src/components/mobile/MobilePWABanner.tsx:20
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 `frame_tour_seen_v2` in frontend/src/hooks/useFirstVisit.ts: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 `homepage_v2` in frontend/src/hooks/useExperiment.ts:5
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 `oi_anomaly_v2` in signals/research/oi_anomaly_v2.py:12
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 `PropsLegacy` in frontend/src/components/export/CsvExportButton.tsx:36
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 `research_v2` in signals/classification.py:17
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: cache_stats
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/cache.py:120
low System graph software Dead code conf 1.00 Possibly dead Python function: cap_gdp_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/exports.py:443
low System graph software Dead code conf 1.00 Possibly dead Python function: cap_m2_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/exports.py:475
low System graph software Dead code conf 1.00 Possibly dead Python function: check_rate_limit
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/public_api.py:179
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_ip_attempts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/security/brute_force.py:299
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_temp_password
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/security/password.py:139
low System graph software Dead code conf 1.00 Possibly dead Python function: is_weekend
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
moex_calendar.py:115
low System graph software Dead code conf 1.00 Possibly dead Python function: layer_daily
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/exports.py:285
low System graph software Dead code conf 1.00 Possibly dead Python function: layer_monthday_avg
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/exports.py:336
low System graph software Dead code conf 1.00 Possibly dead Python function: layer_monthly_avg
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/exports.py:313
low System graph software Dead code conf 1.00 Possibly dead Python function: layer_weekday_avg
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/exports.py:291
low System graph software Dead code conf 1.00 Possibly dead Python function: list_public_plans
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/billing/plans.py:106
low System graph software Dead code conf 1.00 Possibly dead Python function: log_account_locked
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/security/brute_force.py:186
low System graph software Dead code conf 1.00 Possibly dead Python function: optional_tier
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/billing/tiers.py:79
low System graph software Dead code conf 1.00 Possibly dead Python function: require_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/auth.py:161
low System graph software Dead code conf 1.00 Possibly dead Python function: require_pro
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/auth.py:172
low System graph software Dead code conf 1.00 Possibly dead Python function: require_tier
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/billing/tiers.py:54
low System graph software Dead code conf 1.00 Possibly dead Python function: send_verification_email
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/services/email.py:74
low System graph software Dead code conf 1.00 Possibly dead Python function: update_chart_caches
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/cache_updater.py:201
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 — frontend/scripts/prerender-meta.ts:181
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 — frontend/src/pages/ApiDocsPage.tsx:710
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: DELETE /experiments/{name}
`api/routers/analytics.py` declares `DELETE /experiments/{name}` 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: DELETE /token/{token_id}
`api/routers/extension.py` declares `DELETE /token/{token_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: DELETE /{key_id}
`api/routers/api_keys.py` declares `DELETE /{key_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: GET /
`api/routers/api_keys.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/health
`api/main.py` declares `GET /api/health` 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/info
`api/main.py` declares `GET /api/info` 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 /asset-history/{ticker}
`api/routers/fund_trades.py` declares `GET /asset-history/{ticker}` 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 /asset/{asset_name}
`api/routers/fund_trades.py` declares `GET /asset/{asset_name}` 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 /assets
`api/routers/fund_trades.py` declares `GET /assets` 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 /cohort
`api/routers/analytics.py` declares `GET /cohort` 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 /company-flows
`api/routers/fund_trades.py` declares `GET /company-flows` 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 /experiments
`api/routers/analytics.py` declares `GET /experiments` 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 /experiments/{name}/assign
`api/routers/analytics.py` declares `GET /experiments/{name}/assign` 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 /fund/{ticker}
`api/routers/fund_trades.py` declares `GET /fund/{ticker}` 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 /funds
`api/routers/fund_trades.py` declares `GET /funds` 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 /funnel
`api/routers/analytics.py` declares `GET /funnel` 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 /guest-limits
`api/routers/auth.py` declares `GET /guest-limits` 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 /heatmap.csv
`api/routers/exports.py` declares `GET /heatmap.csv` 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 /imoex
`api/routers/heatmap.py` declares `GET /imoex` 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 /intervals/{sectype}
`api/routers/chart.py` declares `GET /intervals/{sectype}` 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 /intraday-assets
`api/routers/open_interest.py` declares `GET /intraday-assets` 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 /intraday/{ticker}
`api/routers/fund_trades.py` declares `GET /intraday/{ticker}` 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 /me
`api/routers/auth.py` declares `GET /me` 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 /movers
`api/routers/fund_trades.py` declares `GET /movers` 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 /prices
`api/routers/heatmap.py` declares `GET /prices` 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 /realtime
`api/routers/analytics.py` declares `GET /realtime` 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 /snapshot/{ticker}
`api/routers/fund_trades.py` declares `GET /snapshot/{ticker}` 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 /snapshots/{ticker}
`api/routers/fund_trades.py` declares `GET /snapshots/{ticker}` 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 /stats
`api/routers/analytics.py` declares `GET /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: GET /stocks
`api/routers/heatmap.py` declares `GET /stocks` 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 /token
`api/routers/extension.py` declares `GET /token` 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 /usage
`api/routers/api_keys.py` declares `GET /usage` 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 /users
`api/routers/analytics.py` declares `GET /users` 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 /users/{user_id}
`api/routers/analytics.py` declares `GET /users/{user_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: GET /{path:path}
`api/main.py` declares `GET /{path:path}` 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 /{sec_id}
`api/routers/chart.py` declares `GET /{sec_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: GET /{sectype}
`api/routers/open_interest.py` declares `GET /{sectype}` 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/routers/api_keys.py` declares `POST /` 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 /add-email
`api/routers/auth.py` declares `POST /add-email` 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 /change-password
`api/routers/auth.py` declares `POST /change-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: POST /event
`api/routers/analytics.py` declares `POST /event` 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 /exchange
`api/routers/extension.py` declares `POST /exchange` 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 /experiments
`api/routers/analytics.py` declares `POST /experiments` 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 /login
`api/routers/auth.py` declares `POST /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: POST /logout
`api/routers/auth.py` declares `POST /logout` 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 /refresh
`api/routers/auth.py` declares `POST /refresh` 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 /register
`api/routers/auth.py` declares `POST /register` 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 /resend-verification
`api/routers/auth.py` declares `POST /resend-verification` 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 /token
`api/routers/extension.py` declares `POST /token` 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 /verify-email
`api/routers/auth.py` declares `POST /verify-email` 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: api/billing/service.py (1027 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: api/routers/fund_trades.py (1625 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Candles/fetch_candles_futures_realtime.py (1352 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: docs/design-system/project/reference/frontend/src/components/SimpleChart.tsx (1284 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: docs/handoff/SimpleChart.tsx (1286 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/public/videos/funds-catalog/seg002.ts (992 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/public/videos/oi/seg000.ts (1483 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/public/videos/strength/seg000.ts (1227 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/funds/FundDetailModal.tsx (1030 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/mobile/MobileChart.tsx (1115 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/SimpleChart.tsx (1730 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/ApiDocsPage.tsx (2241 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/FundTradesPage.tsx (1847 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/mobile/MobileFundTradesPage.tsx (1777 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/mobile/MobileSeasonalityPage.tsx (1206 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/OpenInterestPage.tsx (887 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/SeasonalityPage.tsx (1020 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/services/api.ts (1770 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: main_orchestrator.py (1202 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: sandbox/app.py (970 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/0b6ab556-79c8-4245-a7f1-dc736033ac19/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0b6ab556-79c8-4245-a7f1-dc736033ac19/

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.