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.

withdoron/locallane

https://github.com/withdoron/locallane · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

94 raw signals (2 security + 92 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 94 actionable findings from 2 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 92 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 15 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 2 System graph 92 Crowd 0 Layer: Quality 61 Api 1 Frontend 28 Security 4

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 45 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 middleware.ts:74
info Commented-code block (6 lines) in next.config.ts:8
info Commented-code block (7 lines) in scripts/replay-accept-as-test.mjs:7
info Commented-code block (6 lines) in scripts/verify-client-projects.mjs:6
info Commented-code block (25 lines) in scripts/smoke-test-create-invitation.mjs:15
info Commented-code block (7 lines) in scripts/verify-6-4b-2-ledger-tiles.mjs:4
info Commented-code block (12 lines) in scripts/verify-scheduler.mjs:7
info Commented-code block (5 lines) in scripts/verify-estimate-write-path.mjs:6
info Commented-code block (15 lines) in scripts/verify-trade-taxonomy.mjs:9
info Commented-code block (14 lines) in scripts/verify-change-orders.mjs:4
info Commented-code block (7 lines) in scripts/verify-6-4b-1-payments.mjs:4
info Commented-code block (6 lines) in scripts/diagnose-cross-user-accept.mjs:4

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 Commented-code block (6 lines) in next.config.ts:8

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/a210dff2-2e2e-4392-8496-7315f29b01bd/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a210dff2-2e2e-4392-8496-7315f29b01bd/

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.