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.

shaktisingh204/wachat

https://github.com/shaktisingh204/wachat · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

1838 raw signals (0 security + 1838 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 1829 actionable findings from 1 signal source. 9 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 · 1829 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 293 Medium 259 Low 402 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1829 Crowd 0 Layer: Software 3 Frontend 845 Network 4 Hardware 3 Security 103 Cicd 3 Quality 603 Api 265

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 23 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 Old/deprecated-named symbol `buildYDocFromLegacy` in scripts/sabflow/migrate-do…
low Old/deprecated-named symbol `normalizeLegacy` in src/components/20ui-domain/adm…
low Old/deprecated-named symbol `normalizeLegacy` in src/components/20ui-domain/pla…
low Old/deprecated-named symbol `waitForExecutionLegacy` in src/app/api/sabflow/web…
low Old/deprecated-named symbol `rustDocToLegacy` in src/app/actions/crm-accounts.a…
low Old/deprecated-named symbol `sendTelegramBroadcastNowLegacy` in src/app/actions…
low Old/deprecated-named symbol `rustContactDocToLegacy` in src/app/actions/crm.act…
low Old/deprecated-named symbol `lineItemsLegacy` in src/app/actions/crm-invoices.a…
low Old/deprecated-named symbol `rustDocToLegacy` in src/app/actions/crm-deals.acti…
low Old/deprecated-named symbol `rustDeptToLegacy` in src/app/actions/crm-employees…
low Old/deprecated-named symbol `rustDocToLegacy` in src/app/actions/crm-products.a…
low Old/deprecated-named symbol `rustDocToLegacy` in src/app/actions/crm-vendors.ac…

View all legacy markers findings →

Commented-out code 236 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.js:71
info Commented-code block (5 lines) in worker.js:235
info Commented-code block (5 lines) in fix_fmtdate.js:25
info Commented-code block (8 lines) in next.config.js:32
info Commented-code block (5 lines) in tests/sabflow-worker/roundtrip.test.ts:79
info Commented-code block (5 lines) in scripts/zoru-codemod-safe.mjs:161
info Commented-code block (5 lines) in scripts/sabsms-e2e.mjs:347
info Commented-code block (5 lines) in scripts/chunk35_step4.py:22
info Commented-code block (6 lines) in scripts/zoru-codemod.mjs:384
info Commented-code block (6 lines) in scripts/zoru-fixer.mjs:88
info Commented-code block (5 lines) in scripts/db/backfill-users.mjs:131
info Commented-code block (5 lines) in services/sabflow-ws/test/fuzz/protocol.fuzz.t…

View all commented-out code findings →

Config drift 15 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

low Very large file: src/config/dashboard-config.ts (856 lines)
medium Runtime service client appears to use placeholder configuration
info Commented-code block (7 lines) in ecosystem.config.js:71
info Commented-code block (8 lines) in next.config.js:32
medium `fetch()` without try/.catch or AbortSignal — next.config.js:71
info Commented-code block (5 lines) in src/app/sabsms/_components/sabsms-sidebar-con…
info Commented-code block (5 lines) in src/lib/sabflow/n8n/internal/config-stub.d.ts…
high Dangling fetch: POST https://graph.facebook.com/${API_VERSION}/${project.wabaId…
high Dangling fetch: POST https://graph.facebook.com/${API_VERSION}/${project.wabaId…
high Dangling fetch: POST https://graph.facebook.com/${API_VERSION}/${project.wabaId…
high Dangling fetch: DELETE https://graph.facebook.com/${API_VERSION}/${project.waba…
high Dangling fetch: GET https://graph.facebook.com/${API_VERSION}/${project.wabaId}…

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/a373e772-96a1-4a00-9fec-e66981053c4c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a373e772-96a1-4a00-9fec-e66981053c4c/

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.