byte-walkers/Aegis-Elite-SolConsensus

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.

https://github.com/byte-walkers/Aegis-Elite-SolConsensus.git · scanned 2026-05-16 17:51 UTC (1 day, 3 hours ago) · 10 languages

51 findings (3 legacy + 48 scanner) 53rd percentile · Typescript · small (2-20K LoC) Scanner says 83 (lower by 10)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 3 hours ago · v2 · 27 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}

Severity distribution — click a segment to filter

Active filters: severity: low × excluding tests × Reset all

Scan summary Repository scanned at 83.1/100 with 100.0% coverage. It contains 139 nodes across 8 cross-layer flows, written primarily in mixed languages. Engine surfaced 24 findings — concentrated in api (7), frontend (5), security (5). Risk profile is high: 0 critical, 4 high, 3 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 16 of 27 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low 9-layer quality integrity conf 1.00 60 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `AXIOM_403_BACKOFF_MS`, `AXIOM_DISCOVER_ENABLED`, `AXIOM_DISCOVER_SYNC_INTERVAL_MS`, `AXIOM_DISCOVER_URL`, `AXIOM_MAX_CANDIDATES`, `BOT_PASSWORD`, `BURST_ACTIVITY_THRESHOLD`, `BURST_ACTIVITY_WINDOW_MS` + 52 more. Add them (with a placeholder/commen…

integrityconfig-drift

low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: core-engine/setup_security.ts

Source file with no class/function declarations — possible config, dead code, or scratch file.

dead-code-candidate

low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: core-engine/src/types.ts

Source file with no class/function declarations — possible config, dead code, or scratch file.

dead-code-candidate

low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: core-engine/src/types/bs58.d.ts

Source file with no class/function declarations — possible config, dead code, or scratch file.

dead-code-candidate

low 9-layer frontend frontend-quality conf 1.00 Stray `console.log` in TS/JS — core-engine/setup_security.ts:9

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

frontend-qualityfq.console-leak

low 9-layer frontend frontend-quality conf 1.00 Stray `console.log` in TS/JS — core-engine/src/bot.ts:533

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

frontend-qualityfq.console-leak

low 9-layer frontend frontend-quality conf 1.00 Stray `console.log` in TS/JS — core-engine/src/solana.ts:189

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

frontend-qualityfq.console-leak

low 9-layer frontend frontend-quality conf 1.00 Stray `console.log` in TS/JS — core-engine/src/tests/risk_guards.test.ts:10

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

frontend-qualityfq.console-leak

low 9-layer api wiring conf 1.00 Unused endpoint: GET /api/status

`core-engine/src/api_server.ts` declares `GET /api/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 documenting who consumes it.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /config

`ai-engine/main.py` declares `GET /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 documenting who consumes it.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /analyze

`ai-engine/main.py` declares `POST /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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /analyze-momentum

`ai-engine/main.py` declares `POST /analyze-momentum` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /analyze-sniping

`ai-engine/main.py` declares `POST /analyze-sniping` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /api/config

`core-engine/src/api_server.ts` declares `POST /api/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 documenting who consumes it.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /config

`ai-engine/main.py` declares `POST /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 documenting who consumes it.

wiringunused-endpoint

low 9-layer quality complexity conf 1.00 Very large file: core-engine/src/bot.ts (3904 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

complexity

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}

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/c873bdae-e3a1-4511-b06a-76dc4f3ed03f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c873bdae-e3a1-4511-b06a-76dc4f3ed03f/

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.