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.

Thepluscode/NexusTradeAI

https://github.com/Thepluscode/NexusTradeAI · scanned 2026-06-16 00:34 UTC (2 months, 2 weeks ago)

418 raw signals (0 security + 418 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 395 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 115 Medium 32 Low 186 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 395 Crowd 0 Layer: Software 14 Frontend 84 Hardware 1 Security 65 Cicd 3 Quality 99 Api 129

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 5 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

5 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 9 places

View all duplicates & near-duplicates findings →

Legacy markers 65 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

12 matching findings on this repo

low Stray `console.log` in TS/JS — tests/legacy/test-dashboard-data.js:7
low Stray `console.log` in TS/JS — tests/legacy/test-exports-fix.js:11
low Stray `console.log` in TS/JS — tests/legacy/test-frontend-fixes.js:11
low Stray `console.log` in TS/JS — tests/legacy/test-complete-system.js:16
low Stray `console.log` in TS/JS — tests/legacy/test-immediate-next-steps.js:16
low Stray `console.log` in TS/JS — tests/legacy/test-python-bridge.js:8
low Stray `console.log` in TS/JS — tests/legacy/test-enhanced-features.js:16
low Stray `console.log` in TS/JS — tests/legacy/test-banking-integration.js:4
low Stray `console.log` in TS/JS — tests/legacy/test-real-market-data.js:10
low Stray `console.log` in TS/JS — tests/legacy/test-enhanced-frontend.js:12
low Stray `console.log` in TS/JS — tests/legacy/test-core-system.js:10
low Stray `console.log` in TS/JS — docs/archive/legacy-dir/check-orders.js:26

View all legacy markers findings →

Commented-out code 53 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in tests/strategy-tests.js:40
info Commented-code block (6 lines) in tests/unit/anti-churning.test.js:320
info Commented-code block (6 lines) in deploy/stock-bot/unified-trading-bot.js:15
info Commented-code block (5 lines) in deploy/stock-bot/stock-modules.manifest.js:1
info Commented-code block (5 lines) in deploy/stock-bot/signals/displacement.js:47
info Commented-code block (6 lines) in deploy/stock-bot/signals/exit-manager.js:30
info Commented-code block (5 lines) in deploy/stock-bot/signals/committee-scorer.js:…
info Commented-code block (10 lines) in deploy/stock-bot/signals/account-snapshot.js…
info Commented-code block (14 lines) in deploy/stock-bot/signals/order-intent.js:8
info Commented-code block (8 lines) in deploy/stock-bot/shared/module-loader.js:3
info Commented-code block (17 lines) in deploy/stock-bot/infrastructure/notification…
info Commented-code block (6 lines) in deploy/stock-bot/infrastructure/notifications…

View all commented-out code findings →

Config drift 6 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

6 matching findings on this repo

low Old/deprecated-named symbol `errorOnDeprecated` in jest.config.js:117
high Flask mutation route `import_configuration` without `@login_required` — service… services/strategy-engine/api_server.py:271
high Dangling fetch: GET http://localhost:3003/api/risk/config (services/dashboard/s…
high Dangling fetch: POST http://localhost:3004/api/strategies/${strategyName}/confi…
low Unused endpoint: ANY /api/config/export
low Unused endpoint: ANY /api/config/import

View all config drift findings →

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/ed213479-92b3-41fc-8366-aa563589ef7c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ed213479-92b3-41fc-8366-aa563589ef7c/

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.