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.

rohitkaul90/tablelab

https://github.com/rohitkaul90/tablelab · scanned 2026-06-15 23:55 UTC (2 months, 3 weeks ago)

50 raw signals (0 security + 50 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 43 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

77.8% cov · 43 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 18 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 43 Crowd 0 Layer: Frontend 5 Security 5 Cicd 4 Quality 29

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 6 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/`.

6 matching findings on this repo

info Commented-code block (5 lines) in scripts/ai-cost-report.mjs:5
info Commented-code block (13 lines) in scripts/smoke-test.mjs:10
info Commented-code block (10 lines) in scripts/daily-digest.mjs:11
info Commented-code block (6 lines) in supabase/functions/analyze-session/index.ts:5…
info Commented-code block (14 lines) in supabase/functions/analyze-hand/index.ts:439
info Commented-code block (6 lines) in supabase/functions/_shared/alert.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

medium CI is configured but no tests are detected
high Agent instruction/config may expose a secret: .claude/commands/mobile-specialis… .claude/commands/mobile-specialist.md:82
high Agent instruction/config may expose a secret: .claude/commands/devops-engineer.… .claude/commands/devops-engineer.md:369
high Agent instruction/config may expose a secret: .claude/commands/security-analyst… .claude/commands/security-analyst.md:157
high Agent instruction/config may expose a secret: .claude/commands/ai-data-engineer… .claude/commands/ai-data-engineer.md:230

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/ed7b60e6-ba53-4bd9-9465-97c3c76ef2c5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ed7b60e6-ba53-4bd9-9465-97c3c76ef2c5/

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.