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

damarleypowell/jamaica-financial-advisor-v2

https://github.com/damarleypowell/jamaica-financial-advisor-v2 · scanned 2026-06-17 01:52 UTC (1 month, 1 week ago)

165 raw signals (0 security + 165 graph)

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

Complete repo analysis

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

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

Showing 138 of 140 actionable findings. 165 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 scripts/seed-admin.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/seed-admin.js:13
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in scripts/seed-users.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 21, 28
scripts/seed-users.js:21, 28 (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET https://jamaica.loopnews.com/category/business (news-scraper.js:148)
`news-scraper.js:148` calls `GET https://jamaica.loopnews.com/category/business` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/jamaica.loopnews.com/category/business` If this points at an external API, prefi…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://news.google.com/rss/search?q=${encodeURIComponent(query)}&hl=${hl}&gl=${gl}&ceid=${ceid} (news-scraper.js:186)
`news-scraper.js:186` calls `GET https://news.google.com/rss/search?q=${encodeURIComponent(query)}&hl=${hl}&gl=${gl}&ceid=${ceid}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/news.google.com/rss/search` If…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://radiojamaicanewsonline.com/business (news-scraper.js:165)
`news-scraper.js:165` calls `GET https://radiojamaicanewsonline.com/business` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/radiojamaicanewsonline.com/business` If this points at an external API, prefix it w…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.jamstockex.com/trading/trade-summary/ (jse-scraper.js:216)
`jse-scraper.js:216` calls `GET https://www.jamstockex.com/trading/trade-summary/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.jamstockex.com/trading/trade-summary` If this points at an external API, p…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.jseinvestor.com/ (jse-scraper.js:156)
`jse-scraper.js:156` calls `GET https://www.jseinvestor.com/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.jseinvestor.com` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/text-to-speech/${VOICE_ID} (src/routes/ai.routes.js:627)
`src/routes/ai.routes.js:627` calls `POST https://api.elevenlabs.io/v1/text-to-speech/${VOICE_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/text-to-speech/<p>` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/text-to-speech/${VOICE_ID} (src/routes/ai.routes.js:766)
`src/routes/ai.routes.js:766` calls `POST https://api.elevenlabs.io/v1/text-to-speech/${VOICE_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/text-to-speech/<p>` If this points at an …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `advanced_screen` without auth dependency — python-analytics/routers/screener.py:39
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
python-analytics/routers/screener.py:39 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `backtest` without auth dependency — python-analytics/routers/prediction.py:369
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
python-analytics/routers/prediction.py:369 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `optimize_portfolio` without auth dependency — python-analytics/routers/portfolio.py:110
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
python-analytics/routers/portfolio.py:110 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pattern_detection` without auth dependency — python-analytics/routers/technical.py:385
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
python-analytics/routers/technical.py:385 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `predict` without auth dependency — python-analytics/routers/prediction.py:97
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
python-analytics/routers/prediction.py:97 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `risk_metrics` without auth dependency — python-analytics/routers/portfolio.py:208
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
python-analytics/routers/portfolio.py:208 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `support_resistance` without auth dependency — python-analytics/routers/technical.py:302
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
python-analytics/routers/technical.py:302 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `technical_analysis` without auth dependency — python-analytics/routers/technical.py:66
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
python-analytics/routers/technical.py:66 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 JS POST `/api/admin/kyc/${userId}/approve` admin endpoint without auth — client/src/api/admin.ts:25
Admin-scoped JS route with no recognizable auth: no middleware-position guard, no router-level guard above it in this file, and no inline permission call within the first 15 lines of the handler. If auth is applied where this router is mounted, dismiss with reason `by_design` or tag the route `// p…
client/src/api/admin.ts:25 securityAuth js admin unauth
high System graph security auth conf 1.00 JS POST `/api/admin/kyc/${userId}/reject` admin endpoint without auth — client/src/api/admin.ts:30
Admin-scoped JS route with no recognizable auth: no middleware-position guard, no router-level guard above it in this file, and no inline permission call within the first 15 lines of the handler. If auth is applied where this router is mounted, dismiss with reason `by_design` or tag the route `// p…
client/src/api/admin.ts:30 securityAuth js admin unauth
high System graph security auth conf 1.00 JS PUT `/api/admin/users/${id}` admin endpoint without auth — client/src/api/admin.ts:15
Admin-scoped JS route with no recognizable auth: no middleware-position guard, no router-level guard above it in this file, and no inline permission call within the first 15 lines of the handler. If auth is applied where this router is mounted, dismiss with reason `by_design` or tag the route `// p…
client/src/api/admin.ts:15 securityAuth js admin unauth
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — public-react/assets/index-DEXxlYPP.js:10
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/features/learn/Learn.tsx:956
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 — public-react/assets/api-HAxN0Coo.js:1
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 — public-react/assets/index-DEXxlYPP.js:2
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 — public/sw.js:112
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/routes/auth.routes.js:1721
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, tests, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Frontend route `${e===`/`?`*`:`${e}/*`}` has no Link/navigate to it — public-react/assets/index-DEXxlYPP.js
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `${e}` has no Link/navigate to it — public-react/assets/index-DEXxlYPP.js
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 6 occurrences Frontend route `onboarding` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
6 occurrences
repo-level (6 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 19 occurrences Frontend route `subscription` has no Link/navigate to it — client/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
19 occurrences
repo-level (19 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in public-react/assets/index-DEXxlYPP.js:10
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
public-react/assets/index-DEXxlYPP.js:10 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public-react/assets/index-DEXxlYPP.js:9
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public-react/assets/index-DEXxlYPP.js:9 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin.html:210
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin.html:210 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/app.js:51
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/app.js:51 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in client/src/api/client.ts:53
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
client/src/api/client.ts:53 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in client/src/context/AuthContext.tsx:100
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
client/src/context/AuthContext.tsx:100 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/components/modals/AuthModal.tsx:431
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/components/modals/AuthModal.tsx:431 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/stores/auth.ts:52
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/stores/auth.ts:52 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in public/app.js:403
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
public/app.js:403 Local storage auth token
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 165 placeholder/mock markers across 55 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 587 in use
Port 587 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
src/services/email.service.js Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 203 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 28 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AI_MODEL_HAIKU`, `AI_MODEL_OPUS`, `AI_MODEL_SONNET`, `ANALYTICS_PORT`, `CLERK_SECRET_KEY`, `CORS_ORIGIN`, `CORS_ORIGINS`, `DEV` + 20 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 69 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 1, 5
Dockerfile:1, 5 (2 hits)
containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/components/ui/AppTour.tsx:234
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/features/admin/Admin.tsx:205
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: client/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
client/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: frontend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
frontend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `eleven_multilingual_v2` in src/routes/ai.routes.js:638
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 `gf_compliance_v1` in frontend/src/components/modals/ComplianceModal.tsx:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `gf_tour_v1` in frontend/src/components/ui/AppTour.tsx:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `gf_tour_v1` in frontend/src/components/ui/FeatureGuide.tsx:7
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 `gf_tour_v1` in scripts/shot.mjs: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 `gotham_heatmap_v2` in frontend/src/features/dashboard/Heatmap.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 `gotham_heatmap_v2` in public-react/assets/Dashboard-Q4PaOzUF.js: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 `gotham_learn_progress_v2` in frontend/src/features/learn/Learn.tsx:790
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 `unstable_legacy` in public-react/assets/index-DEXxlYPP.js: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 software Dead code conf 1.00 Possibly dead Python function: fetch_finnhub_quote
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
python-analytics/services/data_service.py:223
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_prices_from_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
python-analytics/services/data_service.py:125
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_training_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
python-analytics/services/data_service.py:242
low System graph software Dead code conf 1.00 Possibly dead Python function: neg_sharpe
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
python-analytics/routers/portfolio.py:142
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend-server.js:57
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 — jse-scraper.js:42
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 — news-scraper.js:275
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/migrate-json-to-pg.js:21
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-admin.js:34
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-users.js:52
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/config/database.js:31
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/middleware/rateLimit.js:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/server.js:23
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/services/email.service.js:23
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/services/market.service.js:26
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 /api/currency-impact
`src/routes/market.routes.js` declares `GET /api/currency-impact` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dividends
`src/routes/market.routes.js` declares `GET /api/dividends` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/docs
`src/routes/docs.routes.js` declares `GET /api/docs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/docs/openapi.json
`src/routes/docs.routes.js` declares `GET /api/docs/openapi.json` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/forex
`src/routes/market.routes.js` declares `GET /api/forex` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/global-markets
`src/routes/market.routes.js` declares `GET /api/global-markets` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/history/:symbol
`src/routes/market.routes.js` declares `GET /api/history/:symbol` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/leaderboard
`src/routes/market.routes.js` declares `GET /api/leaderboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/market-overview
`src/routes/market.routes.js` declares `GET /api/market-overview` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/news
`src/routes/market.routes.js` declares `GET /api/news` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/research/:symbol
`src/routes/market.routes.js` declares `GET /api/research/:symbol` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/search
`src/routes/market.routes.js` declares `GET /api/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sectors
`src/routes/market.routes.js` declares `GET /api/sectors` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/stocks/:symbol
`src/routes/market.routes.js` declares `GET /api/stocks/:symbol` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/stocks/:symbol/history
`src/routes/market.routes.js` declares `GET /api/stocks/:symbol/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/stocks/:symbol/profile
`src/routes/market.routes.js` declares `GET /api/stocks/:symbol/profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/stream/prices
`src/routes/market.routes.js` declares `GET /api/stream/prices` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/technicals/:symbol
`src/routes/market.routes.js` declares `GET /api/technicals/:symbol` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /predict/:symbol
`src/routes/analytics.routes.js` declares `GET /predict/:symbol` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /technical/:symbol
`src/routes/analytics.routes.js` declares `GET /technical/:symbol` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /technical/:symbol/advanced
`src/routes/analytics.routes.js` declares `GET /technical/:symbol/advanced` 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 /advanced-screen
`python-analytics/routers/screener.py` declares `POST /advanced-screen` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/chat
`src/middleware/aiGuard.js` declares `POST /api/chat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/compare
`src/routes/market.routes.js` declares `POST /api/compare` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/payments/capture-order
`src/routes/payment.routes.js` declares `POST /api/payments/capture-order` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/payments/create-order
`src/routes/payment.routes.js` declares `POST /api/payments/create-order` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/payments/create-withdrawal
`src/routes/payment.routes.js` declares `POST /api/payments/create-withdrawal` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/screener
`src/routes/market.routes.js` declares `POST /api/screener` 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 /backtest
`python-analytics/routers/prediction.py` declares `POST /backtest` 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 /compound-growth
`src/routes/analytics.routes.js` declares `POST /compound-growth` 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 /indicator
`src/routes/analytics.routes.js` declares `POST /indicator` 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 /irr
`src/routes/analytics.routes.js` declares `POST /irr` 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 /loan
`src/routes/analytics.routes.js` declares `POST /loan` 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 /optimize
`python-analytics/routers/portfolio.py` declares `POST /optimize` 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 /pattern-detection
`python-analytics/routers/technical.py` declares `POST /pattern-detection` 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
`src/routes/analytics.routes.js` declares `POST /portfolio` 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/optimize
`src/routes/analytics.routes.js` declares `POST /portfolio/optimize` 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/risk
`src/routes/analytics.routes.js` declares `POST /portfolio/risk` 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 /predict
`python-analytics/routers/prediction.py` declares `POST /predict` 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 /retirement
`src/routes/analytics.routes.js` declares `POST /retirement` 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 /risk-metrics
`python-analytics/routers/portfolio.py` declares `POST /risk-metrics` 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 /screener
`src/routes/analytics.routes.js` declares `POST /screener` 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 /support-resistance
`python-analytics/routers/technical.py` declares `POST /support-resistance` 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 /technical-analysis
`python-analytics/routers/technical.py` declares `POST /technical-analysis` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /analyze
`frontend-server.js` declares `USE /analyze` 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: USE /api
`frontend-server.js` declares `USE /api` 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: USE /api/admin
`src/app.js` declares `USE /api/admin` 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: USE /api/analytics
`src/app.js` declares `USE /api/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: USE /api/auth
`src/app.js` declares `USE /api/auth` 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: USE /api/us
`src/app.js` declares `USE /api/us` 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: client/src/pages/TechnicalAnalysis.tsx (949 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/features/admin/Admin.tsx (948 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/features/dashboard/Dashboard.tsx (1438 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/features/learn/Learn.tsx (1706 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/app.js (6637 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/routes/auth.routes.js (1895 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/routes/market.routes.js (1510 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/77ab47d7-684e-4c7b-bfd9-8185de68383c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/77ab47d7-684e-4c7b-bfd9-8185de68383c/

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.