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

tyeom/AlphaMind

https://github.com/tyeom/AlphaMind · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

111 raw signals (0 security + 111 graph)

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

Complete repo analysis

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

JSON
Combined
52.5
/100
Security checks
53
0 findings
System graph
53
100.0% cov · 109 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 14 Medium 19 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 109 Crowd 0 Layer: Frontend 6 Hardware 6 Security 9 Cicd 1 Quality 27 Api 60
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 52.5/100 with 100.0% coverage. It contains 1489 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 111 findings — concentrated in api (60), quality (27), security (9). Risk profile is high: 0 critical, 14 high, 19 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/kis-api/references/kis-auth.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/kis-api/references/kis-auth.md:50 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/kis-api/references/kis-websocket.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/kis-api/references/kis-websocket.md:327 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/kis-api/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/kis-api/SKILL.md:103 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: GET /market-api/agents/login/status?provider=${targetProvider} (apps/frontend/src/pages/AgentSettings.tsx:60)
`apps/frontend/src/pages/AgentSettings.tsx:60` calls `GET /market-api/agents/login/status?provider=${targetProvider}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/market-api/agents/login/status` If this points at …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /market-api/stocks/collection-status (apps/frontend/src/components/CollectionStatus.tsx:20)
`apps/frontend/src/components/CollectionStatus.tsx:20` calls `GET /market-api/stocks/collection-status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/market-api/stocks/collection-status` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /market-api/stocks/collection-status (apps/frontend/src/components/CollectionStatus.tsx:49)
`apps/frontend/src/components/CollectionStatus.tsx:49` calls `GET /market-api/stocks/collection-status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/market-api/stocks/collection-status` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.openai.com/v1/models (apps/market-data-service/src/agent-config/agent-config.service.ts:648)
`apps/market-data-service/src/agent-config/agent-config.service.ts:648` calls `GET https://api.openai.com/v1/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/models` If this points at …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /market-api/agents/config (apps/frontend/src/pages/AgentSettings.tsx:153)
`apps/frontend/src/pages/AgentSettings.tsx:153` calls `POST /market-api/agents/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/market-api/agents/config` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /market-api/agents/gpt/auth/import (apps/frontend/src/pages/AgentSettings.tsx:196)
`apps/frontend/src/pages/AgentSettings.tsx:196` calls `POST /market-api/agents/gpt/auth/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/market-api/agents/gpt/auth/import` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /market-api/agents/login (apps/frontend/src/pages/AgentSettings.tsx:229)
`apps/frontend/src/pages/AgentSettings.tsx:229` calls `POST /market-api/agents/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/market-api/agents/login` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /market-api/agents/login/code (apps/frontend/src/pages/AgentSettings.tsx:261)
`apps/frontend/src/pages/AgentSettings.tsx:261` calls `POST /market-api/agents/login/code` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/market-api/agents/login/code` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /market-api/agents/verify (apps/frontend/src/pages/AgentSettings.tsx:110)
`apps/frontend/src/pages/AgentSettings.tsx:110` calls `POST /market-api/agents/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/market-api/agents/verify` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (apps/market-data-service/src/agent-config/agent-config.service.ts:627)
`apps/market-data-service/src/agent-config/agent-config.service.ts:627` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in apps/backend/src/kis/toss.service.ts:206
Found a known-risky pattern (exec_used). Review and replace if possible.
apps/backend/src/kis/toss.service.ts:206 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/frontend/src/api/scanner.ts:133
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 — apps/frontend/src/pages/AgentSettings.tsx:153
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 — apps/market-data-service/src/agent-config/agent-config.service.ts:455
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 — apps/market-data-service/src/yahoo-finance/yahoo-finance.service.ts:84
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, ci, 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, 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: apps/backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: apps/frontend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: apps/market-data-service/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 `/admin/users/:id` has no Link/navigate to it — apps/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.
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in apps/frontend/src/api/client.ts:19
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
apps/frontend/src/api/client.ts:19 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/market-data-service/src/ai-scoring/claude-pty.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/market-data-service/src/ai-scoring/claude-pty.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/market-data-service/src/ai-scoring/gpt-pty.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/market-data-service/src/ai-scoring/gpt-pty.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in README.md:58
Found a known-risky pattern (node_child_process). Review and replace if possible.
README.md:58 Node child process
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 24 placeholder/mock markers across 8 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
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
8 test file(s) for 219 source file(s) (ratio 0.04). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 12 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENTS_CONFIG_DIR`, `ANTHROPIC_API_KEY`, `BACKEND_INSTANCE_ID`, `CLAUDE_CONFIG_DIR`, `CODEX_CLI_PATH`, `CODEX_HOME`, `CODEX_MODEL`, `CODEX_WORKDIR` + 4 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 5 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: nginx:alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
apps/frontend/Dockerfile:19 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
3 files, 3 locations
apps/backend/Dockerfile:1
apps/frontend/Dockerfile:1
apps/market-data-service/Dockerfile:1
containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — apps/frontend/src/components/AutoTradingConfigModal.tsx:168
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 — apps/frontend/src/components/SessionConflictModal.tsx:65
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 security security conf 1.00 Insecure pattern 'document_write' in apps/market-data-service/document/kis-api/한국투자증권_오픈API_전체문서_20260328_030000.htm:727
Found a known-risky pattern (document_write). Review and replace if possible.
apps/market-data-service/document/kis-api/한국투자증권_오픈API_전체문서_20260328_030000.htm:727 Document write
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: apps/backend/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.
apps/backend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/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.
apps/frontend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/market-data-service/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.
apps/market-data-service/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: libs/common/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.
libs/common/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: libs/strategies/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.
libs/strategies/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/src/main.ts:66
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 — apps/market-data-service/src/main.ts:25
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 — apps/market-data-service/src/strategy/__sim__/regime-cluster-sim.ts:5
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /ai-scoring/session/:id
`apps/market-data-service/src/ai-scoring/ai-scoring.controller.ts` declares `DELETE /ai-scoring/session/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /notifications/:id
`apps/backend/src/notification/notification.controller.ts` declares `DELETE /notifications/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /agents/login/status
`apps/market-data-service/src/agent-config/agent-config.controller.ts` declares `GET /agents/login/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /agents/status
`apps/market-data-service/src/agent-config/agent-config.controller.ts` declares `GET /agents/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ai-scoring/session/:id
`apps/market-data-service/src/ai-scoring/ai-scoring.controller.ts` declares `GET /ai-scoring/session/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ai-scoring/session/:id/stream
`apps/market-data-service/src/ai-scoring/ai-scoring.controller.ts` declares `GET /ai-scoring/session/:id/stream` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ai-scoring/session/active
`apps/market-data-service/src/ai-scoring/ai-scoring.controller.ts` declares `GET /ai-scoring/session/active` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auto-trading/sessions
`apps/backend/src/auto-trading/auto-trading.controller.ts` declares `GET /auto-trading/sessions` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auto-trading/sessions/:id
`apps/backend/src/auto-trading/auto-trading.controller.ts` declares `GET /auto-trading/sessions/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/unread-count
`apps/backend/src/notification/notification.controller.ts` declares `GET /notifications/unread-count` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stocks/:code
`apps/market-data-service/src/stock/stock.controller.ts` declares `GET /stocks/:code` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stocks/:code/prices
`apps/market-data-service/src/stock/stock.controller.ts` declares `GET /stocks/:code/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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stocks/collection-status
`apps/market-data-service/src/stock/stock.controller.ts` declares `GET /stocks/collection-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/analyze
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/backtest
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/candle-pattern
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/candle-pattern` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/day-trading
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/day-trading` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/infinity-bot
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/infinity-bot` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/mean-reversion
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/mean-reversion` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/momentum-power
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/momentum-power` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/momentum-surge
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/momentum-surge` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/:code/scalping
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/:code/scalping` 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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /strategies/optimal-params/short-term-tp-sl
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `GET /strategies/optimal-params/short-term-tp-sl` 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 — consid…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /time
`apps/backend/src/app.controller.ts` declares `GET /time` 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 /yahoo-finance/chart/:symbol
`apps/market-data-service/src/yahoo-finance/yahoo-finance.controller.ts` declares `GET /yahoo-finance/chart/: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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /auto-trading/sessions/:id/pause
`apps/backend/src/auto-trading/auto-trading.controller.ts` declares `PATCH /auto-trading/sessions/:id/pause` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /notifications/:id/read
`apps/backend/src/notification/notification.controller.ts` declares `PATCH /notifications/:id/read` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /notifications/read-all
`apps/backend/src/notification/notification.controller.ts` declares `PATCH /notifications/read-all` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /agents/config
`apps/market-data-service/src/agent-config/agent-config.controller.ts` declares `POST /agents/config` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /agents/gpt/auth/import
`apps/market-data-service/src/agent-config/agent-config.controller.ts` declares `POST /agents/gpt/auth/import` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /agents/login
`apps/market-data-service/src/agent-config/agent-config.controller.ts` declares `POST /agents/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /agents/login/code
`apps/market-data-service/src/agent-config/agent-config.controller.ts` declares `POST /agents/login/code` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /agents/verify
`apps/market-data-service/src/agent-config/agent-config.controller.ts` declares `POST /agents/verify` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ai-scoring/score
`apps/market-data-service/src/ai-scoring/ai-scoring.controller.ts` declares `POST /ai-scoring/score` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ai-scoring/score-stream
`apps/market-data-service/src/ai-scoring/ai-scoring.controller.ts` declares `POST /ai-scoring/score-stream` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ai-scoring/session/start
`apps/market-data-service/src/ai-scoring/ai-scoring.controller.ts` declares `POST /ai-scoring/session/start` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/sign-in
`apps/backend/src/auth/auth.controller.ts` declares `POST /auth/sign-in` 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 /auth/sign-out
`apps/frontend/src/api/auth.ts` declares `POST /auth/sign-out` 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 /auto-trading/scheduled-scan/trigger
`apps/backend/src/auto-trading/auto-trading.controller.ts` declares `POST /auto-trading/scheduled-scan/trigger` 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 removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auto-trading/sessions
`apps/backend/src/auto-trading/auto-trading.controller.ts` declares `POST /auto-trading/sessions` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auto-trading/sessions/batch
`apps/backend/src/auto-trading/auto-trading.controller.ts` declares `POST /auto-trading/sessions/batch` 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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /kis/order/buy
`apps/frontend/src/api/kis.ts` declares `POST /kis/order/buy` 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 /kis/order/cancel
`apps/frontend/src/api/kis.ts` declares `POST /kis/order/cancel` 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 /kis/order/modify
`apps/frontend/src/api/kis.ts` declares `POST /kis/order/modify` 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 /kis/order/sell
`apps/frontend/src/api/kis.ts` declares `POST /kis/order/sell` 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 /notifications/create
`apps/frontend/src/pages/AiScanner.tsx` declares `POST /notifications/create` 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 /stocks/collect
`apps/market-data-service/src/stock/stock.controller.ts` declares `POST /stocks/collect` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /strategies/optimize-tp-sl
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `POST /strategies/optimize-tp-sl` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /strategies/optimize-tp-sl/run-weekly-now
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `POST /strategies/optimize-tp-sl/run-weekly-now` 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 — conside…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /strategies/scan
`apps/market-data-service/src/strategy/strategy.controller.ts` declares `POST /strategies/scan` 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…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/auto-trading/auto-trading.service.ts (3420 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/pages/AiScanner.tsx (3329 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/market-data-service/src/strategy/backtest.service.ts (2865 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/02771326-65b6-49c6-b6f8-9a97bb819409/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/02771326-65b6-49c6-b6f8-9a97bb819409/

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.