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.

dougsimpsoncodes/PinkAutoGlassWebsite

https://github.com/dougsimpsoncodes/PinkAutoGlassWebsite · scanned 2026-06-17 01:59 UTC (1 month, 1 week ago)

947 raw signals (0 security + 947 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -34.1 (diff) · 939 actionable findings from 1 signal source. 8 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 939 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 154 Medium 486 Low 261 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 939 Crowd 0 Layer: Frontend 447 Network 1 Security 218 Cicd 3 Quality 115 Api 155

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 31 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 next.config.js:108
info Commented-code block (5 lines) in scripts/audit-geo-citability.mjs:188
info Commented-code block (5 lines) in scripts/backfill-market-user-sessions.ts:52
info Commented-code block (7 lines) in src/app/api/cron/sync-search-data/route.ts:291
info Commented-code block (5 lines) in src/app/api/cron/daily-report/route.ts:207
info Commented-code block (6 lines) in src/app/api/cron/process-drip/route.ts:23
info Commented-code block (5 lines) in src/app/api/admin/dashboard/search-performanc…
info Commented-code block (7 lines) in src/app/api/admin/analytics/route.ts:611
info Commented-code block (5 lines) in src/app/api/quote/book/route.ts:232
info Commented-code block (8 lines) in src/app/api/quote/price/route.ts:197
info Commented-code block (8 lines) in src/app/api/booking/submit/route.ts:264
info Commented-code block (5 lines) in src/app/api/webhook/ringcentral/sms/route.ts:…

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

low Stray `console.log` in TS/JS — next.config.js:23
low Stray `console.log` in TS/JS — scripts/validate-email-config.js:9
low Stray `console.log` in TS/JS — scripts/configure-vercel-firewall.js:40
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/CLAUDE.md .claude/CLAUDE.md:81
high Agent instruction/config may expose a secret: .claude/skills/setup-satellite/SK… .claude/skills/setup-satellite/SKILL.md:160
info Commented-code block (5 lines) in next.config.js:108

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/c353d6ba-d50f-480b-83c6-b68d3a486832/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c353d6ba-d50f-480b-83c6-b68d3a486832/

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.