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.

StephPonce/oubon_mailbot

https://github.com/StephPonce/oubon_mailbot · scanned 2026-06-16 00:22 UTC (2 months, 2 weeks ago)

442 raw signals (3 security + 439 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 410 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 156 Medium 30 Low 131 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 410 Crowd 0 Layer: Quality 167 Cicd 3 Software 18 Frontend 15 Network 1 Hardware 3 Security 156 Api 50

Exclude dismissed / FP Exclude test files

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.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

low Very large file: archive/legacy_mailbot/main.py (1649 lines)
low Old/deprecated-named symbol `product_intelligence_v2` in archive/legacy_mailbot…
info Commented-code block (6 lines) in archive/legacy_mailbot/main.py:760
medium Network/subprocess call without timeout or try/except — archive/legacy_mailbot/…
info Commented-code block (5 lines) in archive/legacy_mailbot/app/email_processor.py…
low Old/deprecated-named symbol `test_decrypt_with_wrong_key_falls_back_to_legacy` …
low Old/deprecated-named symbol `shopify_legacy` in ospra_os/api/shopify_routes.py:…
high FastAPI POST `gmail_ingest` without auth dependency — archive/legacy_mailbot/ma… archive/legacy_mailbot/main.py:279
high FastAPI POST `gmail_send_demo` without auth dependency — archive/legacy_mailbot… archive/legacy_mailbot/main.py:290
high FastAPI POST `templates_upsert` without auth dependency — archive/legacy_mailbo… archive/legacy_mailbot/main.py:367
high FastAPI POST `set_rules` without auth dependency — archive/legacy_mailbot/main.… archive/legacy_mailbot/main.py:378
high FastAPI POST `ensure_labels` without auth dependency — archive/legacy_mailbot/m… archive/legacy_mailbot/main.py:394

View all legacy markers findings →

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

12 matching findings on this repo

info Commented-code block (5 lines) in frontend/vite.config.js:16
info Commented-code block (6 lines) in frontend/src/App.jsx:21
info Commented-code block (5 lines) in frontend/src/components/ProductDiscovery.jsx:…
info Commented-code block (13 lines) in frontend/src/components/auth/LoginForm.jsx:35
info Commented-code block (6 lines) in frontend/src/services/api.js:344
info Commented-code block (6 lines) in archive/legacy_mailbot/main.py:760
info Commented-code block (5 lines) in archive/legacy_mailbot/app/email_processor.py…
info Commented-code block (7 lines) in tests/conftest.py:61
info Commented-code block (7 lines) in tests/test_differentiation.py:52
info Commented-code block (5 lines) in tests/integration/test_tenant_isolation_scaff…
info Commented-code block (8 lines) in tests/unit/test_action_executor.py:164
info Commented-code block (8 lines) in ospra_os/main.py:9

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

medium Runtime service client appears to use placeholder configuration
info Commented-code block (5 lines) in frontend/vite.config.js:16
high FastAPI POST `configure_partner_domain` without auth dependency — ospra_os/whit… ospra_os/whitelabel/routes.py:358

View all config drift findings →

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/6cc88e22-8c14-4140-a0c2-47328ac0a513/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6cc88e22-8c14-4140-a0c2-47328ac0a513/

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.