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

Scan timing: clone 3.99s · analysis 13.03s · 10.1 MB · GitHub API rate-limit (preflight)

chef/supermarket

https://github.com/chef/supermarket · scanned 2026-06-05 18:26 UTC (4 days, 19 hours ago) · 10 languages

319 raw signals (219 security + 100 graph) System graph score 76 (lower by 25)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 19 hours ago · v2 · 206 actionable findings from 2 signal sources. 63 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 65.0 0.15 9.75
security_score 22.9 0.25 5.72
testing_score 15.0 0.20 3.00
documentation_score 85.0 0.15 12.75
practices_score 80.0 0.15 12.00
code_quality 72.9 0.10 7.29
Overall 1.00 50.5
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 1 finding
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/`.
1 matching finding on this repo
  • info Commented-code block (8 lines) in src/supermarket/spec/javascripts/config/karma…
View all commented-out code findings →
Config drift 6 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.
6 matching findings on this repo
  • low File has no detected symbols: src/supermarket/engines/fieri/spec/dummy/app/asse…
  • low File has no detected symbols: src/supermarket/spec/javascripts/config/sprockets…
  • low File has no detected symbols: src/supermarket/spec/javascripts/config/karma.con…
  • low File has no detected symbols: src/supermarket/spec/javascripts/config/specHelpe…
  • low File has no detected symbols: src/supermarket/app/assets/config/manifest.js
  • info Commented-code block (8 lines) in src/supermarket/spec/javascripts/config/karma…
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/8fa01497-35dc-4e5f-a82a-98da800f40c7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8fa01497-35dc-4e5f-a82a-98da800f40c7/

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.