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.
45 of your 134 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.64s · analysis 41.65s · 4.4 MB · GitHub API rate-limit (preflight)

simpx/loopat

https://github.com/simpx/loopat · scanned 2026-06-05 17:42 UTC (4 days, 22 hours ago) · 10 languages

698 raw signals (120 security + 578 graph) 39th percentile · Typescript · medium (20-100K LoC) System graph score 46 (higher by 21)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 22 hours ago · v2 · 345 actionable findings from 2 signal sources. 64 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 58.2 0.25 14.55
testing_score 85.0 0.20 17.00
documentation_score 68.7 0.15 10.30
practices_score 75.0 0.15 11.25
code_quality 46.3 0.10 4.63
Overall 1.00 66.7
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 35 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 (6 lines) in dogfood/playwright.config.ts:34
  • info Commented-code block (12 lines) in dogfood/setup.ts:64
  • info Commented-code block (5 lines) in dogfood/first-5-minutes/journey.spec.ts:164
  • info Commented-code block (7 lines) in dogfood/sync/sync.spec.ts:126
  • info Commented-code block (5 lines) in dogfood/sync/zzz-s3-ai.spec.ts:46
  • info Commented-code block (6 lines) in dogfood/context-notes-sync/journey.spec.ts:157
  • info Commented-code block (7 lines) in dogfood/first-run/setup.ts:77
  • info Commented-code block (9 lines) in dogfood/first-run/journey.spec.ts:239
  • info Commented-code block (5 lines) in dogfood/second-loop-warm/journey.spec.ts:214
  • info Commented-code block (5 lines) in dogfood/concurrent-push/journey.spec.ts:124
  • info Commented-code block (5 lines) in scripts/loopat.ts:260
  • info Commented-code block (6 lines) in web/src/useLoopRuntime.tsx:589
View all commented-out code findings →
Config drift 7 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.
7 matching findings on this repo
  • high Express PUT /api/serve/config has no auth server/src/index.ts:175
  • info `truncate` class without `title=` for hover reveal — web/src/components/setting…
  • info `truncate` class without `title=` for hover reveal — web/src/components/setting…
  • low Very large file: web/src/components/settings/MiseConfigPanel.tsx (1517 lines)
  • info Commented-code block (6 lines) in dogfood/playwright.config.ts:34
  • low Unused endpoint: GET /api/serve/config
  • low Unused endpoint: PUT /api/serve/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/b60525ac-5073-488b-b96c-88a6cf0caf4c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b60525ac-5073-488b-b96c-88a6cf0caf4c/

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.