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.

Steviewonders99/OneTake

https://github.com/Steviewonders99/OneTake · scanned 2026-06-16 00:23 UTC (2 months, 2 weeks ago)

362 raw signals (18 security + 344 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
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.

Duplicates & near-duplicates 4 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.
4 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 4 places repo-level
  • low Near-duplicate function bodies in 7 places
  • low Near-duplicate function bodies in 12 places
View all duplicates & near-duplicates findings →
Commented-out code 46 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 (7 lines) in tests/components/insights/deep-dive/path-expl…
  • info Commented-code block (5 lines) in scripts/seed_project_aliases.py:93
  • info Commented-code block (5 lines) in scripts/seed_all_ga4_funnels.py:110
  • info Commented-code block (6 lines) in worker/db_proxy.py:92
  • info Commented-code block (5 lines) in worker/platforms/meta_organic.py:21
  • info Commented-code block (6 lines) in worker/ai/sedeo_client.py:38
  • info Commented-code block (7 lines) in worker/scripts/sync_real_funnel.py:62
  • info Commented-code block (5 lines) in worker/scripts/backfill_ga4_event_user_grain.…
  • info Commented-code block (5 lines) in worker/scripts/sync_ga4_mp_outbox.py:239
  • info Commented-code block (7 lines) in worker/scripts/sync_platform_outcomes.py:221
  • info Commented-code block (6 lines) in worker/scripts/cron_sync_all.py:82
  • info Commented-code block (7 lines) in worker/scripts/sync_funnel_paths.py:222
View all commented-out code findings →
Config drift 1 finding
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.
1 matching finding on this repo
  • info `truncate` class without `title=` for hover reveal — src/components/insights/Wi…
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/48dccb40-2be8-45e8-a44b-4fabb6785918/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/48dccb40-2be8-45e8-a44b-4fabb6785918/

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.