— Repobility public scan

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.

DanOps-1/Gpt-Agreement-Payment

https://github.com/DanOps-1/Gpt-Agreement-Payment · scanned 2026-05-17 01:36 UTC (14 hours, 45 minutes ago) · 10 languages

249 findings (16 legacy + 233 scanner) 84th percentile · Python · medium (20-100K LoC) Scanner says 68 (higher by 12)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 14 hours, 44 minutes ago · v2 · 132 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

100.0% cov · 116 gaps

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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.

Fragile runtime 8 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

8 matching findings on this repo

medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … CTF-pay/hcaptcha_auto_solver.py:3042
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … CTF-pay/gopay.py:162
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … CTF-pay/card.py:158
medium localStorage write failures are swallowed silently webui/frontend/src/views/Run.vue:575
medium Codex session log reader may expose prompts or tool-call content CTF-reg/auth_flow.py:174
low Duplicated implementation block across source files webui/frontend/src/views/Setup.vue:28
low Duplicated implementation block across source files webui/frontend/src/components/steps/Step09_VLM.vue:13
low Duplicated implementation block across source files webui/frontend/src/components/steps/Step08_Captch…:12

View all fragile runtime findings →

Legacy markers 2 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.

2 matching findings on this repo

low Legacy-named symbol `wa_otp_legacy` in webui/backend/db.py:23
low Legacy-named symbol `sentinel_v1_legacy` in CTF-reg/sentinel.py:7

View all legacy markers findings →

Commented-out code 2 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/`.

2 matching findings on this repo

info Commented-code block (5 lines) in CTF-reg/browser_register.py:271
info Commented-code block (6 lines) in CTF-pay/card.py:2546

View all commented-out code findings →

Config drift 3 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.

3 matching findings on this repo

low File has no detected symbols: webui/frontend/vite.config.ts
low File has no detected symbols: webui/frontend/vitest.config.ts
high FastAPI POST `export` without auth dependency — webui/backend/routes/config.py:… webui/backend/routes/config.py:26

View all config drift findings →

{# ── 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/6af2fc05-432f-4cf8-b415-4aa1a7b84868/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6af2fc05-432f-4cf8-b415-4aa1a7b84868/

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.