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

AI-Isaiah/Quantalyze

https://github.com/AI-Isaiah/Quantalyze · scanned 2026-06-17 01:21 UTC (1 month, 2 weeks ago)

965 raw signals (0 security + 965 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -20.7 (diff) · 956 actionable findings from 1 signal source. 9 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
56.0
/100
Security checks
56
0 findings
System graph
56
100.0% cov · 956 findings
Critical
8
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 8 High 86 Medium 48 Low 129 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 956 Crowd 0 Layer: Software 1 Frontend 36 Network 1 Hardware 2 Security 30 Cicd 1 Quality 804 Api 81
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 56.0/100 with 100.0% coverage. It contains 10208 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 965 findings — concentrated in quality (811), api (81), frontend (36). Risk profile is high: 10 critical, 86 high, 48 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 260 of 956 actionable findings. 965 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 System graph security Secrets conf 1.00 Possible secret in e2e/helpers/discovery-selectors.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
e2e/helpers/discovery-selectors.ts:45
critical System graph security Secrets conf 1.00 Possible secret in scripts/seed-full-app-demo.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/seed-full-app-demo.ts:46
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/strategies/draft/${strategyId} (src/app/(dashboard)/strategies/new/wizard/WizardClient.tsx:470)
`src/app/(dashboard)/strategies/new/wizard/WizardClient.tsx:470` calls `DELETE /api/strategies/draft/${strategyId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/strategies/draft/<p>` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/compute-jobs?${params.toString()} (src/components/admin/ComputeJobsTable.tsx:94)
`src/components/admin/ComputeJobsTable.tsx:94` calls `GET /api/admin/compute-jobs?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/compute-jobs` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/match/allocators (src/components/admin/MatchQueueIndex.tsx:51)
`src/components/admin/MatchQueueIndex.tsx:51` calls `GET /api/admin/match/allocators` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/match/allocators` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/match/eval?${params.toString()} (src/components/admin/MatchEvalDashboard.tsx:59)
`src/components/admin/MatchEvalDashboard.tsx:59` calls `GET /api/admin/match/eval?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/match/eval` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/match/kill-switch (src/components/admin/MatchQueueIndex.tsx:52)
`src/components/admin/MatchQueueIndex.tsx:52` calls `GET /api/admin/match/kill-switch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/match/kill-switch` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/alerts/critical?portfolio_id=${encodeURIComponent(portfolioId)} (src/app/(dashboard)/allocations/components/AlertBanner.tsx:37)
`src/app/(dashboard)/allocations/components/AlertBanner.tsx:37` calls `GET /api/alerts/critical?portfolio_id=${encodeURIComponent(portfolioId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/alerts/critical` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/bridge/outcome/${outcome.id}/curves (src/app/(dashboard)/allocations/widgets/outcomes/OutcomesWidget.tsx:369)
`src/app/(dashboard)/allocations/widgets/outcomes/OutcomesWidget.tsx:369` calls `GET /api/bridge/outcome/${outcome.id}/curves` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bridge/outcome/<p>/curves` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/bridge/outcome/{id}/curves (src/app/(dashboard)/allocations/widgets/outcomes/outcomes.test.tsx:435)
`src/app/(dashboard)/allocations/widgets/outcomes/outcomes.test.tsx:435` calls `GET /api/bridge/outcome/{id}/curves` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bridge/outcome/<p>/curves` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/audit-log/export (src/app/(dashboard)/profile/components/AuditLogSubsection.tsx:35)
`src/app/(dashboard)/profile/components/AuditLogSubsection.tsx:35` calls `GET /api/me/audit-log/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/me/audit-log/export` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/notes?scope_kind=bridge_outcome&scope_ref=${encodeURIComponent(outcomeId)} (src/components/notes/BridgeOutcomeNoteSection.tsx:49)
`src/components/notes/BridgeOutcomeNoteSection.tsx:49` calls `GET /api/notes?scope_kind=bridge_outcome&scope_ref=${encodeURIComponent(outcomeId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/notes` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/notes?scope_kind=holding&scope_ref=${encodeURIComponent(scope_ref)} (src/app/(dashboard)/allocations/components/HoldingDetail.tsx:90)
`src/app/(dashboard)/allocations/components/HoldingDetail.tsx:90` calls `GET /api/notes?scope_kind=holding&scope_ref=${encodeURIComponent(scope_ref)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/notes` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/notes?scope_kind=holding&scope_ref=${encodeURIComponent(scope_ref)} (src/components/notes/HoldingNoteRow.tsx:158)
`src/components/notes/HoldingNoteRow.tsx:158` calls `GET /api/notes?scope_kind=holding&scope_ref=${encodeURIComponent(scope_ref)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/notes` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/strategies/browse (src/app/(dashboard)/allocations/components/StrategyBrowseDrawer.tsx:160)
`src/app/(dashboard)/allocations/components/StrategyBrowseDrawer.tsx:160` calls `GET /api/strategies/browse` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/strategies/browse` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/strategies/browse (src/app/(dashboard)/allocations/components/StrategyBrowseDrawer.tsx:69)
`src/app/(dashboard)/allocations/components/StrategyBrowseDrawer.tsx:69` calls `GET /api/strategies/browse` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/strategies/browse` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /x (tools/eslint-plugin-quantalyze/tests/no-raw-localstorage.test.ts:26)
`tools/eslint-plugin-quantalyze/tests/no-raw-localstorage.test.ts:26` calls `GET /x` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/x` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/notes (src/components/notes/useNoteAutoSave.ts:74)
`src/components/notes/useNoteAutoSave.ts:74` calls `PATCH /api/notes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/notes` 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: PATCH /api/portfolio-alerts (src/components/portfolio/AlertsList.tsx:34)
`src/components/portfolio/AlertsList.tsx:34` calls `PATCH /api/portfolio-alerts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/portfolio-alerts` 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/account/deletion-request (src/components/auth/DeleteAccountButton.tsx:20)
`src/components/auth/DeleteAccountButton.tsx:20` calls `POST /api/account/deletion-request` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/account/deletion-request` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/allocator-approve (src/components/admin/AdminTabs.tsx:564)
`src/components/admin/AdminTabs.tsx:564` calls `POST /api/admin/allocator-approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/allocator-approve` 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/admin/allocators/${allocatorId}/holdings (src/components/admin/SendIntroPanel.tsx:44)
`src/components/admin/SendIntroPanel.tsx:44` calls `POST /api/admin/allocators/${allocatorId}/holdings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/allocators/<p>/holdings` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/deletion-requests/${encodeURIComponent(requestId)}/approve (src/components/admin/DeletionRequestActions.tsx:49)
`src/components/admin/DeletionRequestActions.tsx:49` calls `POST /api/admin/deletion-requests/${encodeURIComponent(requestId)}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/deletion-requests/<p>/appr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/deletion-requests/${encodeURIComponent(requestId)}/reject (src/components/admin/DeletionRequestActions.tsx:82)
`src/components/admin/DeletionRequestActions.tsx:82` calls `POST /api/admin/deletion-requests/${encodeURIComponent(requestId)}/reject` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/deletion-requests/<p>/rejec…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/for-quants-leads/process (src/components/admin/ForQuantsLeadsTable.tsx:66)
`src/components/admin/ForQuantsLeadsTable.tsx:66` calls `POST /api/admin/for-quants-leads/process` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/for-quants-leads/process` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/intro-request (src/components/admin/AdminTabs.tsx:187)
`src/components/admin/AdminTabs.tsx:187` calls `POST /api/admin/intro-request` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/intro-request` 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/admin/intro-request (src/components/admin/AdminTabs.tsx:314)
`src/components/admin/AdminTabs.tsx:314` calls `POST /api/admin/intro-request` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/intro-request` 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/admin/manager-approve (src/components/admin/AdminTabs.tsx:612)
`src/components/admin/AdminTabs.tsx:612` calls `POST /api/admin/manager-approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/manager-approve` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/match/decisions (src/components/admin/AllocatorMatchQueue.tsx:240)
`src/components/admin/AllocatorMatchQueue.tsx:240` calls `POST /api/admin/match/decisions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/match/decisions` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/match/kill-switch (src/components/admin/MatchQueueIndex.tsx:146)
`src/components/admin/MatchQueueIndex.tsx:146` calls `POST /api/admin/match/kill-switch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/match/kill-switch` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/match/kill-switch (src/components/admin/MatchQueueIndex.tsx:216)
`src/components/admin/MatchQueueIndex.tsx:216` calls `POST /api/admin/match/kill-switch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/match/kill-switch` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/match/recompute (src/components/admin/AllocatorMatchQueue.tsx:218)
`src/components/admin/AllocatorMatchQueue.tsx:218` calls `POST /api/admin/match/recompute` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/match/recompute` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/notify-submission (src/components/strategy/StrategyActions.tsx:41)
`src/components/strategy/StrategyActions.tsx:41` calls `POST /api/admin/notify-submission` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/notify-submission` 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/admin/partner-import (src/app/(dashboard)/admin/partner-import/page.tsx:61)
`src/app/(dashboard)/admin/partner-import/page.tsx:61` calls `POST /api/admin/partner-import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/partner-import` 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/admin/strategy-review (src/components/admin/AdminTabs.tsx:363)
`src/components/admin/AdminTabs.tsx:363` calls `POST /api/admin/strategy-review` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/strategy-review` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/strategy-review (src/components/admin/AdminTabs.tsx:386)
`src/components/admin/AdminTabs.tsx:386` calls `POST /api/admin/strategy-review` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/strategy-review` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/users/${encodeURIComponent(targetUserId)}/roles (src/components/admin/UserRolesPanel.tsx:97)
`src/components/admin/UserRolesPanel.tsx:97` calls `POST /api/admin/users/${encodeURIComponent(targetUserId)}/roles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/<p>/roles` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/allocator/holdings/sync (src/components/exchanges/AllocatorExchangeManager.tsx:336)
`src/components/exchanges/AllocatorExchangeManager.tsx:336` calls `POST /api/allocator/holdings/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/allocator/holdings/sync` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/allocator/holdings/sync (src/components/exchanges/AllocatorExchangeManager.tsx:457)
`src/components/exchanges/AllocatorExchangeManager.tsx:457` calls `POST /api/allocator/holdings/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/allocator/holdings/sync` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/allocator/holdings/sync (src/components/exchanges/AllocatorExchangeManager.tsx:598)
`src/components/exchanges/AllocatorExchangeManager.tsx:598` calls `POST /api/allocator/holdings/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/allocator/holdings/sync` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/allocator/scenario/commit (src/app/(dashboard)/allocations/components/ScenarioCommitDrawer.tsx:524)
`src/app/(dashboard)/allocations/components/ScenarioCommitDrawer.tsx:524` calls `POST /api/allocator/scenario/commit` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/allocator/scenario/commit` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/attestation (src/components/legal/AccreditedInvestorGate.tsx:30)
`src/components/legal/AccreditedInvestorGate.tsx:30` calls `POST /api/attestation` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/attestation` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/bridge (src/components/portfolio/ReplacementPanel.tsx:40)
`src/components/portfolio/ReplacementPanel.tsx:40` calls `POST /api/bridge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bridge` 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/bridge/outcome (src/lib/bridge-outcome-schema.ts:133)
`src/lib/bridge-outcome-schema.ts:133` calls `POST /api/bridge/outcome` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bridge/outcome` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/bridge/outcome/dismiss (src/app/(dashboard)/allocations/components/BridgeOutcomeBanner.tsx:36)
`src/app/(dashboard)/allocations/components/BridgeOutcomeBanner.tsx:36` calls `POST /api/bridge/outcome/dismiss` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bridge/outcome/dismiss` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/for-quants-lead (src/app/(dashboard)/strategies/new/wizard/DesktopGate.tsx:42)
`src/app/(dashboard)/strategies/new/wizard/DesktopGate.tsx:42` calls `POST /api/for-quants-lead` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/for-quants-lead` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/for-quants-lead (src/app/for-quants/RequestCallModal.tsx:140)
`src/app/for-quants/RequestCallModal.tsx:140` calls `POST /api/for-quants-lead` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/for-quants-lead` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/intro (src/components/portfolio/ReplacementCard.tsx:63)
`src/components/portfolio/ReplacementCard.tsx:63` calls `POST /api/intro` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/intro` 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/intro (src/components/strategy/RequestIntroButton.tsx:93)
`src/components/strategy/RequestIntroButton.tsx:93` calls `POST /api/intro` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/intro` 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/intro-response (src/components/strategy/PendingIntros.tsx:61)
`src/components/strategy/PendingIntros.tsx:61` calls `POST /api/intro-response` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/intro-response` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/keys/sync (src/app/(dashboard)/strategies/new/wizard/steps/SyncPreviewStep.tsx:207)
`src/app/(dashboard)/strategies/new/wizard/steps/SyncPreviewStep.tsx:207` calls `POST /api/keys/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/keys/sync` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/keys/sync (src/components/strategy/ApiKeyManager.tsx:188)
`src/components/strategy/ApiKeyManager.tsx:188` calls `POST /api/keys/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/keys/sync` 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: POST /api/keys/sync (src/components/strategy/ApiKeyManager.tsx:251)
`src/components/strategy/ApiKeyManager.tsx:251` calls `POST /api/keys/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/keys/sync` 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: POST /api/keys/validate-and-encrypt (src/components/exchanges/AllocatorExchangeManager.tsx:529)
`src/components/exchanges/AllocatorExchangeManager.tsx:529` calls `POST /api/keys/validate-and-encrypt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/keys/validate-and-encrypt` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/keys/validate-and-encrypt (src/components/strategy/ApiKeyManager.tsx:137)
`src/components/strategy/ApiKeyManager.tsx:137` calls `POST /api/keys/validate-and-encrypt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/keys/validate-and-encrypt` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/keys/validate-and-encrypt (src/components/strategy/StrategyForm.tsx:103)
`src/components/strategy/StrategyForm.tsx:103` calls `POST /api/keys/validate-and-encrypt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/keys/validate-and-encrypt` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/match/decisions/holding (src/lib/bridge/send-intro.ts:48)
`src/lib/bridge/send-intro.ts:48` calls `POST /api/match/decisions/holding` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/match/decisions/holding` 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/portfolio-documents (src/components/portfolio/DocumentUpload.tsx:54)
`src/components/portfolio/DocumentUpload.tsx:54` calls `POST /api/portfolio-documents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/portfolio-documents` 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/strategies/create-with-key (src/app/(dashboard)/strategies/new/wizard/steps/ConnectKeyStep.tsx:137)
`src/app/(dashboard)/strategies/new/wizard/steps/ConnectKeyStep.tsx:137` calls `POST /api/strategies/create-with-key` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/strategies/create-with-key` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/strategies/csv-finalize (src/app/(dashboard)/strategies/new/wizard/steps/CsvSubmitStep.tsx:98)
`src/app/(dashboard)/strategies/new/wizard/steps/CsvSubmitStep.tsx:98` calls `POST /api/strategies/csv-finalize` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/strategies/csv-finalize` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/strategies/csv-validate (src/app/(dashboard)/strategies/new/wizard/steps/CsvUploadStep.tsx:266)
`src/app/(dashboard)/strategies/new/wizard/steps/CsvUploadStep.tsx:266` calls `POST /api/strategies/csv-validate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/strategies/csv-validate` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/strategies/finalize-wizard (src/app/(dashboard)/strategies/new/wizard/steps/SubmitStep.tsx:74)
`src/app/(dashboard)/strategies/new/wizard/steps/SubmitStep.tsx:74` calls `POST /api/strategies/finalize-wizard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/strategies/finalize-wizard` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (supabase/functions/notify-admin/index.ts:66)
`supabase/functions/notify-admin/index.ts:66` calls `POST https://api.resend.com/emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.resend.com/emails` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.supabase.com/v1/projects/${SUPABASE_PROJECT_REF}/database/query (src/lib/test-helpers/live-db.ts:212)
`src/lib/test-helpers/live-db.ts:212` calls `POST https://api.supabase.com/v1/projects/${SUPABASE_PROJECT_REF}/database/query` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.supabase.com/v1/projects/<p>/d…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/match/preferences/${allocatorId} (src/components/admin/PreferencesPanel.tsx:143)
`src/components/admin/PreferencesPanel.tsx:143` calls `PUT /api/admin/match/preferences/${allocatorId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/match/preferences/<p>` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/preferences (src/app/(dashboard)/allocations/components/MandateQuickSetCard.tsx:82)
`src/app/(dashboard)/allocations/components/MandateQuickSetCard.tsx:82` calls `PUT /api/preferences` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/preferences` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/preferences (src/app/(dashboard)/allocations/components/MandateQuickSetCard.tsx:93)
`src/app/(dashboard)/allocations/components/MandateQuickSetCard.tsx:93` calls `PUT /api/preferences` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/preferences` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/preferences (src/components/mandate/useMandateAutoSave.ts:272)
`src/components/mandate/useMandateAutoSave.ts:272` calls `PUT /api/preferences` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/preferences` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/watchlist/${strategyId} (src/components/strategy/StarToggle.tsx:63)
`src/components/strategy/StarToggle.tsx:63` calls `PUT /api/watchlist/${strategyId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/watchlist/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `compute_analytics` without auth dependency — analytics-service/routers/analytics.py:15
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/analytics.py:15 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cron_recompute` without auth dependency — analytics-service/routers/match.py:1829
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/match.py:1829 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cron_sync` without auth dependency — analytics-service/routers/cron.py:555
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/cron.py:555 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `csv_validate` without auth dependency — analytics-service/routers/csv.py:56
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/csv.py:56 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `encrypt_key` without auth dependency — analytics-service/routers/debug_key_flow.py:159
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/debug_key_flow.py:159 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `encrypt_key` without auth dependency — analytics-service/routers/exchange.py:75
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/exchange.py:75 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `fetch_trades` without auth dependency — analytics-service/routers/debug_key_flow.py:196
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/debug_key_flow.py:196 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `fetch_trades` without auth dependency — analytics-service/routers/exchange.py:88
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/exchange.py:88 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `get_key_permissions` without auth dependency — analytics-service/routers/internal.py:126
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/internal.py:126 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `portfolio_analytics` without auth dependency — analytics-service/routers/portfolio.py:1529
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/portfolio.py:1529 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `portfolio_bridge` without auth dependency — analytics-service/routers/portfolio.py:1849
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/portfolio.py:1849 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `portfolio_optimizer` without auth dependency — analytics-service/routers/portfolio.py:1589
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/portfolio.py:1589 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `portfolio_simulator` without auth dependency — analytics-service/routers/simulator.py:231
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/simulator.py:231 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `process_key` without auth dependency — analytics-service/routers/process_key.py:338
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/process_key.py:338 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recompute` without auth dependency — analytics-service/routers/match.py:1619
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/match.py:1619 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_key` without auth dependency — analytics-service/routers/debug_key_flow.py:113
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/debug_key_flow.py:113 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_key` without auth dependency — analytics-service/routers/exchange.py:25
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/exchange.py:25 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_strategy` without auth dependency — analytics-service/routers/portfolio.py:2144
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
analytics-service/routers/portfolio.py:2144 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/check-banned-packages.mjs:60
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 — src/__tests__/check-banned-packages.test.ts:15
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 — src/__tests__/gdpr-export.test.ts:128
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 — src/__tests__/match-decisions-holding-endpoint-rls.test.ts:99
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 — src/__tests__/scenario-commit-rls.test.ts:414
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 — src/app/(dashboard)/allocations/components/MandateQuickSetCard.tsx:93
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 — src/app/(dashboard)/allocations/components/ScenarioCommitDrawer.test.tsx:703
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 — src/app/(dashboard)/allocations/components/StrategyBrowseDrawer.test.tsx:350
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 — src/app/(dashboard)/allocations/components/StrategyBrowseDrawer.tsx: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 — src/app/(dashboard)/allocations/widgets/outcomes/outcomes.test.tsx:435
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 — src/app/(dashboard)/strategies/new/wizard/steps/ConnectKeyStep.test.tsx:8
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 — src/app/(dashboard)/strategies/new/wizard/steps/SyncPreviewStep.render.test.tsx:142
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 — src/app/(dashboard)/strategies/new/wizard/steps/SyncPreviewStep.tsx:207
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 — src/app/api/cron/founder-lp-report/route.test.ts:26
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 — src/app/api/cron/founder-lp-report/route.ts:19
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 — src/app/api/cron/reconcile-strategies/route.ts:11
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 — src/app/api/keys/validate-and-encrypt/route.ts:79
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 — src/app/api/strategies/finalize-wizard/route.ts:81
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 — src/components/admin/MatchQueueIndex.tsx:146
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 — src/components/exchanges/AllocatorExchangeManager.test.tsx:239
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 — src/components/exchanges/AllocatorExchangeManager.tsx:529
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 — src/components/mandate/useMandateAutoSave.ts:118
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 — src/components/mandate/useMandateAutoSave.unmount.test.ts:71
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 — src/components/portfolio/AlertsList.tsx: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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/portfolio/DocumentUpload.tsx:54
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 — src/components/strategy-v2/HeadlineMetricsPanel.tsx:13
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 — src/components/strategy/ManagerIdentityPanel.test.tsx:72
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 — src/components/strategy/ManagerIdentityPanel.tsx:16
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 — src/components/strategy/PendingIntros.test.tsx:207
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 — src/components/strategy/PendingIntros.tsx: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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/hooks/useLazyPanelMetrics.test.ts:659
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 — src/lib/analytics-client.test.ts:211
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 — src/lib/api/withAuth.ts:44
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 — src/lib/auth.test.ts:586
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 — src/lib/bridge/send-intro.ts:7
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 — src/lib/test-helpers/live-db.ts:212
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 — supabase/functions/notify-admin/index.ts:66
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 cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/cassette-refresh.yml CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — analytics-service/scripts/phase12_deploy.py:133
`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 — analytics-service/scripts/phase12_kill_switch.py:190
`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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 208 placeholder/mock markers across 91 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 quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 72 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALERT_ACK_SECRET`, `ALLOWED_ORIGINS`, `ALLOW_NO_LOCKFILE`, `AWS_LAMBDA_FUNCTION_NAME`, `BASE_URL`, `CI`, `DATABASE_URL`, `DB_THREAD_POOL_SIZE` + 64 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
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 115 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: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
analytics-service/Dockerfile:9 containersPinned dependencies
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: analytics-service/scripts/phase12_kill_switch.py:measure_p999_via_sql, analytics-service/scripts/phase12_kill_switch.py:measure_p999 This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Co…
8 occurrences
repo-level (8 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 `_claim_legacy` in analytics-service/main_worker.py:397
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 `_claim_legacy` in analytics-service/tests/test_compute_jobs_fencing.py:1634
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 `boLegacy` in src/__tests__/bridge-outcome-cron-holding.test.ts:457
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 `compute_fingerprint_v1` in analytics-service/services/ingestion/binance.py:123
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 `compute_fingerprint_v1` in analytics-service/services/ingestion/bybit.py:89
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `compute_fingerprint_v1` in analytics-service/services/ingestion/csv_adapter.py:218
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 `compute_fingerprint_v1` in analytics-service/services/ingestion/fingerprint.py:62
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 `compute_fingerprint_v1` in analytics-service/services/ingestion/okx.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 `compute_fingerprint_v1` in analytics-service/tests/test_compute_similarity_sql.py: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 `compute_fingerprint_v1` in analytics-service/tests/test_fingerprint.py:1
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 `emitFirstBridgeSurfacedLegacy` in src/lib/analytics/onboarding-funnel.ts:242
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 `excess_old` in analytics-service/tests/test_ana_recon_audit.py:1034
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 `factsheet_v2_share_copy` in src/app/factsheet/[id]/v2/factsheet-analytics.ts:28
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 `factsheet_v2_share_copy` in src/app/factsheet/[id]/v2/FactsheetView.tsx:800
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 `for_quants_view_fired_v1` in src/app/for-quants/ForQuantsCtas.test.tsx: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 `for_quants_view_fired_v1` in src/app/for-quants/ForQuantsCtas.tsx:41
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 `match_decisions_kind_bridge_recommended_v2` in src/__tests__/match-decisions-xor-rls.test.ts:129
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 `migrateLegacy` in src/app/(dashboard)/allocations/hooks/useExcludedKeyIds.ts:61
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 `migrateLegacy` in src/lib/storage/codecs.test.ts:15
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 `migrateLegacy` in src/lib/storage/codecs.ts:52
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 `quantalyze_wizard_state_v1` in e2e/wizard-hydration-probe.spec.ts:148
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 `quantalyze_wizard_state_v1` in src/components/auth/SignOutButton.test.tsx:73
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 `quantalyze_wizard_state_v1` in src/lib/wizard/localStorage.test.ts:301
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 `quantalyze_wizard_state_v1` in src/lib/wizard/localStorage.ts:51
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 `runIntrospectionSqlLegacy` in src/__tests__/match-decisions-schema.test.ts:34
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 `sOld` in src/app/(dashboard)/allocations/widgets/outcomes/outcomes.test.tsx:321
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 `strategy_v2` in e2e/strategy-v2-axe.spec.ts:44
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 `strategy_v2` in e2e/strategy-v2-chart-parity.spec.ts:66
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 `strategy_v2` in e2e/strategy-v2-keyboard.spec.ts:70
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_90_day_gate_fetches_archive_when_old` in analytics-service/tests/test_exchange_harness.py:227
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_drain_missing_metadata_treated_as_legacy` in analytics-service/tests/test_long_fetch.py:317
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_and_clear_returns_defensive_copy` in analytics-service/tests/test_exchange.py:5142
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_weights_version_pinned_v2` in analytics-service/tests/test_match_engine.py:1208
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 `ui_v2` in src/app/(dashboard)/allocations/AllocationsTabs.scenario-composer.test.tsx:8
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 `ui_v2` in src/app/(dashboard)/allocations/AllocationsTabs.test.tsx:614
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 `ui_v2` in src/app/(dashboard)/allocations/AllocationsTabs.tsx:137
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `verification_requests_legacy` in analytics-service/routers/portfolio.py:2151
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 `verification_requests_legacy` in analytics-service/tests/test_legacy_table_rls.py:2
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 `verification_requests_legacy` in analytics-service/tests/test_verify_strategy_no_legacy_writes.py:6
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 `verification_requests_legacy` in src/app/api/verify-strategy/[id]/status/route.ts:23
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 `widget_state_v2` in src/app/(dashboard)/allocations/components/WidgetState.tsx:21
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 `widget_state_v2` in src/app/(dashboard)/allocations/widgets/outcomes/OutcomesWidget.v2.test.tsx:21
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 `widget_state_v2` in src/app/(dashboard)/allocations/widgets/performance/EquityChart.v2.test.tsx:9
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `widget_state_v2` in src/lib/widget-state-flag.test.ts:8
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 `widget_state_v2` in src/lib/widget-state-flag.ts: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 software Dead code conf 1.00 Possibly dead Python function: npv
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
analytics-service/services/portfolio_metrics.py:204
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — e2e/csv-upload-flow.spec.ts:110
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 — e2e/demo-founder-view.spec.ts:75
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 — e2e/demo-public.spec.ts:269
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 — e2e/wizard-hydration-probe.spec.ts:84
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 — scripts/check-admin-route-manifest.ts:431
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 — scripts/check-founder-lp-readiness.ts:48
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 — scripts/check-gdpr-export-coverage.ts:780
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 — scripts/seed-demo-data.ts:655
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 — scripts/seed-full-app-demo.ts:1193
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 — scripts/verify-phase18-artifacts.ts:87
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 — src/app/api/keys/sync/route.ts:274
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: GET /eval
`analytics-service/routers/match.py` declares `GET /eval` 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 /
`analytics-service/routers/process_key.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 /compute-analytics
`analytics-service/routers/analytics.py` declares `POST /compute-analytics` 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 /cron-recompute
`analytics-service/routers/match.py` declares `POST /cron-recompute` 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 /cron-sync
`analytics-service/routers/cron.py` declares `POST /cron-sync` 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 /csv/validate
`analytics-service/routers/csv.py` declares `POST /csv/validate` 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 /encrypt
`analytics-service/routers/debug_key_flow.py` declares `POST /encrypt` 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 /encrypt-key
`analytics-service/routers/exchange.py` declares `POST /encrypt-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: POST /fetch-trades
`analytics-service/routers/debug_key_flow.py` declares `POST /fetch-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: POST /portfolio-analytics
`analytics-service/routers/portfolio.py` declares `POST /portfolio-analytics` 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 /portfolio-bridge
`analytics-service/routers/portfolio.py` declares `POST /portfolio-bridge` 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 /recompute
`analytics-service/routers/match.py` declares `POST /recompute` 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 /validate
`analytics-service/routers/debug_key_flow.py` declares `POST /validate` 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 /validate-key
`analytics-service/routers/exchange.py` declares `POST /validate-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 quality Complexity conf 1.00 Very large file: analytics-service/routers/match.py (2018 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/routers/portfolio.py (2423 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/scripts/phase12_kill_switch.py (1138 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/services/analytics_runner.py (2172 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/services/equity_reconstruction.py (3181 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/services/exchange.py (2777 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/services/job_worker.py (2799 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/services/match_engine.py (1280 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/services/metrics.py (1499 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/services/position_reconstruction.py (2149 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_ana_recon_audit.py (1281 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_analytics_runner.py (5350 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_c19_portfolio_fixes.py (1150 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_compute_jobs_fencing.py (2607 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_cron_router.py (2690 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_equity_reconstruction.py (4907 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_exchange.py (5658 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_feedback_engine.py (2059 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_funding_fetch.py (1983 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_job_worker.py (3291 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_main_worker.py (1675 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_match_engine.py (1588 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_match_router.py (3956 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_metrics.py (2067 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_phase12_kill_switch.py (1709 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_position_reconstruction.py (4033 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_position_reconstruction_funding.py (1669 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_process_key.py (1986 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: analytics-service/tests/test_simulator_router.py (1736 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/seed-full-app-demo.ts (1768 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/__tests__/audit-coverage.test.ts (1282 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/__tests__/critical-regressions.test.ts (1247 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/__tests__/csv-validate-route.test.ts (1355 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/__tests__/gdpr-export.test.ts (2384 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/(dashboard)/allocations/components/ScenarioCommitDrawer.test.tsx (2067 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/(dashboard)/allocations/components/ScenarioCommitDrawer.tsx (1194 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/(dashboard)/allocations/components/ScenarioComposer.test.tsx (2043 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/(dashboard)/allocations/components/ScenarioComposer.tsx (1427 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/(dashboard)/allocations/widgets/performance/EquityChart.tsx (2303 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/api/admin/users/[id]/roles/route.test.ts (1982 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/api/allocator/scenario/commit/route.test.ts (1604 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/api/strategies/csv-finalize/route.ts (1399 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/app/factsheet/[id]/v2/TimeSeriesChart.tsx (1311 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/audit.ts (1142 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/auth.test.ts (1426 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/database.types.ts (3580 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/gdpr-export.ts (1295 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/queries.my-allocation.test.ts (1506 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/queries.ts (3205 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/types.ts (1709 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: supabase/types.generated.ts (3256 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/39ce0f62-382a-45eb-ac42-1985c5079bde/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/39ce0f62-382a-45eb-ac42-1985c5079bde/

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.