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

rashadrahimov/leaddrive-v2

https://github.com/rashadrahimov/leaddrive-v2 · scanned 2026-06-15 23:48 UTC (2 months, 3 weeks ago)

2083 raw signals (0 security + 2083 graph)

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

Complete repo analysis

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

JSON
Combined
45.3
/100
Security checks
45
0 findings
System graph
45
100.0% cov · 2070 findings
Critical
9
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 9 High 1136 Medium 285 Low 132 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 2070 Crowd 0 Layer: Software 8 Frontend 256 Network 2 Hardware 4 Security 41 Cicd 1 Quality 624 Api 1134

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 4 places repo-level
  • low Near-duplicate function bodies in 2 places repo-level
View all duplicates & near-duplicates findings →
Legacy markers 9 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.
9 matching findings on this repo
  • info `truncate` class without `title=` for hover reveal — src/app/(dashboard)/inbox/…
  • medium `fetch()` without try/.catch or AbortSignal — src/app/(dashboard)/inbox/legacy/…
  • low Old/deprecated-named symbol `hex_legacy` in src/lib/payments/providers/stripe.t…
  • high Dangling fetch: GET /api/v1/inbox${params} (src/app/(dashboard)/inbox/legacy/pa…
  • high Dangling fetch: GET /api/v1/contacts?limit=500 (src/app/(dashboard)/inbox/legac…
  • high Dangling fetch: POST /api/v1/inbox (src/app/(dashboard)/inbox/legacy/page.tsx:2…
  • high Dangling fetch: POST /api/v1/inbox (src/app/(dashboard)/inbox/legacy/page.tsx:2…
  • high Dangling fetch: PATCH /api/v1/inbox (src/app/(dashboard)/inbox/legacy/page.tsx:…
  • high Dangling fetch: DELETE /api/v1/inbox (src/app/(dashboard)/inbox/legacy/page.tsx…
View all legacy markers findings →
Commented-out code 336 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 ecosystem.config.cjs:26
  • info Commented-code block (5 lines) in next.config.ts:12
  • info Commented-code block (13 lines) in generated/logos/master-d-notch.mjs:14
  • info Commented-code block (5 lines) in scripts/seed-mtm.ts:65
  • info Commented-code block (7 lines) in scripts/seed-tenant-demo.mjs:82
  • info Commented-code block (6 lines) in scripts/_rls.mjs:1
  • info Commented-code block (6 lines) in scripts/seed-plan-templates.mjs:9
  • info Commented-code block (6 lines) in scripts/backfill-group-modules.mjs:1
  • info Commented-code block (8 lines) in scripts/backfill-sales-module.mjs:1
  • info Commented-code block (5 lines) in scripts/migrate-v1.ts:24
  • info Commented-code block (5 lines) in scripts/lint-encrypted-columns.mjs:155
  • info Commented-code block (5 lines) in scripts/farid-edge-cases.ts:308
View all commented-out code findings →
Config drift 46 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.
12 matching findings on this repo
  • medium Runtime service client appears to use placeholder configuration
  • info Commented-code block (7 lines) in ecosystem.config.cjs:26
  • medium `fetch()` without try/.catch or AbortSignal — ecosystem.config.cjs:30
  • info Commented-code block (5 lines) in next.config.ts:12
  • info Commented-code block (5 lines) in src/components/channel-config-form.tsx:233
  • medium `fetch()` without try/.catch or AbortSignal — src/components/budget-config-tab.…
  • medium `fetch()` without try/.catch or AbortSignal — src/components/boards/config-tabl…
  • medium `fetch()` without try/.catch or AbortSignal — src/app/(dashboard)/settings/budg…
  • info Commented-code block (5 lines) in src/lib/marketing-attribution/model-config-va…
  • high Dangling fetch: POST /api/v1/channels/sms/test (src/components/channel-config-f…
  • high Dangling fetch: GET /api/budgeting/config?type=departments (src/components/budg…
  • high Dangling fetch: GET /api/budgeting/cost-types?includeInactive=true (src/compone…
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/2a8006bf-4d6c-4955-9e1c-a51f091a6cae/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2a8006bf-4d6c-4955-9e1c-a51f091a6cae/

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.