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.
Sign up free Scan another repo

roopbreak/achat

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

177 raw signals (0 security + 177 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 174 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
69.7
/100
Security checks
70
0 findings
System graph
70
100.0% cov · 174 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 4 Medium 70 Low 69 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 174 Crowd 0 Layer: Frontend 9 Hardware 3 Security 16 Cicd 1 Quality 91 Api 54

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 25 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 docs/stories/dayoung-piled-up/build-payloads-…
  • info Commented-code block (5 lines) in docs/stories/momo-surrogate/build-payloads.mj…
  • info Commented-code block (7 lines) in docs/stories/momo-surrogate/build-payloads-v2…
  • info Commented-code block (5 lines) in docs/stories/bangkok-poolvilla/build-payloads…
  • info Commented-code block (5 lines) in docs/stories/male-conservation-clinic/apply-r…
  • info Commented-code block (6 lines) in docs/stories/summer-village-harem/build-paylo…
  • info Commented-code block (7 lines) in docs/stories/summer-village-harem/build-paylo…
  • info Commented-code block (5 lines) in docs/stories/캠퍼스퀸/smoke-test-v2.mjs:1
  • info Commented-code block (5 lines) in docs/stories/캠퍼스퀸/apply-remote.mjs:1
  • info Commented-code block (5 lines) in docs/stories/캠퍼스퀸/apply-remote-v2.mjs:1
  • info Commented-code block (6 lines) in scripts/migrate-to-slug.mjs:10
  • info Commented-code block (10 lines) in scripts/generate-duo-scenes.mjs:9
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
  • medium Runtime service client appears to use placeholder configuration
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/0df22151-8eea-4b0b-95ba-a49a8abc5e7a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0df22151-8eea-4b0b-95ba-a49a8abc5e7a/

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.