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

elsenorchris-openclaw/judgebot

https://github.com/elsenorchris-openclaw/judgebot · scanned 2026-06-16 04:22 UTC (2 months ago)

44 raw signals (0 security + 44 graph)

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

Complete repo analysis

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

JSON
Combined
98.2
/100
Security checks
98
0 findings
System graph
98
66.7% cov · 40 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 3 Low 21 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 40 Crowd 0 Layer: Software 6 Quality 34
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 98.2/100 with 66.7% coverage. It contains 487 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 44 findings — concentrated in quality (36), software (8). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 24 of 40 actionable findings. 44 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 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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 12 placeholder/mock markers across 3 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 Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 47 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 8 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ANTHROPIC_API_KEY`, `DISCORD_BOT_TOKEN`, `DISCORD_CHANNEL_ID`, `DISCORD_TRADE_CHANNEL_ID`, `JUDGE_NWS_FC_HISTORY_DIR`, `JUDGE_PRES_HISTORY_DIR`, `OPEN_METEO_API_KEY`, `WETHR_API_KEY`. Add them (with a placeholder/comment) to .env.example so onboar…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 134 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 quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: kalshi_client.py:get_orderbook, kalshi_client.py:get_order 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.
3 occurrences
repo-level (3 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 quality Integrity conf 1.00 Old/deprecated-named symbol `nbp_cache_v1` in nbp_reader.py:3
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 `pace_curves_v2` in config.py:672
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 `pace_curves_v2` in nn_shadow_worker.py:681
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 `pace_curves_v2` in paper_judge_bot.py:89
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 `paper_min_bot_v2` in shared_cache_reader.py:3
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_one
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
wethr_rm.py:145
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_one
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
wethr_client.py:60
low System graph software Dead code conf 1.00 Possibly dead Python function: judge_entry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
judgment.py:1288
low System graph software Dead code conf 1.00 Possibly dead Python function: list_claims
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
state.py:190
low System graph software Dead code conf 1.00 Possibly dead Python function: refresh_wallet_positions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
paper_judge_bot.py:288
low System graph software Dead code conf 1.00 3 occurrences Possibly dead Python function: stop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
3 files, 3 locations
nn_shadow_worker.py:3156
obs_refresh.py:60
wethr_rm.py:139
low System graph quality Complexity conf 1.00 Very large file: cell_mae_table.py (1218 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: config.py (1403 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: judgment.py (1343 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: nn_shadow_worker.py (3171 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: paper_judge_bot.py (4629 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/168ce565-8a84-4f98-a13e-fbfdca63a2a3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/168ce565-8a84-4f98-a13e-fbfdca63a2a3/

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.