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.

vsarypova071-glitch/Photo-Transformation-Studio

https://github.com/vsarypova071-glitch/Photo-Transformation-Studio · scanned 2026-06-16 00:53 UTC (2 months, 1 week ago)

102 raw signals (0 security + 102 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 102 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
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 18 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 supabase/functions/find-recent-order/index.ts…
  • info Commented-code block (5 lines) in supabase/functions/create-payment/index.ts:80
  • info Commented-code block (10 lines) in supabase/functions/auto-refund-order/index.t…
  • info Commented-code block (6 lines) in server/featureFlags.ts:23
  • info Commented-code block (5 lines) in server/routes/generation.ts:211
  • info Commented-code block (7 lines) in server/routes/payment.ts:350
  • info Commented-code block (6 lines) in server/routes/order.ts:51
  • info Commented-code block (7 lines) in server/services/pairPrompts.ts:3
  • info Commented-code block (5 lines) in server/services/prompts.ts:682
  • info Commented-code block (6 lines) in server/services/orderCredit.ts:7
  • info Commented-code block (5 lines) in server/services/openrouter.ts:51
  • info Commented-code block (9 lines) in server/services/referrals.ts:3
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
  • low Unused endpoint: GET /api/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/7f986c44-97e6-4c0b-aa27-a66f4ae23888/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7f986c44-97e6-4c0b-aa27-a66f4ae23888/

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.