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

yody38/KizCapital-Battle-of-Bots

https://github.com/yody38/KizCapital-Battle-of-Bots · scanned 2026-06-16 01:06 UTC (2 months, 1 week ago)

58 raw signals (0 security + 58 graph)

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

Complete repo analysis

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

JSON
Combined
64.8
/100
Security checks
65
0 findings
System graph
65
88.9% cov · 43 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 0 Medium 13 Low 21 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 43 Crowd 0 Layer: Software 6 Frontend 5 Data 1 Hardware 4 Security 2 Cicd 3 Quality 22
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 64.8/100 with 88.9% coverage. It contains 676 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 58 findings — concentrated in quality (28), cicd (12), software (6). Risk profile is low: 0 critical, 0 high, 15 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 34 of 43 actionable findings. 58 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — app.js:1236
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 — scripts/cdp_verify_auth.js:49
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 — scripts/cdp_verify_live.js:44
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/cdp_verify_timing.js:41
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 — scripts/dashboard_audit.js:68
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase-client.js:94
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 hardware Security conf 1.00 Dockerfile runs as root: railway/live-bridge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
tailscale/github-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 3 locations
.github/workflows/mcp-health.yml:33
.github/workflows/refresh.yml:35
.github/workflows/sampler-tick.yml:41
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/refresh.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app.js:353
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app.js:353 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in app.js:592
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
app.js:592 Insert adjacent html
medium System graph data Coverage conf 1.00 ORM models found but no DB engine detected
The repo defines tables/models but no DB connection string was found. Likely lives in env vars or a config file the scanner didn't read.
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 32 source file(s) (ratio 0.03). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 14 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AUTO_RECOVERY`, `LIVE_INTERVAL_SECS`, `LIVE_VPS_TAG`, `MCP_HEALTH_LOW_RAM_MB`, `MCP_HEALTH_RAM_CRITICAL_MB`, `MCP_HEALTH_STALE_SEC`, `R2_ACCESS_KEY_ID`, `R2_ACCOUNT_ID` + 6 more. Add them (with a placeholder/comment) to .env.example so onboarding …
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 101 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: debian:bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
railway/live-bridge/Dockerfile:11 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: tailscale/tailscale:stable
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
railway/live-bridge/Dockerfile:9 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 8 locations
.github/workflows/refresh.yml:54, 79, 86, 95 (4 hits)
.github/workflows/mcp-health.yml:41, 61, 68 (3 hits)
.github/workflows/integrity-watchdog.yml:38
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/fetch_ledger.py:load_env, scripts/emit_timing.py:load_env This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: gross_pl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_metrics.py:100
low System graph software Dead code conf 1.00 Possibly dead Python function: latest_run_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/dispatch_refresh.py:91
low System graph software Dead code conf 1.00 Possibly dead Python function: load_cursor
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/promote_to_runbook.py:39
low System graph software Dead code conf 1.00 Possibly dead Python function: max_drawdown_from_series
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_metrics.py:174
low System graph software Dead code conf 1.00 Possibly dead Python function: sortino_annualized
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_metrics.py:198
low System graph software Dead code conf 1.00 Possibly dead Python function: wilson_lb
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/_metrics.py:78
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 — scripts/cdp_verify_auth.js:169
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/cdp_verify_live.js:143
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/cdp_verify_timing.js:132
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/dashboard_audit.js:46
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 quality Complexity conf 1.00 Very large file: app.js (5939 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/post_merge.py (3005 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/e3f861c2-b7c4-439a-82ba-999c8d4340b4/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e3f861c2-b7c4-439a-82ba-999c8d4340b4/

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.