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

Timaroc13/polymarket-engine

https://github.com/Timaroc13/polymarket-engine · scanned 2026-06-16 00:36 UTC (2 months, 2 weeks ago)

53 raw signals (0 security + 53 graph)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 51 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
54.9
/100
Security checks
55
0 findings
System graph
55
100.0% cov · 51 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 13 Medium 6 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 51 Crowd 0 Layer: Software 2 Hardware 3 Frontend 1 Cicd 1 Quality 19 Security 10 Api 15
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 54.9/100 with 100.0% coverage. It contains 598 nodes across 15 cross-layer flows, written primarily in mixed languages. Engine surfaced 53 findings — concentrated in quality (20), api (15), security (10). Risk profile is high: 0 critical, 13 high, 6 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 45 of 51 actionable findings. 53 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 quality Integrity conf 1.00 Blocking `urllib.request.urlopen(...)` inside `async def estimate_p_model` — src/crypto_news_parser/llm_adapter.py:124
Sync I/O inside an async function blocks the event loop. While `urllib.request.urlopen(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asy…
src/crypto_news_parser/llm_adapter.py:124 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `urllib.request.urlopen(...)` inside `async def estimate_p_model` — src/crypto_news_parser/llm_adapter.py:241
Sync I/O inside an async function blocks the event loop. While `urllib.request.urlopen(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asy…
src/crypto_news_parser/llm_adapter.py:241 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `urllib.request.urlopen(...)` inside `async def refine` — src/crypto_news_parser/llm_adapter.py:178
Sync I/O inside an async function blocks the event loop. While `urllib.request.urlopen(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asy…
src/crypto_news_parser/llm_adapter.py:178 Sync io in asyncPerformance
high System graph security auth conf 1.00 FastAPI POST `feedback` without auth dependency — src/crypto_news_parser/main.py:410
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:410 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `flow_scan` without auth dependency — src/crypto_news_parser/main.py:673
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:673 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `parse_url` without auth dependency — src/crypto_news_parser/main.py:453
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:453 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `parse` without auth dependency — src/crypto_news_parser/main.py:274
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:274 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `poll_resolutions` without auth dependency — src/crypto_news_parser/main.py:820
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:820 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `release_deployed` without auth dependency — src/crypto_news_parser/main.py:618
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:618 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reset_deployed` without auth dependency — src/crypto_news_parser/main.py:632
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:632 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `risk` without auth dependency — src/crypto_news_parser/main.py:586
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:586 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `signal` without auth dependency — src/crypto_news_parser/main.py:520
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:520 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `track_market_endpoint` without auth dependency — src/crypto_news_parser/main.py:741
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/crypto_news_parser/main.py:741 securityAuth fastapi unauth mutation
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. 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 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: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALERT_MIN_TIER`, `DB_PATH`, `PAPER_FEE`, `PAPER_STAKE`, `RUN_GOLDEN_STRICT`. 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 36 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: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 14, 17
.github/workflows/ci.yml:14, 17 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/crypto_news_parser/models.py:validate_text, src/crypto_news_parser/models.py:validate_text 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 sepa…
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: src/crypto_news_parser/llm_adapter.py:refine, src/crypto_news_parser/llm_adapter.py:refine, src/crypto_news_parser/llm_adapter.py:refine, src/crypto_news_parser/llm_adapter.py:refine This is *the* AI-coder failure mode (4× more duplication in vibe-co…
2 occurrences
repo-level (2 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 `model_copy` in src/crypto_news_parser/main.py:595
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 `too_old` in tests/test_wallet_flow.py:127
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: key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/crypto_news_parser/parser.py:1057
low System graph software Dead code conf 1.00 Possibly dead Python function: resolve_jurisdiction
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/crypto_news_parser/parser.py:274
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 quality Integrity conf 1.00 Stub function `estimate_p_model` (body is just `pass`/`return`) — src/crypto_news_parser/llm_adapter.py:81
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`src/crypto_news_parser/main.py` declares `GET /` 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 /dashboard
`src/crypto_news_parser/main.py` declares `GET /dashboard` 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 /dashboard/data
`src/crypto_news_parser/main.py` declares `GET /dashboard/data` 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 /deployed
`src/crypto_news_parser/main.py` declares `GET /deployed` 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 /flow-calibration
`src/crypto_news_parser/main.py` declares `GET /flow-calibration` 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 /deployed/release
`src/crypto_news_parser/main.py` declares `POST /deployed/release` 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 /deployed/reset
`src/crypto_news_parser/main.py` declares `POST /deployed/reset` 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 /feedback
`src/crypto_news_parser/main.py` declares `POST /feedback` 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 /flow-scan
`src/crypto_news_parser/main.py` declares `POST /flow-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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /parse
`src/crypto_news_parser/main.py` declares `POST /parse` 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 /parse_url
`src/crypto_news_parser/main.py` declares `POST /parse_url` 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 /poll-resolutions
`src/crypto_news_parser/main.py` declares `POST /poll-resolutions` 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 /risk
`src/crypto_news_parser/main.py` declares `POST /risk` 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 /signal
`src/crypto_news_parser/main.py` declares `POST /signal` 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 /track-market
`src/crypto_news_parser/main.py` declares `POST /track-market` 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
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/5746fd0b-be00-4114-9c94-2e3978a89224/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5746fd0b-be00-4114-9c94-2e3978a89224/

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.