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.

Sepnexus/leadintel-ACQ

https://github.com/Sepnexus/leadintel-ACQ · scanned 2026-06-16 00:07 UTC (2 months, 2 weeks ago)

393 raw signals (0 security + 393 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 386 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 1 Medium 235 Low 79 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 386 Crowd 0 Layer: Frontend 65 Hardware 10 Security 160 Cicd 1 Quality 150

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.

Commented-out code 56 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 platform-admin-api/src/auth.ts:3
info Commented-code block (6 lines) in platform-admin-api/src/lib/wallet-mirror.ts:4
info Commented-code block (5 lines) in platform-admin-api/src/lib/app-customer.ts:31
info Commented-code block (5 lines) in platform-admin-api/src/lib/sync-scheduler.ts:8
info Commented-code block (5 lines) in platform-admin-api/src/lib/provisioning.ts:3
info Commented-code block (6 lines) in platform-admin-api/src/lib/auto-recharge.ts:4
info Commented-code block (5 lines) in platform-admin-api/src/routes/sso.ts:4
info Commented-code block (9 lines) in platform-admin-api/src/routes/topup.ts:3
info Commented-code block (6 lines) in platform-admin-api/src/routes/stripe-webhook.…
info Commented-code block (6 lines) in platform-admin-api/src/routes/users-password.…
info Commented-code block (5 lines) in platform-admin-api/src/routes/customers.ts:262
info Commented-code block (6 lines) in platform-admin-api/src/routes/master-keys.ts:3

View all commented-out code findings →

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

5 matching findings on this repo

high Agent instruction/config may expose a secret: leadintel-selfhost/CLAUDE.md leadintel-selfhost/CLAUDE.md:67
info Commented-code block (6 lines) in my-acq-coach-5b771b53/playwright.config.ts:4
info Commented-code block (6 lines) in acq-coach-selfhost/apps/web/playwright.config…
info Commented-code block (6 lines) in closercontrolleadintel/playwright.config.ts:4
info Commented-code block (6 lines) in leadintel-selfhost/apps/web/playwright.config…

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/a63ad75a-e2aa-4f20-ad2c-52abc605bbe4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a63ad75a-e2aa-4f20-ad2c-52abc605bbe4/

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.